-
Bug
-
Resolution: Fixed
-
Medium
-
2.1.3
-
None
If an LDAP group contains a member which doesn't exist, Confluence gets the name from the group, gets a user (which returns null) and then does things with the null pointer, rather than reporting that the group contains a user which doesn't exist (it does log it, but not in a clear way)
- is related to
-
CONFSERVER-5723 Group membership search in LDAP assumes user's dn starts with username attribute
-
- Closed
-
[CONFSERVER-5305] Non-existent users in groups cause problems when using LDAP
Workflow | Original: JAC Bug Workflow v3 [ 2882931 ] | New: CONFSERVER Bug Workflow v4 [ 2978365 ] |
Workflow | Original: JAC Bug Workflow v2 [ 2785164 ] | New: JAC Bug Workflow v3 [ 2882931 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Bug Workflow [ 2714180 ] | New: JAC Bug Workflow v2 [ 2785164 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2379905 ] | New: JAC Bug Workflow [ 2714180 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2270737 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2379905 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2216012 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2270737 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2167445 ] | New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2216012 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 1925627 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2167445 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v3 [ 1727714 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 1925627 ] |
Workflow | Original: CONF Bug Subtask WF (TEMP) [ 1684018 ] | New: Confluence Workflow - Public Facing - Restricted v3 [ 1727714 ] |