#### [Abblix\.Oidc\.Server](https://www.abblix.com/en/docs/api/abblix-oidc-server 'index')

## Abblix\.Oidc\.Server\.Features\.ClientInformation Namespace

| Classes | |
| :--- | :--- |
| [ClientInfo](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.ClientInformation.ClientInfo 'Abblix\.Oidc\.Server\.Features\.ClientInformation\.ClientInfo') | Contains information about a client in an OAuth2/OpenID Connect context\. |
| [ClientKeysProvider](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.ClientInformation.ClientKeysProvider 'Abblix\.Oidc\.Server\.Features\.ClientInformation\.ClientKeysProvider') | Facilitates the retrieval of JSON Web Keys \(JWKs\) for cryptographic operations, including encryption and signing\. This provider supports fetching keys from a client's JSON Web Key Set \(JWKS\) URL or directly from the client configuration\. |
| [ClientSecret](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.ClientInformation.ClientSecret 'Abblix\.Oidc\.Server\.Features\.ClientInformation\.ClientSecret') | Encapsulates the details of a client secret used in OAuth2 and OpenID Connect authentication flows\. |
| [OidcOptionsSecurityProfileValidator](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.ClientInformation.OidcOptionsSecurityProfileValidator 'Abblix\.Oidc\.Server\.Features\.ClientInformation\.OidcOptionsSecurityProfileValidator') | Validates that every statically\-configured client whose effective profile mandates a control bundle has a configuration that can satisfy it, failing loudly the first time [OidcOptions](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Common.Configuration.OidcOptions 'Abblix\.Oidc\.Server\.Common\.Configuration\.OidcOptions') is resolved rather than letting a contradiction surface as a per\-request rejection at runtime\. A no\-op for deployments that select no profile, so existing configurations are unaffected\. |
| [SecurityProfileConsistency](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.ClientInformation.SecurityProfileConsistency 'Abblix\.Oidc\.Server\.Features\.ClientInformation\.SecurityProfileConsistency') | Checks whether a client's configuration can actually satisfy the profile it selects, so a contradiction surfaces loudly at registration or startup instead of as a per\-request rejection the operator has to reverse\-engineer\. The runtime validators already tighten a request to the profile; this is the fail\-loud companion that catches static configuration that can never produce a conformant flow in the first place\. |
| [SecurityProfileRequirements](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.ClientInformation.SecurityProfileRequirements 'Abblix\.Oidc\.Server\.Features\.ClientInformation\.SecurityProfileRequirements') | The bundle of controls a [ClientSecurityProfile](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Common.Constants.ClientSecurityProfile 'Abblix\.Oidc\.Server\.Common\.Constants\.ClientSecurityProfile') forces on a client, expressed as individual flags the request\-pipeline validators consult\. This is the single place the profile\-to\-controls mapping lives, so a validator never needs to know what "FAPI 2\.0" means — it only reads the one flag it owns — and adding a future profile touches only [Resolve\(ClientSecurityProfile\)](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.ClientInformation.SecurityProfileRequirements#Abblix.Oidc.Server.Features.ClientInformation.SecurityProfileRequirements.Resolve(Abblix.Oidc.Server.Common.Constants.ClientSecurityProfile) 'Abblix\.Oidc\.Server\.Features\.ClientInformation\.SecurityProfileRequirements\.Resolve\(Abblix\.Oidc\.Server\.Common\.Constants\.ClientSecurityProfile\)')\. |
| [TlsClientAuthOptions](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.ClientInformation.TlsClientAuthOptions 'Abblix\.Oidc\.Server\.Features\.ClientInformation\.TlsClientAuthOptions') | RFC 8705 metadata for tls\_client\_auth method\. Defines match rules for Subject DN and/or Subject Alternative Name entries\. |

| Interfaces | |
| :--- | :--- |
| [IClientInfoManager](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.ClientInformation.IClientInfoManager 'Abblix\.Oidc\.Server\.Features\.ClientInformation\.IClientInfoManager') | Defines operations for managing the lifecycle and information of OAuth 2\.0 clients in a storage system\. |
| [IClientInfoProvider](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.ClientInformation.IClientInfoProvider 'Abblix\.Oidc\.Server\.Features\.ClientInformation\.IClientInfoProvider') | Provides access to OAuth 2\.0 client information, enabling the retrieval of client details by client ID\. |
| [IClientKeysProvider](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.ClientInformation.IClientKeysProvider 'Abblix\.Oidc\.Server\.Features\.ClientInformation\.IClientKeysProvider') | Provides access to cryptographic keys for OpenID Connect clients, supporting token encryption and signature validation\. |