Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

195 views 6 7
Read article

Community Events

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

Events near you