I’'m having a problem with my Auth, User and Group providers when running under wildfire 3.2 versions.
The problem is connected with a change in Wildfire that now assumes that the username I login with is the front part of my jid. This was not necessarily the case with versions prior to 3.2, since a custom UserProvider can return a User object that has a different username from the one passed to the UserProvider.
In previous versions this was supported and was quite useful for keeping a the username used for authentication hidden from other users. For example, I may want to login with a username used for my corporate identity, but don’'t necessarily want all my jabber contacts to know my corporate username by looking at my JID.
Is there any chance that the final version of 3.2 will support this? (i.e. behave like previous releases)
Or perhaps someone has an idea for a workround?