Custom properties added to the wrong token
I added custom properties to the id token, but I see them added to the access token instead of the id token.
Is this a known issue?
15 Replies
Hi @moroshko,
I cannot reproduce this issue.
After you have added the specified custom properties to the ID token, are you able to logout and back into your app.
If the issue still exists, are you willing to share the claims of your ID and access tokens?
Just tried to reproduce this again and do a recording, but now I started getting a new issue:
/api/auth/kinde_callback crashes with 500
KindeSDKError: Attempting to commit invalid access_token tokenI'm using the Next.js SDK. Is this a known issue?
I am not aware of this issue.
I wil get one of my teammates to look into this issue tomorrow.
Oh, I just realized that I moved my machine clock a few days ahead and forgot about that π
Now that I synced the clock again, the issue disappeared π
Let me get back to you regarding your ask above.
DMed you the tokens
Hi @moroshko,
I can now reproduce the issue above with custom properties being added to the
access token
instead of the ID token
.
My team are already looking into a fix.
Sorry the inconvenience caused with this issue.
Hey @moroshko,
Are you being blocked by this issue? If so, I want to help you find a workaround for the meantime.
Let me know.Thanks for looking into this.
I'm blocked in a sense that I can't currently rely on the custom properties to exist in the id token.
I can get them from the access token, but if the issue is going to be fixed then I guess the property will suddenly disappear from the access token which will break things.
I can wait until this is fixed.
I just surprised that no one else has raised this.
Dave, our co-founder, is the best person to fix this issue.
He will continue to look into a fix on Monday.
If you are willing to wait for a fix, then I will let you know once it's fixed.
No worries, keep me updated!
Will do!
@Oli - Kinde Just checking to see if there are any news on this issue?
Hey @moroshko,
We are still implementing a fix to this issue.
Apologies for the inconvenience.
Thanks for the update
Hey @moroshko,
There is a PR with a fix to this issue, that is currently being reviewed
great to hear, appreciate the update!
Hey @moroshko,
This issue has been resolved