Confusion on /userinfo vs. /api/v2/users/{id} apis

[ty.frith]

Hey there @dean2 sorry for the delayed response here!

@dean2

I am simply missing this {id} though seems like I should not need it somehow. Is there another endpoint that simply uses my access token or is there a library to parse the access token for the {id} somehow?

The {id} is equivalent to the sub claim in either an ID or access token.

@dean2

I was reading this article as well trying to parse the access token. When I use the website it links(jwt.io), it says invalid access token, BUT when I cut/paste the json to generate the token, it gives me an accesstoken just fine. I don’t understand how auth0 is giving an access token that can’t be parsed when there is docs talking about accesstoken. This is so confusing here.

It’s possible you are receiving an opaque access token if you aren’t passing an audience param in the /authorize request - The following FAQ(s) may be helpful:

https://community.auth0.com/t/why-is-my-access-token-not-a-jwt-opaque-token/31028

https://community.auth0.com/t/what-is-the-audience/71414