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

SSO: stash -- crowd console, works one way but not the other

I have crowd and stash installed behind a Apached proxy, all operating on the same machine (with the same IP address). I've configured both according to all the documentation I can find. If I log into Crowd Console, SSO works fine on Stash. If I log into Stash, there is no SSO for Crowd Console (IOW, I have to log into Crowd Console even though I'm logged into Stash via Crowd). I'm at a loss how to fix this. Suggestions?

3 answers

1 accepted

0 votes
Answer accepted

Apparently I wasn't correctly proxying in Apache. After I changed the proxy to be the following, everything worked.

ProxyRequests Off
    ProxyPreserveHost On

    ProxyPass /crowd  http://localhost:8095/crowd
    ProxyPassReverse /crowd  http://localhost:8095/crowd

    ProxyPass /stash http://localhost:7990/stash
    ProxyPassReverse /stash http://localhost:7990/stash

Hi Robert,

I just wanted to confirm. You managed to get SSO working?


2 votes

Hi Robert,

The SSO configuration sometimes is tricky, but there are some key points that I'd suggest you to check, they are the following:

1. Ensure that the URLs being used to access each application and the SSO Domain value stored in Crowd are valid and match the pattern;
2. Ensure that all applications are using the Crowd authenticator at their WEB-INF/classes/seraph-config.xml files;
3. Ensure that the Directories that are assigned to each application in Crowd, If more than one, are in the exact same order;
4. If there are proxy servers being used between Crowd and the applications, make sure to add their IP addresses to theTrusted Proxy Servers list in Crowd.

I hope this information has helped.


Thanks. Here's what I've configured:

  1. The URLs are all D.C.B.A/X, like D.C.B.A/stash or D.C.B.A/crowd. The SSO Domain is D.C.B.A
  2. Stash doesn't use Seraph and doesn'thave a seraph-config.xml file.
  3. The directories are in the same order, but aren't identical. No users are shared between directories. IOW, user X exists in only one directory.
  4. There is a proxy server and its address in the Trusted Proxy Server's list, and also it is the same IP as each of the Atlassian applications which are standalone.

All of this was the existing configuration which had the problem described above. So none of this fixed the problem.

0 votes

In addition, I'd suggest you specially to check if is correctly informed the application name in the file on your application.

Please check this documentation for more information:


Thanks. Yep, had did that already.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events