When I am getting the token after login, But when I want to verify in jwt.io the payload data is something like this: “{"id":"643da67379850�\u0012�\u0013\u001d\n\u0010P�\u0007.�+\u0018��n˽L��NL�\f�\b�^\u001c\b��M�\u000eMM\rL�\f�”

Hi all, Just circling back on the solution that @prisoner544 and I worked on through direct messages. Essentially, the payload was in the wrong format – specifically, it was an opaque access token because the ‘audience’ parameter was not sent in the login request. Passing an ‘audience’ in the /au…

Incorrect payload data format

JWT.io

system Closed September 12, 2023, 4:37pm 6

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
No payload in access token JWT.io jwt , auth0 , login	5	8514	January 28, 2022
JWT token is "invalid signature"? Get Help login-experience , new-universal-login-experience	19	54087	May 29, 2023
JWT Missing Payload Get Help oidc , protocols	2	2709	May 2, 2023
JWT.io is decoding the JWT header "wrong" Get Help jwt	3	2395	September 16, 2021
Unable to verify jwt. generated idToken looks different than the ones generated by our other application Get Help	4	3566	March 26, 2020

Incorrect payload data format

Related topics