-
Suggestion
-
Resolution: Duplicate
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
When LDAP users are deleted in the LDAP server JIRA will automatically delete the users on JIRA side during the next synchronization.
This behavior would cause a known issue which is documented on knowledge base article here:
It would be great if JIRA would be able to do the following scenarios:
Option 1
- User deleted on LDAP server
- JIRA synchronize with LDAP server and understand that there are missing users
- JIRA check if the users have created any content on JIRA
- If the users have created any content JIRA would keep the users and deactivate it for licensing purposes
Option 1
- User deleted on LDAP server
- JIRA synchronize with LDAP server and understand that there are missing users
- JIRA check if the users have created any content on JIRA
- JIRA deleted the user on LDAP directory
- Re-create the user in "Internal Directory"
- Deactivate it for licensing purposes
- duplicates
-
- Closed
- relates to
-
- Closed
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
[JRASERVER-29202] JIRA Should Handle Deleted LDAP User(s) Better
| Workflow | Original: JAC Suggestion Workflow [ 3055148 ] | New: JAC Suggestion Workflow 3 [ 3684859 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2606461 ] | New: JAC Suggestion Workflow [ 3055148 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2557735 ] | New: Confluence Workflow - Public Facing v4 [ 2606461 ] |
| Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2347842 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2557735 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2114341 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2347842 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2093051 ] | New: JIRA Bug Workflow w Kanban v6 [ 2114341 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 875517 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2093051 ] |
| Description |
Original:
When LDAP users are deleted in the LDAP server JIRA will automatically delete the users on JIRA side during the next synchronization.
This behavior would cause a known issue which is documented on knowledge base article here: * [Issues associated to users deleted from LDAP or crowd can not be reassociated to a different user|https://confluence.atlassian.com/display/JIRAKB/Issues+associated+to+users+deleted+from+LDAP+or+crowd+can+not+be+reassociated+to+a+different+user] It would be great if JIRA would be able to do the following scenarios: *Option 1* # User deleted on LDAP server # JIRA synchronize with LDAP server and understand that there are missing users # JIRA check if the users have created any content on JIRA # If the users have created any content JIRA would keep the users and deactivate it for licensing purposes *Option 1* # User deleted on LDAP server # JIRA synchronize with LDAP server and understand that there are missing users # JIRA check if the users have created any content on JIRA # JIRA deleted the user on LDAP directory # Re-create the user in "Internal Directory" # Deactivate it for licensing purposes |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-29202]. {panel} When LDAP users are deleted in the LDAP server JIRA will automatically delete the users on JIRA side during the next synchronization. This behavior would cause a known issue which is documented on knowledge base article here: * [Issues associated to users deleted from LDAP or crowd can not be reassociated to a different user|https://confluence.atlassian.com/display/JIRAKB/Issues+associated+to+users+deleted+from+LDAP+or+crowd+can+not+be+reassociated+to+a+different+user] It would be great if JIRA would be able to do the following scenarios: *Option 1* # User deleted on LDAP server # JIRA synchronize with LDAP server and understand that there are missing users # JIRA check if the users have created any content on JIRA # If the users have created any content JIRA would keep the users and deactivate it for licensing purposes *Option 1* # User deleted on LDAP server # JIRA synchronize with LDAP server and understand that there are missing users # JIRA check if the users have created any content on JIRA # JIRA deleted the user on LDAP directory # Re-create the user in "Internal Directory" # Deactivate it for licensing purposes |
| Link |
New:
This issue relates to |
| Labels | New: affects-server |