Using the 7/28/05 night build.
I have been experimenting with the new ldap groups support. Here’‘s the problem that I’'ve run into. When JM is parsing the users in a group for displaying the group summary, it all of the sudden begins searching for the wrong username. Hopefully, my debug logs will do a better job explaining what I mean. First, from the debug log is my startup parameters:
+++++++++++++++++++++++++++++++
2005.07.28 14:57:53 host: 10.100.10.1
2005.07.28 14:57:53 port: 389
2005.07.28 14:57:53 usernamefield: nGWObjectID
2005.07.28 14:57:53 baseDN: o=acs
2005.07.28 14:57:53 alternateBaseDN: null
2005.07.28 14:57:53 nameField: fullName
2005.07.28 14:57:53 emailField: mail
2005.07.28 14:57:53 adminDN: cn=holtsclawb,ou=annex,o=acs
2005.07.28 14:57:53 adminPassword: test
2005.07.28 14:57:53 searchFilter: (&(nGWObjectID=)(objectClass=inetOrgPerson))
2005.07.28 14:57:53 ldapDebugEnabled: false
2005.07.28 14:57:53 sslEnabled: false
2005.07.28 14:57:53 initialContextFactory: com.sun.jndi.ldap.LdapCtxFactory
2005.07.28 14:57:53 connectionPoolEnabled: true
2005.07.28 14:57:53 autoFollowReferrals: false
+++++++++++++++++++++++++++++++
As shown, the username is set to nGWObjectID. This is a user’'s groupwise username. Now, the part of the log file that shows my problem:
+++++++++++++++++++++++++++++++
2005.07.28 14:44:09 Trying to find a user’'s DN based on their username. nGWObjectID: mikesholar, Base DN: o=acs…
2005.07.28 14:44:09 Creating a DirContext in LdapManager.getContext()…
2005.07.28 14:44:09 Created hashtable with context values, attempting to create context…
2005.07.28 14:44:09 … context created successfully, returning.
2005.07.28 14:44:09 Starting LDAP search…
2005.07.28 14:44:09 … search finished
2005.07.28 14:44:09 Creating a DirContext in LdapManager.getContext()…
2005.07.28 14:44:09 Created hashtable with context values, attempting to create context…
2005.07.28 14:44:09 … context created successfully, returning.
2005.07.28 14:44:09 Trying to find a user’'s DN based on their username. nGWObjectID: donpowers, Base DN: o=acs…
2005.07.28 14:44:09 Creating a DirContext in LdapManager.getContext()…
2005.07.28 14:44:09 Created hashtable with context values, attempting to create context…
2005.07.28 14:44:09 … context created successfully, returning.
2005.07.28 14:44:09 Starting LDAP search…
2005.07.28 14:44:09 … search finished
2005.07.28 14:44:09 Creating a DirContext in LdapManager.getContext()…
2005.07.28 14:44:09 Created hashtable with context values, attempting to create context…
2005.07.28 14:44:09 … context created successfully, returning.
2005.07.28 14:44:09 Trying to find a user’'s DN based on their username. nGWObjectID: cn=carverj,ou=users,ou=ces,o=acs, Base DN: o=acs…
2005.07.28 14:44:09 Creating a DirContext in LdapManager.getContext()…
2005.07.28 14:44:09 Created hashtable with context values, attempting to create context…
2005.07.28 14:44:09 … context created successfully, returning.
2005.07.28 14:44:09 Starting LDAP search…
2005.07.28 14:44:09 … search finished
2005.07.28 14:44:09 User DN based on username ‘‘cn=carverj,ou=users,ou=ces,o=acs’’ not found.
2005.07.28 14:44:09 Exception thrown when searching for userDN based on username ‘‘cn=carverj,ou=users,ou=ces,o=acs’’
org.jivesoftware.messenger.user.UserNotFoundException: Username cn=carverj,ou=users,ou=ces,o=acs not found
+++++++++++++++++++++++++++++++
The two users, mikesholar and donpowers, work fine. So do quite a few other users before these. However, when it gets to joshcarver, it thinks his nGWObjectID is cn=carverj,ou=users,ou=ces,o=acs. Where does that come from?? It’'s as if JM forgets its usernamefield. I have done an ldif extract to make sure the attribute on that user object is set correctly.
Please let me know what other information I might be able to provide to shed more light on the problem.
Thanks.