Hello Ilgrosso,
After struggling for a while with the LDAP and AD connectors I kept
wondering why the LDAP connector doesn't search for groups with "Group Name
Attributes" instead of "Uid Attribute".
I was hoping you can illustrate me why it searches on "Uid Attribute" it
makes me curious.
Also it seems for me now, that the only way to set up a succesful user and
group (de)prov with one connector is by using a cn as your username in
Syncope itself (and probably in LDAP aswell for best practice). When using
the uid value it creates a strange search query (see below). As cn=Guus
Geluk it won't find any results since it is searching for the uid value
(uid=guus).
I haven't found a connector configuration which fixes this yet, so I thought
you might have any idea. Since I also haven't seen any other questions about
this scenario, so I am starting to wonder if this is such a unique scenario
to use uid's aswell in Syncope as well as in LDAP.
When using two connectors the user and group (de)prov goes well. Except the
memberships don't seem to get propagated or synchronized from the LDAP
server. I will try a bit harder to get this (and the one connector) setup
working this week. If you like I can keep you posted.
23:55:25.647 DEBUG
org.connid.bundles.ldap.search.DefaultSearchStrategy.doSearch Searching in
[ou=Persons,dc=apds,dc=test,dc=nl, ou=Groups,dc=apds,dc=test,dc=nl] with
filter
(&(&(objectClass=inetOrgPerson)(objectClass=posixAccount)(objectClass=extensibleObject))(cn=guus)(uid=*))
and SearchControls: {returningAttributes=[cn, description, email, gidNumber,
givenName, homeDirectory, sn, uidNumber, userPassword], scope=SUBTREE}
Kind regards,
Jeffrey Everling
--
View this message in context:
http://syncope-user.1051894.n5.nabble.com/ConnId-LDAP-searches-for-uid-in-groupOfUniqueNames-tp5707398p5707423.html
Sent from the syncope-user mailing list archive at Nabble.com.
