Bug: The idTokenData is not set

[soofstad]

Bug: The idTokenData is not set

[soofstad]

Issue resolved by 85744ec.

Version 1.9.1 is now available with this included.

[albertwangnz]

Tested and it works. Thanks!

[soofstad]

Hi,
Can you please post your configuration?
Also, are you sure the access token is a valid JWT? You can try it out at pages like jwt.ms
And, are you receiving an id_token in the token request? Usually you need some special config on the provider, and a special scope for this.

[albertwangnz]

Hi @soofstad , thank you for your reply.

I created a fork of the project https://github.com/albertwangnz/react-oauth2-pkce-issue49, and you can see my change in the example microsoft-auth-provider. I use AWS Cognito as the auth provider.

As you can see in the screenshot below, idTokenData is empty but idToken is not, and I can manually parse idToken to an object with the data.

[albertwangnz]

I just guess the issue might be missing of using if (idToken) setIdTokenData(decodeJWT(idToken)) in the file below.

src/AuthContext.tsx

Line 195.

[anthony-vito]

I think he's right. The idToken data is decoded and assign on line 105 of the AuthContext when a login happens...... but there is another effect() that decodes the access token that starts on line 163..... What is the purpose of that effect() ? An additional decode for both tokens might need to be placed in there.

They should both also obey the configuration "config.decodeToken" to decide on if token decoding happens at all.

[soofstad]

You are both absolutely right.
Seems I was a bit quick on the testing for the last version.

As it is now, we decode the idToken on a received token response, but not when loading the page when the idToken is already fetched.

Will get a fix for this ASAP.

[albertwangnz]

Really appreciate your so fast response :-)