[CONFSERVER-13420] LDAP users can be cached as non-existant / not permitted to login if the LDAP repository is not available - Create and track feature requests for Atlassian products.

Type: Bug
Resolution: Fixed
Priority: Medium
Fix Version/s: 3.5
Affects Version/s: 2.5
Component/s: None
Labels:
- LDAP
- affects-server
- ec
- failure
- intermittent
- login
- pm_review
- random
- users&groups

Support reference count:
8
Bug Fix Policy:
View Atlassian Server bug fix policy

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

Assignee:: Matt Ryall

Reporter:: Andrew Lynch (Inactive)

Affected customers:: 11 This affects my team

Watchers:: 13 Start watching this issue

Created:: 16/Oct/2008 10:34 PM

Updated:: 11/Oct/2018 9:01 AM

Resolved:: 14/Mar/2011 6:03 AM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates