You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the improvement or update you wish to see?
I am using auth0 as a provider to get a JWS and store that on the user session. I want to verify that the token sent back with requests from my frontend is still valid (it should not be expired and should also be verified against the issuer/audience).
The documentation mentions the getToken function as a helper to verify and decode the JWT. It appears that this will verify that the token was issued by my server which has the auth endpoint - but it would not verify other things based on the JWKS endpoint of my auth0 client. So I still need to check the expiration and verify the issuer/audience on my end correct?
I have something like the following code set up using the jose library:
What is the improvement or update you wish to see?
I am using auth0 as a provider to get a JWS and store that on the user session. I want to verify that the token sent back with requests from my frontend is still valid (it should not be expired and should also be verified against the issuer/audience).
The documentation mentions the
getToken
function as a helper to verify and decode the JWT. It appears that this will verify that the token was issued by my server which has the auth endpoint - but it would not verify other things based on the JWKS endpoint of my auth0 client. So I still need to check the expiration and verify the issuer/audience on my end correct?I have something like the following code set up using the jose library:
Just want to make sure I am understanding the
getToken
function correctlyIs there any context that might help us understand?
Help understanding how to properly verify JWT when using auth0 provider
Does the docs page already exist? Please link to it.
https://next-auth.js.org/configuration/options#jwt-helper
The text was updated successfully, but these errors were encountered: