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 doesn't see all users in AD

Hi All,

A customer has a Crowd instance that has a connector to a company AD set up.

They recently migrated their AD from one server to two new, and since then, a number of users have been unable to login.

Searching for those users in crowd revealed that Crowd no longer sees them in the AD, even though they most certainly are there *and* are members of the relevant groups that I'm filtering for.

I don't know if it's relevant, but the two new DCs are running Windows Server 2012 - I don't know what the old DC was running.

What could be wrong, and how can I find out?

Best regards,

Sune Mølgaard

3 answers

1 accepted

0 votes
Answer accepted

Hi Sune,

It's a bit difficult to know what's wrong with only this information. Would be possible for you add some more details of your configuration and let us know if there is any error in your Crowd logs?

Also, have you created a new directory in Crowd for this new AD server or have just updated the existing one to point to the new server?

Cheers

I initially created a new directory and ran into the problems I described.

Going back and just editing the old directory seemed to do the trick, however.

Worth noting was that I pointed the connector directly at the domain this time, instead of one of the actual servers.

Thus, I mark your post as the answer, since I take it to suggest editing the old directory if (as I did) I had tried to make a new one.

Cheers

Furthermore, trying the LDAP filter on the DC itself *does* find the missing users...

Hi Sune,

It's a bit difficult to know what's wrong with only this information. Would be possible for you add some more details of your configuration and let us know if there is any error in your Crowd logs?

Also, have you created a new directory in Crowd for this new AD server or have just updated the existing one to point to the new server?

Cheers

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

☕️ Monday coffee with Jexo: Weekly Atlassian news roundup | 21st June 2021

Hi community 👋, as every Monday we're bringing you a quick update on what happened in the Atlassian ecosystem last week. There were a few interesting events like for example the announcement of th...

68 views 0 6
Read article

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