AD userPrincipalName issue on latest openfire v. 3.9.1

Openfire Openfire Support
1

Hello,

We have an issue when we try to use userPrincipalName as an openfire username. As a result we receive correct amount of ldap users, but without any data in them.

The ldap properties are:

ldap.searchFilter = memberOf=CN=SecChatActive,DC=lab,DC=priv)

ldap.searchFields = userPrincipalName

ldap.usernameField = userPrincipalName

Below is the screenshot of what we have in user list

Before we used sAMAccountName - it worked well.

Thanks for any kind of help!!!

2

This issue is related to openfire not escaping field when fetching via LDAP. So it fails on loadUser when it checks if name contains ‘@’. Here is a patch for fixing this https://www.dropbox.com/s/lcwld46a1mje5x4/Fix_userFieldName_fetched_from_LDAP_no t_escaped.patch

3

Thanks, filed as OF-779

4

Hey, it looks like this patch may be related to LDAP groups disappearing issue in 3.9.3 (OF-830).

5

I have sync my openfire by using principalName, but when I need to add the administrators, it throws an exception and it tries to add:

user@ldapdomain.com@myjabberdomainserver

there is a solution for this?