feat: production-grade Privy Auth server integration#2
Open
lustsazeus-lab wants to merge 1 commit into
Open
Conversation
06f6036 to
2123757
Compare
Author
|
Friendly follow-up on this PR 👋 This branch has already been rebased and is currently mergeable (CLEAN). Implemented scope recap:
Since issue #1 is no longer accessible, I’m using this PR thread as the implementation context. Happy to make any further changes quickly if you want adjustments before merge. |
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
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.
Summary
Implements a reviewable server-side Privy Auth integration for issue #1 with replay protection and tests.
What changed
PrivyAuthServicefor server-side token verification against Privy JWKSNonceStore,InMemoryNonceStore)AuthError) with status/code semantics.env.exampleVerification
npm testpasses locally (3 tests)Closes #1