Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Crowd Delegated Authentication auto create user

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.

1 answer

Hi Gaurav,

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".

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Asked in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

238 views 12 14
View question

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you