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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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



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

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.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events