No. A schema is a strict definition of how data is to be stored, allowing an application to rely on your storage conforming to that known standard. You can't use a different definition have the application still work.
If you will be storing connections in LDAP, you need to use the established schema for storing those connections. You could also store connections in the database instead, and rely in LDAP strictly for auth. - Mike On Wed, Mar 18, 2020, 12:26 Andrea Lenarduzzi <[email protected]> wrote: > Can I modify "guacConfigGroup" object class? > I cannot modify my actual ldap schema > > Il mercoledì 18 marzo 2020, 20:14:44 CET, Mike Jumper <[email protected]> > ha scritto: > > > On Wed, Mar 18, 2020 at 11:07 AM Andrea Lenarduzzi > <[email protected]> wrote: > > Hi, I've working guacamole 1.2 > > My LDAP server have a particular schema, This is an example: > > dn: cn=Testing,cn=guacamole,dc=domain,dc=local > objectClass: guacConfigGroup > objectClass: top > cn: Testing > guacConfigProtocol: rdp > guacConfigParameter: hostname=host01 > uniqueMember: uid=user1,cn=users,dc=domain,dc=local > > > Guacamole now is searching: > SearchRequest > baseDn : 'cn=guacamole,dc=domain,dc=local' > filter : '(&(objectClass=guacConfigGroup)(|(member= > uid=user1,cn=users,dc=domain,dc=local)))' > scope : whole subtree > typesOnly : false > Size Limit : 1000 > Time Limit : 30 > Deref Aliases : never Deref Aliases > attributes : > > > I think problem is member instead uniqueMember > > How can I fix it? > > > If you will be storing connection data within LDAP using the > "guacConfigGroup" object class, you need to use the correct attribute > ("member") defined by the "groupOfNames" object class that > "guacConfigGroup" inherits from. The "uniqueMember" attribute is not valid > for the schema that we've defined and is not used by the LDAP support for > "guacConfigGroup". > > - Mike > >
