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

How to stop OpenLDAP directory from synchronizing?

Hi,

I have an OpenLdap directory which syncs the users whenever I make any change in user/class filters. 

Lately, I've been testing a bit more with the OpenLDAP directory and whenever I make a change in the userFilter, the directory starts to sync automatically.
This is something that I want.

But I want to know how to stop the directory from syncronising once it has begun? 
The total time to sync is about 50-60 minutes for my JIRA server, so lets say I wanted to stop the current sync because I want to make some changes that I forgot? 
How do I do that?
Because waiting for directory to syncronize completely takes just too much of time. 

1 answer

Hi Muhammad,

In order to stop the sync you would need to take the directory offline. Here is how that would have to work:

  1. Stop CROWD
  2. Disable the LDAP directory in the database
  3. Restart CROWD
  4. Make your changes in the third party LDAP server
  5. Stop CROWD
  6. Re-enable the LDAP directory in the database
  7. Restart CROWD

The issue you'll run into is that as long as the third party directory is enabled in CROWD it will attempt to sync.

As you can see that is less than ideal.  I can see the benefit of that feature though.  I would recommend you go to JAC and create a ticket so our developers can consider adding in the future.  Hopefully this helps!

Cheers,

Branden

This is incredibly frustrating as the sync begins automatically before you've finished configuring things like group filter.  On a large LDAP or AD system (the one I'm working with contains 250,000 users and 118,366 groups) this means you have to wait hours for the first full sync to complete, where it queries every user and group in the directory... and then once that's finished... several more hours while it syncs again to remove the redundant directories from Crowd.

It's an atrocious design - the sync should not begin until the Crowd Admin pushes a button!

Like # people like this

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

299 views 9 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