Exposing token-verifier for public use #325
Merged
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
Useful in special cases such as authorize the request websockets requests.
E.g use case,
Next app app authorizes using a firbease custom token, this custom token is sent to websoket server, with in the web socket server easy and lightweight way to authorize the user by validating the token `createIdTokenVerifier` wihout all the next js dependencies.
```
const idTokenVerifier = createIdTokenVerifier("project-name");
const decodedToken = await idTokenVerifier.verifyJWT(token, {});
const { uid, name, exp, picture, email } = decodedToken;
```
awinogrodzki
approved these changes
Apr 8, 2025
|
Hey @websiddu, Thanks for the PR! I've released the changes in v1.10.0-canary.3 |
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.
Useful in special cases such as authorize the request websockets requests.
E.g use case,
Next app app authorizes using a firbease custom token, this custom token is sent to websoket server, with in the web socket server easy and lightweight way to authorize the user by validating the token
createIdTokenVerifierwihout all the next js dependencies.