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

## BackChannelNotificationTransport Class

The HTTP transport CIBA ping and push notifications travel on, to the endpoint a client registered\.

```csharp
public static class BackChannelNotificationTransport
```

Inheritance [System\.Object](https://learn.microsoft.com/en-us/dotnet/api/system.object 'System\.Object') → BackChannelNotificationTransport
### Fields

## BackChannelNotificationTransport\.HttpClientName Field {#Abblix.Oidc.Server.Features.BackChannelAuthentication.BackChannelNotificationTransport.HttpClientName}

The name the transport's client is registered under, published so a host can configure it without copying
the string: `services.AddHttpClient(BackChannelNotificationTransport.HttpClientName)` reaches the same
client the delivery service resolves, and whatever it chains \- a resilience pipeline, a proxy \- applies to
every notification\.

```csharp
public const string HttpClientName = "HttpNotificationDeliveryService";
```

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

### Remarks
Whatever a host chains runs OUTSIDE the SSRF validation, because that validation is the client's primary
handler and therefore the innermost one\. So every attempt a resilience pipeline makes is validated afresh \-
which is what the address of a client\-supplied endpoint requires, since it can start resolving to an
internal one between attempts \- and no ordering of the host's own calls can move the check out of the way\.

The value is the delivery service's type name because that is what shipped, and a host already configuring
the client spells it literally. Changing it would break such a host in the one way nothing reports: the
configuration would bind to a client no longer resolved, leaving the build green and the pipeline gone.