While trying to implement some form of session control on Hipchat, it was found that user logins persist after a service stop/start with over an hour between stoppage and starting again.
As in, I am logged into Hipchat, I stop the service via command line, wait an hour to start it up again, then when I refresh the page, Hipchat loads without asking me to login like I was expecting(hoping) it would.
I have been pondering your question and bouncing it off HipChat support. We are not clear whether you are shutting down the HipChat server service via command line or if you are closing your client for an hour.
Closing the app on your local machine doesn't log you out, so if you are stopping the client service via command line it is expected that the login will persist. The best way to end the session is to log out.
I actually have found a way to log out users at time of day.
Feel free to pass it around. This is all added to the crontab in the hipchat server command line.
service hipchat stop
redis-cli keys websession* | xargs redis-cli del
redis-cli keys OauthSession* | xargs redis-cli del
redis-cli keys moble* | xargs redis-cli del
service hipchat start
...from the beginning. We have built up a lot of content in HipChat, with it being a core tool in our distributed company model. While it is true that we didn’t need to move to Slack immediately, we felt it...
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