We often have the problem that StoreFront thinks the user is already logged in. This is probably caused by a cookie from the previous day, even though the browser session was closed and the PC was restarted. According to the browser, the cookie should be valid only until the end of the browser session, but it still exists. In this case, StoreFront assumes that the user is logged in. One noticeable symptom is that the user name is missing in the header area where it normally says “Good morning John Doe”. Resources cannot be launched. Only after the user manually deletes the ASP.NET_SessionID cookie does StoreFront prompt for login again, and the user is then able to launch resources successfully.

Is the browser configured to re-open tabs on start-up? If so, the browser will store the session cookies and the content of the web page. Is the user actually still authenticated or is it just showing a cached version of the page? I.e. if the user refreshes the page does it refresh or are they re-directed to the authentication screen? What auth method are they using? Is there a NetScaler gateway involved? Normally inactivity or forced timeouts would cause the use to be logged out if they have been inactive over night but it depends on how it's been configured. See https://docs.citrix.com/en-us/storefront/current-release/stores/websites/session-settings.

@Jonathan Adams NetScaler Gateway is in place, but in this case client is internal and connects directly to Storefront. However "Fully trust Netscaler..." Checkbox is enabled When hitting F5 or Ctrl.+F5, the tab reloads the Storefront site and the user is still "partly" logged in. The App-Icons show up and the only difference, where we can see the bad behaviour is "Good Morning" instead of "Good Morning, John Doe" If the user starts an app, nothing happens, this error appears in the bottom left:

What StoreFront version is this?

latest SF: 2507.0.100.141, Timeouts are default: