-
Notifications
You must be signed in to change notification settings - Fork 432
feat: Add DPoP (Demonstrating Proof-of-Possession) #2357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
tusharpandey13
wants to merge
10
commits into
main
Choose a base branch
from
feat/dpop
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…xity; added fetcher and dpop nonce handling; fixed example code
…jitter; add and fix tests; add examples for all server contexts in sample
2 tasks
This replaces #2346
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2357 +/- ##
==========================================
- Coverage 88.58% 85.72% -2.86%
==========================================
Files 32 35 +3
Lines 3109 3614 +505
Branches 615 726 +111
==========================================
+ Hits 2754 3098 +344
- Misses 352 513 +161
Partials 3 3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…ts; make retry validation in dpopUtils more robust
…; addressed some auto-review comments by github bot
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's New?
This PR introduces DPoP (Demonstrating Proof-of-Possession) support to the Auth0 Next.js SDK, implementing the RFC 9449 standard for enhanced OAuth 2.0 security.
Why DPoP? DPoP cryptographically binds access tokens to your client using public key cryptography, preventing token theft and replay attacks. Even if an access token is intercepted, it cannot be used without the corresponding private key.
Quick Start Example
Your API calls are now secured with cryptographic proof-of-possession! 🔒
What's Included
This implementation provides a complete DPoP solution for Next.js applications:
fetchWithAuth()
- Protected resource requests with seamless DPoP integrationcreateFetcher()
- High-level HTTP client with automatic DPoP supportgenerateDpopKeyPair()
- Easy ES256 key pair generation✅ Testing
References