Details
-
Suggestion
-
Resolution: Won't Do
-
None
-
None
-
JIRA 4.4.4, Postgres 9.0, OpenLDAP
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
When creating a "Internal with LDAP authentication" directory in JIRA, we have the message:
Configure Internal with LDAP Authentication User Directory
JIRA can use LDAP for user authentication only. To be able to log in to JIRA with this configuration, users must either be created first in JIRA, or the option 'Copy User on First Login' can be checked to automatically add them to JIRA's internal directory. Copied users can subsequently be modified in Confluence, but modifications will not be reflected on the LDAP server.
Groups and memberships from the LDAP server will not be used. However, users from LDAP can be added to groups maintained in JIRA's internal directory.
Let's say the user's info is the following:
- uid=testuser
- mail=testuser@ldapemail.com
If we try to change an attribute for one of the users in this delegated directory, for example, the email address (changing from testuser@ldapemail.com to testuser@jiraemail.com), next time the users logs in JIRA, the email address is set to the testuser@ldapemail.com.
This behaviour also can be observed by editing the user's Full Name.
Attachments
Issue Links
- duplicates
-
JRASERVER-38606 Option to Synchronize Delegated Directory upon first login only - not upon reauthentication
- Closed
- is duplicated by
-
JRASERVER-27541 Delegated LDAP copy user on first login problem
- Closed
- relates to
-
JRACLOUD-27223 LDAP users from delegated directory cannot change their information though JIRA UI
- Closed