powered by Jive Software

Special Characters in Username break login attemt with AD

Hi group,

at the moment I have successfully set up Openfire 3.6.4 with our Active Directory. Unfortunatly a new Member has a special Character in his Username (ü) wich will break the login process.

Does anyone know if the Bug JM-497 is already resolved? Or if my problem is the same as JM-497?

I created a Test-User with username “ümläüte” (wich is display correctly in the Webbackend BTW) and enabled debugging:

2009.10.06 09:33:33 LdapManager: Trying to find a user’s DN based on their username. sAMAccountName: �ml��te, Base DN: OU=“GDH_user”,DC=“ad”,DC=“gdhv”,DC=“de”…

2009.10.06 09:33:33 LdapManager: Creating a DirContext in LdapManager.getContext()…

2009.10.06 09:33:33 LdapManager: Created hashtable with context values, attempting to create context…

2009.10.06 09:33:33 LdapManager: … context created successfully, returning.

2009.10.06 09:33:33 LdapManager: Starting LDAP search…

2009.10.06 09:33:33 LdapManager: … search finished

2009.10.06 09:33:33 LdapManager: User DN based on username ‘�ml��te’ not found.

2009.10.06 09:33:33 LdapManager: Exception thrown when searching for userDN based on username ‘�ml��te’

org.jivesoftware.openfire.user.UserNotFoundException: Username �ml��te not found

at org.jivesoftware.openfire.ldap.LdapManager.findUserDN(LdapManager.java:711)

at org.jivesoftware.openfire.ldap.LdapManager.findUserDN(LdapManager.java:637)

at org.jivesoftware.openfire.ldap.LdapAuthProvider.authenticate(LdapAuthProvider.j ava:112)

at org.jivesoftware.openfire.auth.AuthFactory.authenticate(AuthFactory.java:158)

at org.jivesoftware.openfire.net.XMPPCallbackHandler.handle(XMPPCallbackHandler.ja va:87)

at org.jivesoftware.openfire.sasl.SaslServerPlainImpl.evaluateResponse(SaslServerP lainImpl.java:112)

at org.jivesoftware.openfire.net.SASLAuthentication.handle(SASLAuthentication.java :245)

at org.jivesoftware.openfire.net.StanzaHandler.process(StanzaHandler.java:161)

at org.jivesoftware.openfire.nio.ConnectionHandler.messageReceived(ConnectionHandl er.java:133)

Maybe anyone could help resolving the issue?

Thanks in advance!

Tobias

After some debugging and testing with other setups I found, that I could log in with a different client. It apears not to be an Openfire Prob lem, but rahter a Problem with the stable version (2.5.8) of Spark.

Switching to the beta-version of spark (2.6.0) resolved the Issue.