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

## IBackChannelNotificationRequest Interface

Common shape of the JSON body the authorization server posts to the client's
`client_notification_endpoint` in CIBA ping and push modes\. The
`auth_req_id` is always present; push payloads add the issued tokens\.

```csharp
public interface IBackChannelNotificationRequest
```

Derived  
↳ [BackChannelPingNotificationRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Model.BackChannelPingNotificationRequest 'Abblix\.Oidc\.Server\.Model\.BackChannelPingNotificationRequest')  
↳ [BackChannelPushNotificationRequest](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Model.BackChannelPushNotificationRequest 'Abblix\.Oidc\.Server\.Model\.BackChannelPushNotificationRequest')
### Properties

## IBackChannelNotificationRequest\.AuthenticationRequestId Property {#Abblix.Oidc.Server.Features.BackChannelAuthentication.Interfaces.IBackChannelNotificationRequest.AuthenticationRequestId}

The `auth_req_id` the notification refers to, allowing the client to correlate
the callback with the originating CIBA authentication request\.

```csharp
string AuthenticationRequestId { get; init; }
```

#### Property Value
[System\.String](https://learn.microsoft.com/en-us/dotnet/api/system.string 'System\.String')
