Crowd for several servers/domains/applications Edited

[Jean Bausch]

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:

• https://server1.company.domain/docs (reverse proxy to confluence on http://server3.internal.domain:8090)
• https://server1.company.domain/plans (reverse proxy to JIRA on http://server4.internal.domain:8080)
• https://server2.company.domain:8443 (running confluence without proxy)

The user management for these applications should run on:

• https://server1.company.domain/crowd (with or without reverse proxy?)

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?

[Nic Brough [Adaptavist]]

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.

[Jean Bausch]

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.