-
Bug
-
Resolution: Fixed
-
Medium
-
2.2 Iteration 4
-
None
Scenario: JIRA -> Crowd -> LDAP Delegated Auth
- New user is created in LDAP.
- New user tries to log in in JIRA.
-> Authentication succeeds, and the new user is created in Crowd, but will not be visible in JIRA before the next synchronisation with Crowd.
The specific problem is that DBCachingRemoteDirectory#authenticate does not create non-existing users in the local directory.
Ideally we would do full synchronisation in this case, but a full synchronisation can take a very long time. Creating user in the local directory and adding group memberships for the user should fix this situation.
- is related to
-
CONFSERVER-23957 Confluence SSO authenticator class does not copy users on login
-
- Closed
-
- relates to
-
CWD-2650 Crowd doesn't create new users automatically in other directories when he first login, but after sometime
-
- Closed
-
[CWD-2238] User should exist in the local directory after successful authentication
Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 1509214 ] | New: JAC Bug Workflow v3 [ 3364075 ] |
Link | New: This issue is related to CONFCLOUD-23957 [ CONFCLOUD-23957 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1390934 ] | New: Simplified Crowd Development Workflow v2 - restricted [ 1509214 ] |
Workflow | Original: Crowd Development Workflow v2 [ 277846 ] | New: Simplified Crowd Development Workflow v2 [ 1390934 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Link |
New:
This issue is related to |
I am able to reproduce this. Should I contact support?