[Feature] Use the nonce parameter in OIDC authorization request to mitigate replay attacks

[jirutka]

Use case

The nonce parameter is used to mitigate replay attacks. It’s not required by the OpenID Connect Core specification, but it’s required by some OIDC/OAuth profiles, e.g. Financial-grade API Security Profile 1.0 and FAPI 2.0 Security Profile.

Description

OpenID Connect Core 1.0 – 3.1.2.1 Authentication Request:

nonce String value used to associate a Client session with an ID Token, and to mitigate replay attacks. The value is passed through unmodified from the Authentication Request to the ID Token. Sufficient entropy MUST be present in the nonce values used to prevent attackers from guessing values. For implementation notes, see Section 15.5.2.

Contribution

• I can write the design doc for this feature
• I can contribute this feature

How can it be implemented?

No response

[kradalby]

There is a PR open for PCKE, which I think is to cover MitM and not replay, is this somehow related still? #1812

Any references to how others implement this in go would also be appreciated as reading spec and reversing it is very time consuming.