We have suffered from this issue before when setting up a new project on Azure.
Old thread:
https://discord.com/channels/869656431308189746/1183873525031911554
Now, we are seeing this issue on local development on localhost:8080 on a project where we're upgrading from Umbraco 10 to 13.
After logging into the CMS, there is about a 40-60 second wait. Then there is a call to
/umbraco/backoffice/umbracoapi/authentication/GetRemainingTimeoutSeconds
that returns:
)]}',
0.0
Upon which the user is logged out showing message "Session timed out."
We have tried using incognito mode to rule out cookies, as well as completely fresh browser profile in Chrome.
Are we missing something completely basic for this problem to occur?
appsetting Umbraco.CMS.Global.TimeOut is set to
08:00:00
. 8 hours is more than 1 minute.
We have not supplied any other setting that should affect this. In our previous 'fresh' project the settings were also default.
Umbraco.CMS.Security.KeepUserLoggedIn is not set to
true
thus it should be interpreted as the default
false
.
> When set to false a user will be logged out after a specific amount of time has passed with no activity. You can specify this time span in the global settings with the TimeOut key.
This is exactly what we've done.
Umbraco.CMS.Security.AllowConcurrentLogins is showing a bit of a strange behavior.
We don't have this defined at all. But setting it to true, and then restarting Umbraco, and then simply
reloading the browser window of the recently auto-logged out user in a fresh browser profile will automatically log them in and show the backoffice.
Logging out above mentioned user and then logging in seems to work fine as well.
GetRemainingTimeoutSeconds
returns the full 8 hours.
However, logging out, setting
AllowConcurrentLogins
to false again and then logging back in, the problem reappears.
In our tests, this is the only browser window using the site. Why are we seeing this problem?