| ConsentDefinition | Defines the details of user consents required for specific scopes and resources. This record is used to manage and validate user consent for accessing specific scopes, resources, and RFC 9396 Rich Authorization Requests entries, ensuring that consent is explicitly granted according to the requirements of the application and compliance standards. |
| NullConsentService | Default no-op consent provider that auto-grants every requested scope and resource and never marks consent as pending. Suitable for trusted first-party deployments and as the starting placeholder during integration; replace with a host-supplied implementation to honour OIDC Core §3.1.2.4 (authorization server obtains end-user consent). |
| PromptConsentDecorator | Honours the OIDC Core §3.1.2.1 prompt=consent parameter by short-circuiting the wrapped IUserConsentsProvider: when the client explicitly requests consent re-confirmation, every requested scope and resource is forced into the pending bucket so the consent UI is shown even if the user previously granted it. For any other prompt value the decorator delegates to the inner provider unchanged. |
| UserConsents | Represents the state of user consents in an authorization flow, categorizing them into granted, denied, and pending. |