Overview#
REQUIRED or the terms "MUST" or "SHALL", mean that the definition is an absolute requirement of the specification. (RFC 2119)An implementation which does not include this particular option MUST be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality.
In the same vein an implementation which does include this particular option MUST be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides.)
We may use REQUIRED in other contexts but we are implying the same interpretation as a Best Current Practice
More Information#
There might be more information for this subject on one of the following:- Acr_values
- Authentication
- Authentication Request
- Authorization Request Parameters
- C_hash
- Check_session_iframe
- Claimed Https Scheme URI Redirection
- ClientHello
- Custom URI scheme
- DID descriptor objects
- Default Profile Claims
- End_session_endpoint
- GCP IAM Policy
- Id_token_encrypted_response_alg
- Id_token_signed_response_alg
- Id_token_signing_alg_values_supported
- JWK Set
- Login_hint_token
- Logout Token
- MUST
- Naming Attributes
- OAuth 2.0 Security Best Current Practice
- OAuth 2.0 Token Revocation
- OAuth Token Response
- OMSyntax
- OpenID Connect Federation
- OpenID Connect MODRNA Authentication Profile 1.0
- OpenID Connect Scopes
- OpenID Connect Standard Claims
- Openid scope
- Openid-configuration
- Password MUST Change
- Proof Key for Code Exchange by OAuth Public Clients
- RFC 2119
- Reciprocal OAuth
- Revocation Request
- SCIM Common Attribute
- SCIM Query parameters
- SCIM Schemas Attribute
- SHALL
- Security Token
