Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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



0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events