Version Affected: 9.0.2, 9.1, 9.2
When setting a non integer value for "SAML Valid Hours" on a WSFed realm (e.g. 0.25 for 15 minutes)
the realm will produce this error on post authentication
and the following can be observed in the debug log:
LogChannel="SA_DEBUG" FormatVersion="0.0.1" EventID="40999" Timestamp="2020-07-13T10:50:24.860Z" CompanyID="" ApplianceID="" Realm="" UserID="" BrowserSession="" StateMachineID="" RequestID="" UserHostAddress="" Message="[WSFedService].[Start]: Exception occurred, System.IdentityModel.Protocols.WSTrust.InvalidRequestException: ID2077: The computed lifetime has a creation time of '13/07/2020 10:50:24' and an expiration time of '13/07/2020 10:50:24'. The expiration time is before or equal to the creation time. If you need to specify such a lifetime, override SecurityTokenService.GetTokenLifetime and provide custom verification.
at System.IdentityModel.SecurityTokenService.VerifyComputedLifetime(DateTime created, DateTime expires)
at System.IdentityModel.SecurityTokenService.GetTokenLifetime(Lifetime requestLifetime)
at System.IdentityModel.SecurityTokenService.Issue(ClaimsPrincipal principal, RequestSecurityToken request)
at System.IdentityModel.Services.FederatedPassiveSecurityTokenServiceOperations.ProcessSignInRequest(SignInRequestMessage requestMessage, ClaimsPrincipal principal, SecurityTokenService sts, WSFederationSerializer federationSerializer)
at SecureAuth.IdentityModel.WSFederation.WSFedService.StartSignIn(SignInRequestMessage msg, GenericPrincipal gp)
Product Defect EE-532 & EE-1830
Addressed in the following hotfix packages:
IdP version 9.3, 19.07+ are unaffected as the fix is already incorporated into the main code.
SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.
Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.
Please sign in to leave a comment.