Changed fullname in LDAP not propagated in JIRA/Confluence

[Matthias Linhuber]

Hi Atlassian Team,

we have the following configuration.

JIRA is accessing our "Apple Open Directory (Read-Only) (Read Only)" LDAP Server and is synchronizing users and groups. Confluence is then using an Atlassian Crowd directory to connect to JIRA and to synchronize users and groups with it. So far this works very nice.

Now we detected that the "first name" of a user was wrong in our Apple Open Directory. Thus we changed it in the LDAP Server (without changing the username). But after synchronizing JIRA and Confluence multiple times, the "full name" of this user is not changed and JIRA as well as Confluence are still showing the wrong name.

Is there a possibility to force JIRA and Confluence to reload the "full name" of one (or all) users while synchronizing?

Thanks for an answer!

Best wishes,

Helma

[Matthias Linhuber · Accepted solution]

Hi Septa,

thank you for the quick response.

We found the problem this morning: we only changed the "full name" in our LDAP server and we thaught that JIRA is using the full name attribute from LDAP as it is mentioned in the User Browser, but it seams that JIRA is using <firstname> <lastname>.

After changing firstname and lastname in LDAP it worked for us and everything is fine :-)

Best wishes,

Helma

[Septa Cahyadiputra]

Great to hear that you are able to resolved it :)

[Septa Cahyadiputra]

Hi Helma,

By default JIRA should pick up any changes done on your LDAP server if the users is searchable on your search filter. Could you please let us know if there are any message of syncrhronization failure on your "User Directories" menu.

If there are none, could you please confirm that the users you changed on the LDAP server is searchable on your LDAP server. There might be duplciate on your LDAP server and the one modified is the duplicate which is not searchable by JIRA which cause your issue.

Cheers,
Septa Cahyadiputra