Timeout / Session Expired should be longer
under review
Z
Zinc Anteater
I've noticed that, at least on occasion, if I'm away from the KB for maybe an hour or so, that I see a SESSION EXPIRED window when I return. Can this timeout be increased to something like 8 hours? Or maybe have an option under SETTINGS that a KB owner/contributor can set? Thanks.
Log In
C
Coherent Hummingbird
I was literally logged out just then while I was in the middle of typing a sentence. I keep getting session expired messages all the time. This might be because I often have multiple 360 tabs open at the same time and it is possibly timing out one, which then logs out the other? Either way, I wish it would stop.
Also, seconding the comment below: being kicked back to the dashboard each time and then having to navigate back to the document/workspace I was working on is very frustrating.
M
Minimum Hedgehog
Adding to this discussion: it's my opinion it should be up to us to decide when we want our sessions to timeout for both the Site and the Portal. I have just begun using the new Portal UI and I find it frustrating that after some time, I am completely logged out without the option to refresh as in the older version. With the older version, no matter how long I was away, I could refresh and go back to the article I was working on. Now, with the new UI, after some time, I am logged out and taken back to the Dashboard. Prefer the way refreshing was handled in the old UI.
H
Heliotrope Parrotfish
I think it would be best if you customized this option, giving a minimum and maximum, with default value. For many 60 minutes is enough. For others, more time is needed.
M
Magnificent Grasshopper
marked this post as
under review
M
Magnificent Grasshopper
Zinc Anteater It's a security mechanism to make the KB accesss more secure. For Private KB, the search key validity expires in 60 minutes of being idle.
B
Bastille Minnow
Magnificent Grasshopper: Can you add this information as a note or tooltip to the Settings > Users and Security > Enterprise SSO > Advanced Settings section? As it is today, it looks like we can adjust this. I have ours set to 23 hours, but I didn't know you had different overriding logic on the backend. This has been pretty frustrating and I even submitted a support ticket on it that they were unable to solve. Having this info in the UI would have saved a lot of time.