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
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
We have two different crowd instances, one for productiopn and one for test. Subsequently we also have prod and test version of Atlassian products, e.g., Jira, Confluence, etc and integrated with the Crowd prod and test instances respectively.
The problem was when we ran a prod and test version of Jira for example in the same browser, then we constantly got kicked out from each other.
This is not an issue when we run a prod instance not on the same browser, e.g., IE and a test instance on different browser, i.e, Chrome, etc.
Is there any session cookies setting that we can configure to allow both prod and test instance running on the same browser?
This behaviour is absolutely normal as your test environment applications set a cookie that has the exact same name as the one set by your prod instances (the default Crowd SSO cookie name is crowd.token_key).
On your test instance of Crowd, go to your crowd.home directory (the one you configured in crowd-init.properties when installing the product), edit the crowd.properties file and set the following value:
That should do the job. If this still does not work you might also need to add that very property to each of your applications' crowd.properties file.
Thanks for the reply, unfortunately it didn't work.
Should I restart the Crowd test instance?
As for the other alternative to add for each applications' crowd.properties file which for sure it requires a restart, since the file is located in the <INSTALL_DIR> not the <APP_HOME_DIR>.
Another question: is the following format correct?
it should be:
You actually do need to restart Crowd once you've edited the cookie.tokenkey property.
As crowd.properties is a standard Java Properties file, both formats are accepted but I guess you should use the equal character so as to remain consistent with the rest of the file.
Do not touch the session.tokenkey property, it's all about the cookie.tokenkey property here.
It should work out of the box.
You might want to take a look at Atlassian documentation: https://confluence.atlassian.com/crowd/the-crowd-properties-file-98665664.html
My guess is that you might have edited the wrong crowd.properties file on your Crowd instance (the right one is in your crowd.home directory).
I suggest that you raise a support ticket if it still does not work.