We have recently moved to Delegated Authentication because the main LDAP Directory is too big( 50k+ users ), to be directly used in Crowd.
The Problem we are facing now is in Crowd 2.1.1 is, if a user does a successful authentication in any of the application, a user is automaticaly created( even though he might not have any access and he might not even be granted any access in future). So this will create a lot of unnecessary users in Crowd.
I checked the database table cwd_directory_attribute and found this attribute "crowd.delegated.directory.auto.create.user" with a value "true", and I think this is the thing which is creating the users.
Now my question is, if I just change it to false, will it stop creating the users and do I need to restart Crowd server and do we have any other neat/clean way to do this or this is the only solution.
You have different fields at configuration tab of directory connection.
These are mapping attributes provided by Active Directory through LDAP interface to your Crowd database.
"User Display Name Attribute" is used displaying concatinated naem in the list.
"User First Name Attribute" and "User Last Name Attribute" is diplayed in user details.
Try different field names for mapping for "User Display Name Attribute" usual attribute names are "fn" or "displayName".
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Do you own more than one Server or Data Center product? Do you have challenges provisioning users across your Atlassian products? Are you spending a lot of time integrating each Atlassian product wit...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs