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

## Abblix\.Oidc\.Server\.Mvc\.Model Namespace

| Classes | |
| :--- | :--- |
| [AuthorizationRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server-mvc/Abblix.Oidc.Server.Mvc.Model.AuthorizationRequest 'Abblix\.Oidc\.Server\.Mvc\.Model\.AuthorizationRequest') | The transport\-bound counterpart of [AuthorizationRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Model.AuthorizationRequest 'Abblix\.Oidc\.Server\.Model\.AuthorizationRequest') for the authorization endpoint\. All bound properties, their model binders, validation attributes and the projection back onto the core model are generated from the core type and its declarative markers\. |
| [BackChannelAuthenticationRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server-mvc/Abblix.Oidc.Server.Mvc.Model.BackChannelAuthenticationRequest 'Abblix\.Oidc\.Server\.Mvc\.Model\.BackChannelAuthenticationRequest') | The transport\-bound counterpart of [BackChannelAuthenticationRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Model.BackChannelAuthenticationRequest 'Abblix\.Oidc\.Server\.Model\.BackChannelAuthenticationRequest') for the CIBA backchannel authentication endpoint\. All bound properties, model binders resolved from the core wire\-format markers and the projection back onto the core model are generated from the core type\. |
| [ClientAuthorizationRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server-mvc/Abblix.Oidc.Server.Mvc.Model.ClientAuthorizationRequest 'Abblix\.Oidc\.Server\.Mvc\.Model\.ClientAuthorizationRequest') | Authorizes permission to manage a client per RFC 7592 Dynamic Client Registration Management Protocol\. Identifies the client and provides authentication credentials without dictating the management action\. The actual operation \(read, update, or delete\) is determined by the HTTP verb\. |
| [ClientRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server-mvc/Abblix.Oidc.Server.Mvc.Model.ClientRequest 'Abblix\.Oidc\.Server\.Mvc\.Model\.ClientRequest') | The transport\-bound counterpart of [ClientRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Model.ClientRequest 'Abblix\.Oidc\.Server\.Model\.ClientRequest'): the client authentication material accompanying back\-channel endpoint payloads\. The body\-level credential parameters, the header and TLS\-connection sources resolved from the core transport\-source markers, and the projection back onto the core model are generated from the core type\. |
| [DeviceAuthorizationRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server-mvc/Abblix.Oidc.Server.Mvc.Model.DeviceAuthorizationRequest 'Abblix\.Oidc\.Server\.Mvc\.Model\.DeviceAuthorizationRequest') | The transport\-bound counterpart of [DeviceAuthorizationRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Model.DeviceAuthorizationRequest 'Abblix\.Oidc\.Server\.Model\.DeviceAuthorizationRequest') for the device authorization endpoint \(RFC 8628\)\. All bound properties, model binders resolved from the core wire\-format markers and the projection back onto the core model are generated from the core type\. |
| [EndSessionRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server-mvc/Abblix.Oidc.Server.Mvc.Model.EndSessionRequest 'Abblix\.Oidc\.Server\.Mvc\.Model\.EndSessionRequest') | The transport\-bound counterpart of [EndSessionRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Model.EndSessionRequest 'Abblix\.Oidc\.Server\.Model\.EndSessionRequest') for the RP\-initiated logout endpoint, reachable via GET and POST\. The bound properties, model binders resolved from the core wire\-format markers and the projection back onto the core model are generated from the core type; the cross\-property validation below stays hand\-written because it spans several parameters at once\. |
| [IntrospectionRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server-mvc/Abblix.Oidc.Server.Mvc.Model.IntrospectionRequest 'Abblix\.Oidc\.Server\.Mvc\.Model\.IntrospectionRequest') | The transport\-bound counterpart of [IntrospectionRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Model.IntrospectionRequest 'Abblix\.Oidc\.Server\.Model\.IntrospectionRequest') for the token introspection endpoint \(RFC 7662\)\. All bound properties, validation attributes and the projection back onto the core model are generated from the core type\. |
| [RevocationRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server-mvc/Abblix.Oidc.Server.Mvc.Model.RevocationRequest 'Abblix\.Oidc\.Server\.Mvc\.Model\.RevocationRequest') | The transport\-bound counterpart of [RevocationRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Model.RevocationRequest 'Abblix\.Oidc\.Server\.Model\.RevocationRequest') for the token revocation endpoint \(RFC 7009\)\. All bound properties, validation attributes and the projection back onto the core model are generated from the core type\. |
| [TokenRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server-mvc/Abblix.Oidc.Server.Mvc.Model.TokenRequest 'Abblix\.Oidc\.Server\.Mvc\.Model\.TokenRequest') | The transport\-bound counterpart of [TokenRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Model.TokenRequest 'Abblix\.Oidc\.Server\.Model\.TokenRequest') for the token endpoint\. All bound properties, model binders resolved from the core wire\-format markers, validation attributes and the projection back onto the core model are generated from the core type\. |
| [UserInfoRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server-mvc/Abblix.Oidc.Server.Mvc.Model.UserInfoRequest 'Abblix\.Oidc\.Server\.Mvc\.Model\.UserInfoRequest') | The transport\-bound counterpart of [UserInfoRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Model.UserInfoRequest 'Abblix\.Oidc\.Server\.Model\.UserInfoRequest') for the UserInfo endpoint \(OIDC Core §5\.3\), reachable via GET and POST\. All bound properties and the projection back onto the core model are generated from the core type\. |