That funny looking username normally relates to a user logged in anonymously. I’m guessing that the JID resource also have the same funny string, so the full JID is like for e.g. 8ab3aae1@servername/8ab3aae1. It seems to me like after the successful authentication the server could not associate the username with an existing user data, therefore it allows login but with an anonymous status and the username changed. If your openfire.xml is like shown in your other thread, I think I might have spotted some errors:
Also the provider section must appear once only. On the contrary, you have more than a provider section scattered around in the file. You should include all your providers in a single provider section, as follows, and remove all others:
<auth> <className>org.jivesoftware.wildfire.auth.JDBCAuthProvider<;/className> </auth> <user> <className>org.jivesoftware.wildfire.user.JDBCUserProvider<;/className> </user> <group> <className>org.jivesoftware.wildfire.group.JDBCGroupProvider<;/className> </group> </provider>
Because you use multiple provider section and you define your AuthProvider first in the file, the authentication works but your UserProvider and GroupProvider don’t.
BTW, you’re looking at the guide for Wildfire. The latest custom database integration guide for Openfire is here
Hope that helps.