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
When using primitives like OIDCUserInfoSignedResponseAlg the RP should verify that the received response has actually been signed with the listed algorithm(s).
Actual behaviour
If one sets for instance value RS256 for the OIDCUserInfoSignedResponseAlg the RP is able to handle the incoming signed response and validate it but it does not verify the algorithm is actually RS256.
Minimized example
Configuration and Apache server log files
The text was updated successfully, but these errors were encountered:
It turns out that this is actually a spec requirement, as follows out of this discussion: openid-certification/oidctest#207 so I'm reclassifying as a bug that needs to be addressed for the next release.
Environment
Any
Expected behaviour
When using primitives like OIDCUserInfoSignedResponseAlg the RP should verify that the received response has actually been signed with the listed algorithm(s).
Actual behaviour
If one sets for instance value RS256 for the OIDCUserInfoSignedResponseAlg the RP is able to handle the incoming signed response and validate it but it does not verify the algorithm is actually RS256.
Minimized example
Configuration and Apache server log files
The text was updated successfully, but these errors were encountered: