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
According to the spec, it seems optional (note the "if a nonce value was sent..."):
If a nonce value was sent in the Authentication Request, a nonce Claim MUST be present and its value checked to verify that it is the same value as the one that was sent in the Authentication Request. The Client SHOULD check the nonce value for replay attacks. The precise method for detecting replay attacks is Client specific.
These providers are simply not OIDC compliant, as already cited above:
If a nonce value was sent in the Authentication Request, a nonce Claim MUST be present and its value checked to verify that it is the same value as the one that was sent in the Authentication Request.
This library always sends the nonce, so it is required to expect it in the response.
The implementation here assumes that
nonce
is always present in the claim:https://github.com/jumbojett/OpenID-Connect-PHP/blob/master/src/OpenIDConnectClient.php#L922
However, some providers do not return a nonce here. For example, Intuit's implementation does not: https://developer.intuit.com/app/developer/qbo/docs/develop/authentication-and-authorization/openid-connect
According to the spec, it seems optional (note the "if a nonce value was sent..."):
From: https://openid.net/specs/openid-connect-core-1_0.html#IDTokenValidation
The text was updated successfully, but these errors were encountered: