You say this, but… I am not sure you are answering the question being asked. It’s easy enough to use rules to add information to the app_metadata and user_metadata, but it isn’t always returned in an accessToken depending on how that accessToken is generated. What I want to know is what is required to get that information to return as part of the accessToken? For example, one of our developers gets an access token using auth0-js and sends the authentication request with a response_type, audience and scope. Another developer is using passport-auth0 and passportjs to do the very same thing. But only the first developer’s accessToken has the metadata in it. I feel like it is has to do with the response_type because the first developer is using “token” and the second developer can’t change it because passport hardcodes it to “code”. If we could change the response_type to “token” for the second developer, would that return the metadata we are looking for in the accessToken? Or is there a different tree we should be barking up?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| How to get app_metadata and user_metadata THE RIGHT WAY | 2 | 17698 | October 21, 2019 | |
| App_metadata not included in IdToken or accessToken | 2 | 4687 | April 30, 2022 | |
| How to get user_metadata and app_metadata in id_token | 3 | 7577 | February 22, 2019 | |
| How to add user meta data and app meta data in access token? | 2 | 6968 | March 28, 2022 | |
| How do I get app_metadata via rules? Docs seem incomplete or confusing | 5 | 8463 | December 19, 2018 |