POP3AuthProvider: capital letters in username becomes 64404c54

Openfire Openfire Support
1

Hi there.

In order to work around a random LDAP problem that appeared this morning (our Active Directory servers have started replying “User DN based on username ‘’[user_name]’’ not found.” to every user), I set up a pop3 to LDAP gateway on localhost and began using the POP3AuthProvider. I have no idea as yet what is causing the original problem.

The pop3 workaround works perfectly, except anyone with capital letters in their login (EG James_Hicks) ends up as random numbers and letters, EG 64404c54. They log in fine, can talk to people etc, but they appear as the randomly generated ID instead of themselves. Everyone using purely lower case letters has no problems. Obviously right now we’‘re telling people to log in with all lower-case, but this isn’'t ideal

Is this a bug? It’'s happening on our live server (2.6.2) and our test server (2.6.2 and then 3.0.1).

Is there some response I can configure my fake pop3 server to give (IE the login name converted to lower case) that will work around it?

Regards,

James

PS Wildfire is fantastic.

2

Update: We’‘re no longer using my dodgy pop3->LDAP gateway, so this issue is no longer urgent for us. I’'m still interested in it though and happy to test on our test things on my test machine

The AD problem was that someone had moved our internal_messaging group out of its own container in the top level into a nicely organised ‘‘groups’’ group or something. This is now fixed.