Users logged out of web interface too soon

Question

We have recently upgraded from 11.5 to 14.5.14503. Everything seems to work fine, except for one irritating thing: the users have to log every day in when visiting the Collaborator interface. This was not the case in Collaborator 11.5, where users rarely had to log in again.Is there a specific setting for this?&nbsp;&nbsp;

faiqarani · Answer

It sounds like you're experiencing an issue with session persistence or authentication settings in your upgrade to Collaborator 14.5.14503. In older versions like 11.5, sessions might have been set to last longer, allowing users to stay logged in for extended periods.To address this in version 14.5.14503, you'll want to check the session timeout settings. Look for options related to session duration or authentication token expiration in the Collaborator configuration. Adjusting these settings to align with your previous setup can help maintain longer user sessions, reducing the frequency of login prompts.Remember to consider security implications when adjusting session durations, as longer sessions can pose a risk if not properly managed. Aim for a balance between user convenience and security best practices.

larswjoh · Answer

Thank you for the response.I have been in contact with Smartbear support och they replied that this timeout value is hard-coded into the application. However, they are investigating if it is feasible to implement a setting for it so that it can be adjusted in a future release.

yasmiqu · Answer

While Collaborator 11.5 had more persistent logins, newer versions may have different default settings or configurations that are impacting the session duration.Here are a few potential causes and fixes:Session Timeout Settings: Collaborator 14.5 likely has different session timeout or cookie settings compared to version 11.5. You can adjust the session timeout settings in the system configuration, which controls how long the session stays active before requiring a re-login. Check the Session Timeout or Idle Timeout settings in the admin console or server configuration files.Cookie Configuration: In some cases, cookie handling might be stricter in newer versions, causing the login session to expire sooner. Ensure that your system allows persistent cookies, and check if any new cookie-related security features in version 14.5 need to be adjusted.Authentication and Single Sign-On (SSO): If you're using an SSO system or external authentication (like LDAP or Active Directory), verify that the integration settings are correctly configured to maintain session persistence across user sessions. Newer versions may have different integration protocols that need fine-tuning.Browser or Cache Issues: Sometimes, a change in the Collaborator version could coincide with changes in browser caching behavior. Ensure that your users' browsers are properly caching authentication cookies and sessions. Clearing browser cache or using a different browser might resolve the issue temporarily.Server Configuration: There may be server-side changes in version 14.5 that affect how sessions are managed. Review the server logs for any errors or warnings related to session management or authentication failures.

john_d · Answer

we have this version, and the only way collaborator (by itself) will log anyone out is if they close all of their browser windows related to collaborator.&nbsp; I suspect your IT area has instituted a method to log individuals out, or to remove cache data from your browsers.