-
Bug
-
Resolution: Fixed
-
Medium
-
2.5
-
None
-
8
-
If an error occurs connection to the LDAP repository during the initial login, it is possible for this failure to be cached as the user not existing and so subsequent login attempts will be unsuccessful.
The workaround for this is to manually flush the LDAP users cache
- duplicates
-
CONFSERVER-8636 Flushing the cache seems to renew LDAP connections
-
- Closed
-
[CONFSERVER-13420] LDAP users can be cached as non-existant / not permitted to login if the LDAP repository is not available
Workflow | Original: JAC Bug Workflow v3 [ 2894900 ] | New: CONFSERVER Bug Workflow v4 [ 2985960 ] |
Workflow | Original: JAC Bug Workflow v2 [ 2782058 ] | New: JAC Bug Workflow v3 [ 2894900 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Bug Workflow [ 2710426 ] | New: JAC Bug Workflow v2 [ 2782058 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2375677 ] | New: JAC Bug Workflow [ 2710426 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2262471 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2375677 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2212392 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2262471 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2159651 ] | New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2212392 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 1915544 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2159651 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v3 [ 1721329 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 1915544 ] |
Workflow | Original: CONF Bug Subtask WF (TEMP) [ 1674159 ] | New: Confluence Workflow - Public Facing - Restricted v3 [ 1721329 ] |