Skip to main content
Veteran
August 13, 2026
Question

SSO token issue after upgrading Appliance/BeyondInsight

  • August 13, 2026
  • 1 reply
  • 15 views

I have recently upgraded my Appliance version and BeyondInsight/Password Safe version with below

  • Password Safe Appliance 4.4.1.1317 → 4.6.1.155
  • BeyondInsight 25.1.1.165 → 26.1.0.878

Upgrade was successful. The following day, my users started receiving an SSO authentication failed error from their browsers. It seems like there was a token lifetime validation happening and it is now failing against my users. Clearing the browser cache and deleting the previous token somewhat helped but this is more of a manual intervention per user I am doing now. Has anybody encountered this and know how to resolve this?

Microsoft.IdentityModel.Tokens.SecurityTokenExpiredException: IDX10223: Lifetime validation failed. The token is expired. ValidTo (UTC): '8/13/2026 9:26:02 PM', Current time (UTC): '8/13/2026 9:51:55 PM'. at Microsoft.IdentityModel.Tokens.ValidatorUtilities.ValidateLifetime(Nullable`1 notBefore, Nullable`1 expires, SecurityToken securityToken, TokenValidationParameters validationParameters) at Microsoft.IdentityModel.Tokens.Validators.ValidateLifetime(Nullable`1 notBefore, Nullable`1 expires, SecurityToken securityToken, TokenValidationParameters validationParameters) at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateLifetime(Nullable`1 notBefore, Nullable`1 expires, JwtSecurityToken jwtToken, TokenValidationParameters validationParameters) at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateTokenPayload(JwtSecurityToken jwtToken, TokenValidationParameters validationParameters, BaseConfiguration configuration) at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateJWS(String token, TokenValidationParameters validationParameters, BaseConfiguration currentConfiguration, SecurityToken& signatureValidatedToken, ExceptionDispatchInfo& exceptionThrown) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateToken(String token, JwtSecurityToken outerToken, TokenValidationParameters validationParameters, SecurityToken& signatureValidatedToken) at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateToken(String token, TokenValidationParameters validationParameters, SecurityToken& validatedToken) at BeyondTrust.BeyondInsight.WebConsole.SSOHelper.SSOJwtTokenService.ValidateToken(String token, String audience, String issuer)

    1 reply

    tclowater
    BeyondTrust Employee
    BeyondTrust Employee
    August 14, 2026

    Yes, has been a challenge for certain environments where the cache isn’t set to clear on close, and there’s no magic I’m aware of to force this as it can be environment dependent.