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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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
4,458,488
Community Members
 
Community Events
176
Community Groups

Crowd SSO only allowing user to access one other application

I have a VM running crowd 2.7.1, a VM running Confluence 5.4.4, and a third VM running JIRA 6.2.

I have successfully configured both confluence and JIRA to use Crowd for authentication and enabled SSO. My problem is, the SSO will only allow me to automatically authenticate with one of the two other applications in a browser session.

Say I log in to crowd. I can then open up JIRA in another tab and I am automatically authenticated. However, if I then open up Confluence in a third tab it directs me to the login page. After I log in to Confluence, if I log out of any one of the 3 applications I am logged out of all the others as well. 

If I log into crowd again, and this time open up confluence first, I will be automatically authenticated. But then if I open JIRA I am directed to the login page. This pattern holds for any order/combination of applications (If I log into JIRA, then open Confluence I will auto-authenticate, but I am taken to the login page when I try to access Crowd.)

What could be causing this?

2 answers

I figured it out, and am posting here for anyone that has this issue in the future. The problem was a combination of things, but I was able to fix this (and a couple other issues) by enabling authentication caching and adding our load balancers to the list of trusted proxies.

1 vote

Proxy server causing issues?

I've thought about that, since it's sitting behind a load balancer, but that still wouldn't explain why it only allows me to auth to one. If neither of them were working then I'd agree, but SSO can force sign off on all three so I don't understand how the reverse isn't true as well.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events