Is OAuth (Impersonation) with crowd not enough anymore for SSO??

We have following setup:

  • jira + confluence on 1 Server with 2 tomcat instances.
  • the aplications are using the context /jira and /confluence
  • confluence uses jira user directory with type crowd. synchronisation is successful.
  • user access both applications via reverse proxy. reverse proxy is setup correctly, using it's own proxy connector in both apps. healthchecks are ok.
  • both applications are linked to eachother by OAUth (impersonation) and green (linked). (Internal linked by localhost, shown URL is the proxy URL)

Quite normal setup. As far as I can remember, I'd say SSO worked before upgrading jira to 7.3.3. After upgrade users have to login twice. Did I something wrong or is this intended behaviour with 7.3.3??


1 answer

PS: confluence and jira logs don't show any error regarding oauth. otherwise I had a point to start from to follow the documentation.

Suggest an answer

Log in or Join to answer
Community showcase
Maarten Cautreels
Posted Thursday in Off-topic

Friday Fun: What's your favourite beer/drink

As a Belgian, beer-lover and home brewer, beer is one of my great passions. I love the fact that with just a few ingredients (usually just water, hop and malt) you can create so many different tastes...

285 views 38 9
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot