-
Suggestion
-
Resolution: Fixed
-
None
-
None
I've been testing Crowd 1.3, and I really like the new Delegated Directory feature. One thing I found non-obvious about it was that users have to be manually created or imported in the delegated directory in order to be visible, even if they actually exist in the underlying connector-based directory. It would be nice if there was a way to have the Delegated Directory have a fallback when a user isn't found in the internal directory, which is to check in the connector-based directory and if the user exists in there, to create it in the internal directory.
One important advantage of such a fallback is that users wouldn't have to be created in two separate places - Crowd would automatically know about a user as soon as it was created in LDAP. (With the Delegated Directory the way it currently is, the user might exist in LDAP but not be visible in Crowd.)
- is related to
-
CWD-962 Automation for delegated directories
- Closed
[CWD-917] Automatically create non-existent users in Delegated Directory
Workflow | Original: JAC Suggestion Workflow [ 3389134 ] | New: JAC Suggestion Workflow 3 [ 3630424 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1392984 ] | New: JAC Suggestion Workflow [ 3389134 ] |
Assignee | Original: David O'Flynn [Atlassian] [ doflynn ] | |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Crowd Development Workflow v2 [ 272828 ] | New: Simplified Crowd Development Workflow v2 [ 1392984 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: Feature Request Workflow [ 174014 ] | New: Crowd Development Workflow v2 [ 272828 ] |
Workflow | Original: jira [ 123630 ] | New: Feature Request Workflow [ 174014 ] |
Component/s | New: Directory - LDAP [ 11873 ] |
This was fixed a long time ago - delegated authentication directories copy the user upon first successful authentication.