After upgrading to NCM 25.4.5 we have noticed several different occurrences for different users, that while their session was active, they would be automatically logged out and would have to login back again.
NCM 25.4.5
NCM Webapp (Browser Client)
The root cause appears to be that the server-side keep-alive mechanism only refreshes one of the multiple authentication cache entries created during a Webswing login, allowing the remaining entries to expire and trigger a forced logout.
This will be fixed in a future NCM release.
This can be tracked in issues resolved under DE183992