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

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.

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.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Do Not Lose your Customer’s Trust

Missing deadlines is one of the biggest problems every team lead wants to avoid when dealing with managed services. When the customer contracts your company to help with IT services it is expected th...

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