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

Adding user to group fails over LDAP to AD?

I run in to a problem with my Crowd 3.6.0 talking LDAP with my AD server:

If I edit a group to add a user to a group, Crowd says "Update successful" and lists the user as beeing added to the group.

Looking in the AD, the user isn't updated with the group.

After a couple of minutes Crowd syncs with the AD and the user is removed from the group in Crowd.

Crowd's Audit log shows exactly the above: User X added to group Y, Sync started, User X removed from group. (See lower part of the screenshot below.)

However: If I instead edit the user to add a group to the user (i.e. not the user to the group) then the AD immediately gets updated and the group stays on even after Crowd has done its periodic sync. (See upper part of the screenshot below.)

If I remove a user from a group or remove a group from a user, then the AD immediately gets updated and my change survives the next Crowd/AD sync. Behaviour is as expected.

To further confirm this bug I hooked up Wireshark to sniff and get a pcap of the Crowd/AD ldap signalling. I could see that on the 3 things that worked, Wireshark showed immediate/live traffic, whereas on the buggy thing (adding user to group) Wireshark was silent. (Or rather: Crowd was silent, didn't attempt to update the AD with the change.)

 

image.png

0 answers

Suggest an answer

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

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

213 views 6 7
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