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

## BackChannelLogoutUriValidator Class

Validates the OIDC Back\-Channel Logout 1\.0 `backchannel_logout_uri`: when supplied it must be an
absolute URI that the server is permitted to fetch under the active SSRF policy
\([SecureHttpFetchOptions](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.SecureHttpFetch.SecureHttpFetchOptions 'Abblix\.Oidc\.Server\.Features\.SecureHttpFetch\.SecureHttpFetchOptions')\)\. Because the OP itself POSTs the logout token to this endpoint,
rejecting an internal/loopback or disallowed\-scheme target at registration stops a registered client
from becoming a \(blind\) SSRF vector and surfaces the problem to the caller up front rather than as a
silent delivery failure at logout time\. The outbound handler still re\-validates at request time\.

```csharp
public class BackChannelLogoutUriValidator : Abblix.Oidc.Server.Endpoints.DynamicClientManagement.Validation.SyncClientRegistrationContextValidator
```

Inheritance [System\.Object](https://learn.microsoft.com/en-us/dotnet/api/system.object 'System\.Object') → [SyncClientRegistrationContextValidator](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Endpoints.DynamicClientManagement.Validation.SyncClientRegistrationContextValidator 'Abblix\.Oidc\.Server\.Endpoints\.DynamicClientManagement\.Validation\.SyncClientRegistrationContextValidator') → BackChannelLogoutUriValidator
### Constructors

## BackChannelLogoutUriValidator\(ISecureUriValidator\) Constructor {#Abblix.Oidc.Server.Endpoints.DynamicClientManagement.Validation.BackChannelLogoutUriValidator.BackChannelLogoutUriValidator(Abblix.Oidc.Server.Features.SecureHttpFetch.ISecureUriValidator)}

Validates the OIDC Back\-Channel Logout 1\.0 `backchannel_logout_uri`: when supplied it must be an
absolute URI that the server is permitted to fetch under the active SSRF policy
\([SecureHttpFetchOptions](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.SecureHttpFetch.SecureHttpFetchOptions 'Abblix\.Oidc\.Server\.Features\.SecureHttpFetch\.SecureHttpFetchOptions')\)\. Because the OP itself POSTs the logout token to this endpoint,
rejecting an internal/loopback or disallowed\-scheme target at registration stops a registered client
from becoming a \(blind\) SSRF vector and surfaces the problem to the caller up front rather than as a
silent delivery failure at logout time\. The outbound handler still re\-validates at request time\.

```csharp
public BackChannelLogoutUriValidator(Abblix.Oidc.Server.Features.SecureHttpFetch.ISecureUriValidator uriValidator);
```
#### Parameters

###### `uriValidator` [ISecureUriValidator](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.SecureHttpFetch.ISecureUriValidator 'Abblix\.Oidc\.Server\.Features\.SecureHttpFetch\.ISecureUriValidator') {#Abblix.Oidc.Server.Endpoints.DynamicClientManagement.Validation.BackChannelLogoutUriValidator.BackChannelLogoutUriValidator(Abblix.Oidc.Server.Features.SecureHttpFetch.ISecureUriValidator).uriValidator}

The shared SSRF URI policy used by the outbound HTTP handler\.