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

## Abblix\.Oidc\.Server\.Features\.ReplayPrevention Namespace

| Classes | |
| :--- | :--- |
| [DistributedJwtReplayCache](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.ReplayPrevention.DistributedJwtReplayCache 'Abblix\.Oidc\.Server\.Features\.ReplayPrevention\.DistributedJwtReplayCache') | Distributed cache implementation of [IJwtReplayCache](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.ReplayPrevention.IJwtReplayCache 'Abblix\.Oidc\.Server\.Features\.ReplayPrevention\.IJwtReplayCache') for JWT replay protection\. Uses [Microsoft\.Extensions\.Caching\.Distributed\.IDistributedCache](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.caching.distributed.idistributedcache 'Microsoft\.Extensions\.Caching\.Distributed\.IDistributedCache') to store JTIs, enabling multi\-instance deployments\. |

| Interfaces | |
| :--- | :--- |
| [IJwtReplayCache](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Features.ReplayPrevention.IJwtReplayCache 'Abblix\.Oidc\.Server\.Features\.ReplayPrevention\.IJwtReplayCache') | Tracks JWT IDs \(jti claims\) presented to the server, so a JWT\-bearing flow can detect replay attempts\. Both RFC 7523 §5\.2 \(JWT\-bearer\-grant assertion replay\) and RFC 9449 §11\.1 \(DPoP proof replay\) want this primitive; it is intentionally namespace\-neutral so a single distributed\-cache instance serves every consumer\. |