You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Caught Exception "EngineBlock_Corto_Module_Bindings_VerificationException":"Received an assertion that has expired. Check clock synchronization on IdP and SP.", redirecting to route "authentication_feedback_verification_failed"
The exception description is very useful because this is a common error. However, EB only presents the abstract error "Invalid Identity Provider Response" (related to the VerificationException). It would be helpful if EB could be explicit to the user that it rejects the assertion due to a clock issue.
The text was updated successfully, but these errors were encountered:
When the received assertion is not valid, EB logs
The exception description is very useful because this is a common error. However, EB only presents the abstract error "Invalid Identity Provider Response" (related to the VerificationException). It would be helpful if EB could be explicit to the user that it rejects the assertion due to a clock issue.
The text was updated successfully, but these errors were encountered: