+V10.5 OIDC Client
---+V10.5.1 Verify that the client (as the relying party) mitigates ID Token replay attacks. For example, by …
---+V10.5.2 Verify that the client uniquely identifies the user from ID Token claims, usually the 'sub' claim …
---+V10.5.3 Verify that the client rejects attempts by a malicious authorization server to impersonate another …
---+V10.5.4 Verify that the client validates that the ID Token is intended to be used for that client …
---+V10.5.5 Verify that, when using OIDC back-channel logout, the relying party mitigates denial of service …

V10.5 OIDC Client

As the OIDC relying party acts as an OAuth client, the requirements from the section "OAuth Client" apply as well.

Note that the "Authentication with an Identity Provider" section in the "Authentication" chapter also contains relevant general requirements.

1. Visão geral

Título Norma
V10.5.1 Verify that the client (as the relying party) mitigates ID Token replay attacks. For example, by …

Verify that the client (as the relying party) mitigates ID Token replay attacks. For example, by ensuring that the 'nonce' claim in the ID Token matches the 'nonce' value sent in the authentication request to the OpenID Provider (in OAuth2 refereed to as the authorization request sent to the authorization server).

V10.5.2 Verify that the client uniquely identifies the user from ID Token claims, usually the 'sub' claim …

Verify that the client uniquely identifies the user from ID Token claims, usually the 'sub' claim, which cannot be reassigned to other users (for the scope of an identity provider).

V10.5.3 Verify that the client rejects attempts by a malicious authorization server to impersonate another …

Verify that the client rejects attempts by a malicious authorization server to impersonate another authorization server through authorization server metadata. The client must reject authorization server metadata if the issuer URL in the authorization server metadata does not exactly match the pre-configured issuer URL expected by the client.

V10.5.4 Verify that the client validates that the ID Token is intended to be used for that client …

Verify that the client validates that the ID Token is intended to be used for that client (audience) by checking that the 'aud' claim from the token is equal to the 'client_id' value for the client.

V10.5.5 Verify that, when using OIDC back-channel logout, the relying party mitigates denial of service …

Verify that, when using OIDC back-channel logout, the relying party mitigates denial of service through forced logout and cross-JWT confusion in the logout flow. The client must verify that the logout token is correctly typed with a value of 'logout+jwt', contains the 'event' claim with the correct member name, and does not contain a 'nonce' claim. Note that it is also recommended to have a short expiration (e.g., 2 minutes).

1.1 Referências

1.2 Requisitos identificados

1.3 Regulamentos relacionados

2. Requisitos identificados

Requisitos
Fonte Requisito

3. Regulamentos relacionados

Regulamentos
Fonte Regulamentação
  • OWASP -

    EN: Publications of the OWASP Foundation, https://owasp.org/. OWASP® is a registered trademark of the OWASP Foundation, Inc.; GRCA is not affiliated with, nor endorsed by, the OWASP Foundation. Only the versions published by OWASP are authoritative.

    DE: Veröffentlichungen der OWASP Foundation, https://owasp.org/. OWASP® ist eine eingetragene Marke der OWASP Foundation, Inc.; GRCA steht in keiner Verbindung zur OWASP Foundation und wird von ihr nicht unterstützt. Maßgeblich sind allein die von OWASP veröffentlichten Fassungen.