Error validating users agent
User Strong Auth Client Auth NRequired - Due to a configuration change made by the admin, or because you moved to a new location, the user must use multi-factor authentication to access the resource.
Retry with a new authorize request for the resource.
When you receive this status, follow the location header associated with the response.
This might be because there was no signing key configured in the app.
Check out the resolutions outlined at https://docs.microsoft.com/azure/active-directory/application-sign-in-problem-federated-sso-gallery#certificate-or-key-not-configured.
If you still see issues, contact the app owner or an app admin.
This is a common error that's expected when a user is unauthenticated and has not yet signed in.
If this error is encouraged in an SSO context where the user has previously signed in, this means that the SSO session was either not found or invalid.
Session mismatch - Session is invalid because user tenant does not match the domain hint due to different resource.