Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,551,771
Community Members
 
Community Events
184
Community Groups

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

PRISMA Computer GmbH
PRISMA Computer GmbH Apr 27, 2017

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

 

Answer
Watch
Like Be the first to like this
273 views

1 answer

0 votes
PRISMA Computer GmbH
PRISMA Computer GmbH Apr 27, 2017

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

Reply

Suggest an answer

Log in or Sign up to answer
Crowd
Crowd
TAGS
AUG Leaders

Atlassian Community Events

See all events