Skip to content

Commit c1de178

Browse files
authored
doc: Remove EA tag for DPoP (#1460)
1 parent a9465c4 commit c1de178

2 files changed

Lines changed: 0 additions & 3 deletions

File tree

EXAMPLES.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1319,8 +1319,6 @@ You can skip sending the `customScheme` property if you do not want to customize
13191319
13201320
[DPoP](https://datatracker.ietf.org/doc/html/rfc9449) (Demonstrating Proof-of-Possession) is an OAuth 2.0 extension that cryptographically binds access and refresh tokens to a client-specific key pair. This prevents token theft and replay attacks by ensuring that even if a token is intercepted, it cannot be used from a different device.
13211321
1322-
> **Note**: This feature is currently available in [Early Access](https://auth0.com/docs/troubleshoot/product-lifecycle/product-release-stages#early-access). Please reach out to Auth0 support to get it enabled for your tenant.
1323-
13241322
### Enabling DPoP
13251323
13261324
DPoP is enabled by default (`useDPoP: true`) when you initialize the Auth0 client:

FAQ.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -483,7 +483,6 @@ DPoP is **enabled by default** (`useDPoP: true`) in this SDK because it provides
483483
- ✅ Enable if you handle sensitive data or financial transactions
484484
- ✅ Enable if you want best-in-class security practices
485485
- ✅ Enable if your users access the app from multiple devices (DPoP helps prevent cross-device token abuse)
486-
- ⚠️ **Note**: DPoP is currently in [Early Access](https://auth0.com/docs/troubleshoot/product-lifecycle/product-release-stages#early-access) - contact Auth0 support to enable it on your tenant
487486
- ⚠️ **Note**: Existing users with Bearer tokens will need to log in again to get DPoP tokens (see [FAQ #13](#13-how-do-i-migrate-existing-users-to-dpop))
488487

489488
**How to disable it (if needed):**

0 commit comments

Comments
 (0)