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

## DPoPAlgorithms Class

Single source of truth for the DPoP signing\-algorithm whitelist \(RFC 9449 §4\.2,
§7\.1\)\. Both the proof\-validator's enforcement \(it rejects proofs whose `alg`
header sits outside this set\) and the resource\-server's `WWW-Authenticate: DPoP
            algs="..."` challenge advertisement read from here, so adding a new algorithm
\(e\.g\. EdDSA when the JWS layer gains support\) propagates everywhere automatically\.

```csharp
public static class DPoPAlgorithms
```

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

## DPoPAlgorithms\.Allowed Field {#Abblix.Oidc.Server.Features.DPoP.DPoPAlgorithms.Allowed}

JWS algorithms accepted on a DPoP proof\. `none` and HMAC\-based algorithms
are intentionally absent — RFC 9449 §4\.2 forbids them because the embedded
`jwk` header carries an asymmetric public key for verification\.

```csharp
public static readonly IReadOnlySet<string> Allowed;
```

#### Field Value
[System\.Collections\.Generic\.IReadOnlySet&lt;](https://learn.microsoft.com/en-us/dotnet/api/system.collections.generic.ireadonlyset-1 'System\.Collections\.Generic\.IReadOnlySet\`1')[System\.String](https://learn.microsoft.com/en-us/dotnet/api/system.string 'System\.String')[&gt;](https://learn.microsoft.com/en-us/dotnet/api/system.collections.generic.ireadonlyset-1 'System\.Collections\.Generic\.IReadOnlySet\`1')