Session Timeout
A session starts as a user logs in to the console of KubeSphere. You may see a message of “Session timeout or this account is logged in elsewhere, please login again” when the session expires.
Session Timeout
You can control when a session expires. The default session timeout is two hours of inactivity. It means once the session timeout is reached, the user will be automatically logged out of the console. You can configure accessTokenMaxAge and accessTokenInactivityTimeout for the session timeout.
Signature Verification Failed
In a multi-cluster environment, clusterRole and jwtSecret must be set correctly.
Node Clock Skew
The node clock skew affects time-sensitive operations such as validating the expiration time of a user token. You can configure the server time synchronization with an NTP server. MaximumClockSkew can also be set, which defaults to 10 seconds.
Feedback
Was this page Helpful?
Thanks for the feedback. If you have a specific question about how to use KubeSphere, ask it on Slack. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.
Previous
What’s on this Page