-
Suggestion
-
Resolution: Fixed
-
None
OSUser's LDAP integration (ie. JIRA's current LDAP integration) offers delegated authentication to LDAP and does not automatically create the user in locally on successful auth.
The current Crowd Delegated Authentication Directory does perform the auto create on successful auth.
We could provide a flag to option to disable auto creation of users upon successful auth - this makes migration from JIRA's user management system easier as JIRA's LDAP config does not store the necessary data (such as user attribute mapping, eg. firstname, lastname, email, etc) to generate the user object for auto-creation.
If auto-create is disabled, then authentication should fail immediately if the user with the supplied username does not exist locally.
[CWD-1868] Provide option to disallow auto creation of users in the Delegated Authentication Directory (mimic OSUser LDAP behaviour)
Workflow | Original: JAC Suggestion Workflow [ 3362808 ] | New: JAC Suggestion Workflow 3 [ 3626563 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1391795 ] | New: JAC Suggestion Workflow [ 3362808 ] |
Issue Type | Original: New Feature [ 2 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Crowd Development Workflow v2 [ 273468 ] | New: Simplified Crowd Development Workflow v2 [ 1391795 ] |
Workflow | Original: Feature Request Workflow [ 209026 ] | New: Crowd Development Workflow v2 [ 273468 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Awaiting Review [ 10033 ] | New: Resolved [ 5 ] |
Component/s | New: Directory - Internal/Delegated [ 12727 ] |
Hi william.juteau@europe.adp.com, thanks for your comment, however at this moment in time, we will not be changing the documentation to include this database customisation since it is not standard configurable behaviour recommended in Crowd.