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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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 Full LDAP Directory Sync running 2 times Edited

Hi!

Crowd Version: 3.7.0 (Build:#1270 - 2019-10-03)

We are using a Generic Directory Server with LDAP to sync Users from Okta.

We have caching enabled and are using a page size of 200 and it looks like Crowd runs a full sync always 2 times.

It starts with

2019-12-19 15:20:33,569 Caesium-2-3 INFO [atlassian.crowd.directory.DbCachingRemoteDirectory] FULL synchronisation for directory [ 28508161 ] starting

The many entry pairs appear during the sync:

2019-12-19 15:21:35,219 Caesium-2-3 INFO [directory.ldap.monitoring.TimedSupplier] Timed call for search with handler on baseDN: ou=users,dc=xxxxx, dc=okta, dc=com, filter: (organizationalStatus=ACTIVE) took 5863ms
2019-12-19 15:21:35,219 Caesium-2-3 DEBUG [atlassian.crowd.directory.SpringLDAPConnector] Iterating a search result size of: 200

. . .

Then a summary about the number of synced users is displayed

2019-12-19 15:39:45,137 Caesium-2-3 INFO [directory.ldap.cache.RemoteDirectoryCacheRefresher] found [ 36047 ] remote users in [ 1151567 ms ]
. . .

but then crowd seems to restart the sync and the previous entry pairs appear again:

2019-12-19 15:40:08,241 Caesium-2-3 INFO [directory.ldap.monitoring.TimedSupplier] Timed call for search with handler on baseDN: ou=users,dc=xxxxxx, dc=okta, dc=com, filter: (organizationalStatus=ACTIVE) took 8862ms
2019-12-19 15:40:08,241 Caesium-2-3 DEBUG [atlassian.crowd.directory.SpringLDAPConnector] Iterating a search result size of: 200

. . .

until the full sync ends

2019-12-19 16:04:07,625 Caesium-2-3 INFO [atlassian.crowd.directory.DbCachingRemoteDirectory] FULL synchronisation complete for directory [ 28508161 ] in [ 2614056ms ]

The number of entry pairs times 200 is about the double number of user entries.

I wonder what Crowd is doing here by syncing the Users two times ?
Can this be optimized ?

Any hints on what is going on would be greatly appreciated!

Regards,
Hans

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Opsgenie

Opsgenie and Amazon team up to launch new DevOps Guru integration - now available!

We’re proud to announce that our integration with Amazon DevOps Guru is now live. The Amazon and Opsgenie product teams have worked together to build a deep integration between Opsgenie and the new...

242 views 0 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