Can't verify ID Token in Auth0
up vote
0
down vote
favorite
I’m trying to verify an ID Token in Auth0 and I can’t get past verifying the signature. At this point, I have an ID Token, and I am able to decode it and get the headers through jwt.get_unverified_header(token). However the header “kid” doesn’t exist, I only see:
“typ”: “JWT”,
“alg”: “RS256”
Does this have anything to do with the fact that I’m using the old legacy pipeline? If not, what am I doing wrong?
I've read this documentation in depth and can't find a reason why: https://auth0.com/docs/jwks#using-the-jwks-in-your-application-to-verify-a-jwt
jwt auth0
add a comment |
up vote
0
down vote
favorite
I’m trying to verify an ID Token in Auth0 and I can’t get past verifying the signature. At this point, I have an ID Token, and I am able to decode it and get the headers through jwt.get_unverified_header(token). However the header “kid” doesn’t exist, I only see:
“typ”: “JWT”,
“alg”: “RS256”
Does this have anything to do with the fact that I’m using the old legacy pipeline? If not, what am I doing wrong?
I've read this documentation in depth and can't find a reason why: https://auth0.com/docs/jwks#using-the-jwks-in-your-application-to-verify-a-jwt
jwt auth0
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I’m trying to verify an ID Token in Auth0 and I can’t get past verifying the signature. At this point, I have an ID Token, and I am able to decode it and get the headers through jwt.get_unverified_header(token). However the header “kid” doesn’t exist, I only see:
“typ”: “JWT”,
“alg”: “RS256”
Does this have anything to do with the fact that I’m using the old legacy pipeline? If not, what am I doing wrong?
I've read this documentation in depth and can't find a reason why: https://auth0.com/docs/jwks#using-the-jwks-in-your-application-to-verify-a-jwt
jwt auth0
I’m trying to verify an ID Token in Auth0 and I can’t get past verifying the signature. At this point, I have an ID Token, and I am able to decode it and get the headers through jwt.get_unverified_header(token). However the header “kid” doesn’t exist, I only see:
“typ”: “JWT”,
“alg”: “RS256”
Does this have anything to do with the fact that I’m using the old legacy pipeline? If not, what am I doing wrong?
I've read this documentation in depth and can't find a reason why: https://auth0.com/docs/jwks#using-the-jwks-in-your-application-to-verify-a-jwt
jwt auth0
jwt auth0
asked Oct 10 at 23:12
Bernardo Rodriguez
968
968
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52749993%2fcant-verify-id-token-in-auth0%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown