Hello, I am trying to understand why calling getAccessTokenSilently redirects me back to the login page after I update my user’s app_metadata via the Management API. Here’s my setup: I have two applications: 1) an SPA, and 2) a M2M The SPA shows the Auth0 login screen and upon successful signup/…

Hi, Is your backend updating the email or email_verified attributes when it patches the user? Patching Email or Email_verified via the management API will invalidate the Auth0 session. Example: This post body will invalidate the session: { "email_verified": true, "app_metadata": { …

If it helps, here’s a sequence diagram of my registration flow: [registration-flow]

Any suggestions here? The difference in behavior of silent-auth (when updating app_metadata via the Management API vs updating via the UI) is quite puzzling. The UX of of having to re-login is what I am trying to avoid. Thanks!

Yes, my backend was setting email_verified: true. After removing it, my frontend is able to refresh the token silently without getting the login required error. Thanks Marcus! Would you mind explaining why toggling email_verified invalidates the session? Is this shared in the docs anywhere?

Silent Auth errors with Login Required after updating app_metadata via Management API

Get Help

Topic		Replies	Views
Auth Error after updating app_metadata via Management API and injecting metadata to IdToken Get Help auth0	6	2731	January 11, 2022
updateUserMetaData - How can I update meta data from useUser without login/logout? Get Help user-profile , user-management	4	1837	June 30, 2023
How to fetch new token after updating user_metadata in React Get Help token , auth0 , node , react , user_metadata	10	6948	August 13, 2021
React auth0 sdk Get Help	2	1737	March 11, 2022
How to get Management API accessToken silently while SPA was already configured for a custom API? Get Help spa , login , access-token , user_metadata	5	4761	May 4, 2021

Silent Auth errors with Login Required after updating app_metadata via Management API

Related topics