This is for a dev/test configuration where all three services JIRA, Confluence, and Crowd are running on a single host (using different ports). I have crowd working with both applications (JIRA and Confluence) and I can log into each separately. The problem is that as soon as I log into the second application, the first application requires a new login. The only diffrence between the services is the port number
So, each time I log into JIRA, it will invalidate the current Confluence login and ask me to login again. Crowd is setup to use a Delegated/Generic LDAP connection.
Using diffrent address per application is the way to go. Got this answer from support...
The reason for this behavior is that the cookie is created via the domain. In this case, each service was at http://host.example.com as far as the browser was concerned. Therefore, each new login granted a new cookie which invalidated the previous one. The most common way around this is to either to us a context path (http://host.example.com/confluence) or a mixed domain (http://confluence.host.example.com).
The other way, which you have discovered, is to establish SSO with Crowd. In this situation the cookie (and token) are assigned view Crowd so for each application the token is the same so you are not logged out.
Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events