-
Bug
-
Resolution: Fixed
-
Medium
-
2.3.1
-
None
-
Using Crowd with delegated authentication against a LDAP
When a user first authenticates against
{JIRA, FECRU, Confuence or Bamboo}, the user's credential are correctly validated and the user is automatically added to the local Crowd cache for that directory.
However, the other Atlassian servers do not have the new user's credential in their local user directory information. Hence, the user login fails on JIRA, etc. and the user is given a system error message.
The problem is self corrected within an hour typically as the other Atlassian servers synchronize their user directories and pick up any incremental user and group information since the last sync.
This should be done automatically when a new user is added to the local Crowd cache for all applications which are using Crowd authentication.
- causes
-
JRASERVER-60747 JIRA with delegated LDAP directory connected through crowd does not auto synchronize user details and groups on first login
-
- Closed
-
- is duplicated by
-
CWD-1857 User Added autmatically to crowd directory when user try to access an application managed in crowd
-
- Closed
-
-
CWD-3972 SSO Authenticator doesn't work for new created crowd users
-
- Closed
-
-
CWD-3661 Crowd backed by delegated auth fails login to connected applications first time
- Closed
- is related to
-
CONFSERVER-23957 Confluence SSO authenticator class does not copy users on login
-
- Closed
-
-
CWD-2238 User should exist in the local directory after successful authentication
-
- Closed
-
-
SER-166 Change login behaviour to authenticate without finding user first
-
- RESOLVED
-
- relates to
-
JRASERVER-39085 JIRA SSO authenticator class does not copy users on login
-
- Closed
-
-
CWD-3163 Crowd-to-Crowd WebHook-based synchronisation
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...