You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Yet another feasibility question.
Currently we have 3 applications for which we would like to centralize the user management and get a Single Sign On:
The user management for these applications should run on:
So we have a mixture of the two examples given at https://confluence.atlassian.com/crowd/overview-of-sso-179445277.html.
Do we have to configure a third reverse proxy to cover the confluence on server2 - like https://server1.company.domain/manuals?
You don't have to configure a reverse proxy, but you do need to make sure server2 can get to Crowd and Crowd can reach it over the base url.
ok for the common user directory.
But is this also true for Single Sign On? The page that I quoted above says that the domain in the Crowd configuration differs between example 1 and 2 (domain.com vs .domain.com). Which one should we choose in our mixed configuration?
I have yet another open question because we can't get SSO to work even with one server only.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.