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,556,176
Community Members
 
Community Events
184
Community Groups

how to force Bitbucket dashboard session logout after x time of inactivity.

Edited

We are upgrading BBDC from 6.9 to 8.9 and as per the security recommendation we need to implement the session timeout to 15 min.
We have removed the "keep me logged in" and impemened "server.session.timeout" to 15 min, but it only logs out if the browser is closed and if the browser/Tab is open(without any activity), it will not log out even after 15-20 min.
Can i know if there is any solution for this?

1 answer

0 votes
Victor Menes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 08, 2023

Hey Diju,

 

Thank you for submitting your doubt here :)

 

I will try to give you useful information so you could get this sorted out. Below are a couple possible causes for the issue you've reported. Additional information can be found here as well - Bitbucket Server Session does not expire after configured timeout 

  • The login screen might have the "remember me" checkbox marked.
  • If using clustering, each node has it's own web.xml and changes may not be in sync.
  • The load balancer has session affinity enabled
  • The user may be active the entire time which will cause them to not be logged out

 

Would you be able to take a look on these and see if that helps?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events