Bad audience when changing user_metadata

JWT.io
1

I’m wondering if someone can clarify the correct workflow for changing an email or app_metadata property in a user’s auth0 account. I have jwt working between express and a react app for login. I’d like to use the auth0 api v2 to edit a user’s app_metadata. When I send a PATCH request off, I get a 401 bad audience error. This kind of makes sense to me because the audience of my jwt for authenticating between the client and my backend is likely different from what I need to communicate with the auth0 api.

This is basically what it looks like clientside, but I’ve also tried it on the server with the same result.

axios.defaults.headers.Authorization = `Bearer ${localStorage.getItem('access_token')}`;
axios
  .get('https://xxx.auth0.com/api/v2/users/58c6db003c9c2b7caff55ebc', { user_metadata: { firstName: 's', lastName: 'j' } })
  .then(response => console.log(response));

How exactly do I get an updated access_token that I can use to change an auth0 property? Is it easier to send off the command from the client, or can I just give my backend full access to change app_metadata and then just ensure that I do enforcement before sending the command off? What does the axios code look like for a server-side PATCH call?

Thanks!

1 Like
3

Hey @stephen.jensen.ihi !

As it has been more than a few months since this topic was opened and there has been no reply or further information provided from the community as to the existence of the issue we would like to check if you are still facing the described challenge?

We are more than happy to assist in any way! If the issue is still out there please let us know so we can create a new thread for better visibility, otherwise we’ll close this one in week’s time.

Thank you!

4

This topic was automatically closed after 6 days. New replies are no longer allowed.