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

## Abblix\.Oidc\.Server\.Endpoints\.UserInfo Namespace

| Classes | |
| :--- | :--- |
| [UserInfoHandler](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Endpoints.UserInfo.UserInfoHandler 'Abblix\.Oidc\.Server\.Endpoints\.UserInfo\.UserInfoHandler') | Handles user information requests in an OpenID Connect compliant manner\. It ensures that requests for user info are correctly validated and processed, returning the requested user information if the request is authorized\. |
| [UserInfoRequestProcessor](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Endpoints.UserInfo.UserInfoRequestProcessor 'Abblix\.Oidc\.Server\.Endpoints\.UserInfo\.UserInfoRequestProcessor') | Default [IUserInfoRequestProcessor](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Endpoints.UserInfo.Interfaces.IUserInfoRequestProcessor 'Abblix\.Oidc\.Server\.Endpoints\.UserInfo\.Interfaces\.IUserInfoRequestProcessor'): assembles the UserInfo claims set from [IUserClaimsProvider](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.UserInfo.IUserClaimsProvider 'Abblix\.Oidc\.Server\.Features\.UserInfo\.IUserClaimsProvider'), filtered by the access token's authorized scopes and any `userinfo` entry of the OIDC Core §5\.5 `claims` request\. Returns [InvalidToken](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Common.Constants.ErrorCodes#Abblix.Oidc.Server.Common.Constants.ErrorCodes.InvalidToken 'Abblix\.Oidc\.Server\.Common\.Constants\.ErrorCodes\.InvalidToken') if no claims are produced for the subject\. |
| [UserInfoRequestValidator](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Endpoints.UserInfo.UserInfoRequestValidator 'Abblix\.Oidc\.Server\.Endpoints\.UserInfo\.UserInfoRequestValidator') | Validates a UserInfo request: extracts the access token \(per RFC 6750, either the `Authorization: Bearer` header or the `access_token` form/query parameter, but not both\), verifies its JWT signature and claims, asserts the `typ` header equals `at+jwt`, and resolves the originating authentication session, authorization context and client\. |