You are viewing documentation for KubeSphere version:v3.0.0
KubeSphere v3.0.0 documentation is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the latest version.
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.
Inactivity Session Timeout
You can control when an inactive user 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.
JWT Signature Verification Failed
In a multi-cluster environment,
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.