I am setting up crowd and two instances of Jira on the same domain: foo2.foo.net
Crowd is using port 8095 : http://jc-prod-tomcat-102.foo2.foo.net:8095/crowd
Jira 1 is using port 8080 : http://jc-prod-tomcat-102.foo2.foo.net:8080
Jira 2 is using port 8081 : http://jc-prod-tomcat-102.foo2.foo.net:8081
I can have Crowd handle centralized authentication no problem. But when I try to turn on SSO with the foo2.foo.net domain, I initially get success -- I can log into one jira -- and then the other jira without logging in again. But if I log out, I am locked out of all both jiras and also crowd. I understand from reading that this is likely due to incorrect domain settings. I've tried both '.foo2.foo.net' and 'foo.foo.net.'.
I am using Jira 5 and Crowd 2.4
SSO for Crowd works via cookies for each application server. If you have more than one application running under the same context (in your case, the root context), the cookies will overwrite one another in the root context "/" and you will run into auth problems like this.
If you run your JIRA servers on separate contexts, it should clear up your issue. Example:
JIRA 1: http://jc-prod-tomcat-102.foo2.foo.net:8080/jira
JIRA 2: http://jc-prod-tomcat-102.foo2.foo.net:8081/jira2
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Do you own more than one Server or Data Center product? Do you have challenges provisioning users across your Atlassian products? Are you spending a lot of time integrating each Atlassian product wit...
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!
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