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 Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Marketplace Apps

Tips on how to choose the best estimation method for your planning

Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...

65 views 0 11
Read article

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