Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,467,408
Community Members
 
Community Events
177
Community Groups

How to save login session after browser window closed

I would like to configure my applications (Crucible & Fisheye, Confluence, Jira, Bamboo all of which use Crowd with the SSO option) to persist their login information across having the browser window closed. Is this possible?

I have verified that cookies are not being auto deleted by the browser when the window is closed however the sessions aren't persisting. I'm not seeing a ready way to address this in the documentation. I have already increased the session timeout to one day which should be the frequency my users need to log in.

Each application is running on a dedicated box, mostly Linux based. The context for all applications (other than bamboo) is set to be the root.

1 answer

Hi Tim,

Actually this problem is related with the context path. Basically it seems that all the requests are coming from one host. For example, http://localhost:8085 -> Confluence http://localhost:8090 -> JIRA http://localhost:8095 -> Bamboo.

We have to create a context path, making Confluence be like this: http://localhost:8085/Confluence JIRA: http://localhost:8090/JIRA, that why Crowd will know which cookie to get.

To create a context path for Confluence you should check this documentation: https://confluence.atlassian.com/display/DOC/Using+Apache+with+mod_proxy

For Bamboo:
https://confluence.atlassian.com/display/BAMBOO/Changing+the+Root+Context+Path

For Fisheye:
https://confluence.atlassian.com/display/FISHEYE/Configuring+the+FishEye+web+server

For JIRA:
https://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+Apache

I hope this helps.

Cheers,

WZ

My applications each have a dedicated server to support them and none are using Apache as a front end. As such I specifically want to keep the context path as root for these hosts. Any other suggestions?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events