Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • 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
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?
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 apache connector performance issues



I am using crowd apache connector for SVN SSO with crowd.

The SSO configuration is working fine and I can see it from browser as well as IDE/Tortoise SVN client etc.

configuration is:

AuthName "Atlassian Crowd"
        AuthType Basic
        AuthBasicProvider crowd
        CrowdAppName <SVN APP NAME>
        CrowdAppPassword <SVN APP PWD>
        CrowdURL https://<CROWD HOST>:9443/crowd/
        CrowdSSLVerifyPeer Off
        CrowdCreateSSO off  # Improves performance when using Subversion clients that don't store cookies

We do have many repos and each repo had its own acl with list of users defined.

We can reuse the same files for authorization as well, however, we are having performance issues. e.g. it used to take 2 sec, now it is taking 40 sec.

Is there any setting to control that e.g. cache data or not to go to crowd for every request etc?





2 answers

0 votes

You have two options to control the cache behavior, which are documented in Integrating Crowd with Apache:

CrowdCacheMaxAge 120

The maximum number of seconds that a response from Crowd will be cached by the Apache Crowd connector.


CrowdCacheMaxEntries 1000

The maximum number of entries cached at any time by the Apache Crowd connector. If set to 0, caching is disabled.



The last column denotes the default value, and a note further down on that page confirms that caching should already be enabled by default:

  • If the CrowdCacheMaxEntries setting is missing or set to a non-zero value, then requests to Crowd are cached in order to increase performance. This means that changes to passwords, group membership and session expiry in Crowd may not be reflected immediately in user access.

Given your scenario comprises many repos, you probably need to ensure that CrowdCacheMaxEntries is sufficiently large to avoid items being purged from the cache early and actually yield them to be cached for CrowdCacheMaxAge.



Although I have


LoadModule authnz_crowd_module modules/

LoadModule  authz_svn_module       modules/


I am getting


CrowdCacheMaxAge not allowed here


Any suggestions.



I guess I had to add those cache options outside of location tag of apache. However, even after doing that, performance didn't improve much. What I have is crowd configuration in place, and not for each individual repo. Each individual repo location, I have specified acl file. Not sure if that makes any difference..

Suggest an answer

Log in or Sign up to answer
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...

180 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