A cloud-based identity and access management service for securing user authentication and resource access
@LYassine , Thanks for reaching out and apologies for the delay in response.
By tracking the details from the backend for your tenant based on the correlation ID and the timeframe of the error you have provided, I see some exception related to date and time of issued token as you could see below, an issued token was just valid for 2 minutes from issinst:2022-03-09T16:57:34Z to naf:2022-03-09T16:59:34Z which I feel very short duration so wondering any specific reason why your IDP sent token with shorter duration ? Ideally SAML token validity is 1 hour with Azure AD scenario.
ValidateSamlToken failed. Assertion: {"iss":"https://localhost:6500","issinst":"2022-03-09T16:57:34Z","naf":"2022-03-09T16:59:34Z","aud":["urn:federation:MicrosoftOnline"]}
Additionally, I would request you to ensure if identity provider is sending proper values in the following fields in the token IssueInstant , NotBefore , NotOnOrAfter , saml:Audience as urn:federation:MicrosoftOnline and, make sure identity provider is using the right key algorithm for signing token like RSA. Here's sample-token.xml for reference which you can use to compare non-working token. For detailed information about compatibility, see Azure AD federation compatibility list and Azure AD identity provider compatibility docs when using custom IDP for SSO.
Hope this helps.