Calling PATCH method to edit User data/metadata always leads to a CORS error

Hello, just wanted to see if anyone else has experienced a CORS issue when trying to use the PATCH call to update user data? I suspect it may be something more than a CORS issue (maybe an Axios issue?), but I’m not sure…

I’ve been stuck on this for a few days now. I’ve tried using both the basic tutorial method as well as using updateUser method in the management client in node-auth0. I’ve ensured that the call is being made via an M2M token from my app’s backend. I confirmed this is being done correctly because GET calls to the management API from my Node back-end work just fine.

Note that making a PATCH call using the management API in the documentation via copying and pasting the token works OK for me. It also works fine for me if I make the PATCH call using curl in Postman.

I’ve ensured that the origin (http://localhost:3000/) and any possible branches have been added to the application’s allowable web origins and CORS websites. I’ve experimented with different ways of making my PATCH call, including adding additional CORS related headers and installing the CORS module on my backend as per external instructions, such as here and here.

Nothing works. The error messages that come back is always:

Access to XMLHttpRequest at 'https://dev-X-XXXXhb.us.auth0.com/api/v2/users/XXXXXX8c288f1a2a3' from origin 'http://localhost:3000' has been blocked by CORS policy: Method PATCH is not allowed by Access-Control-Allow-Methods in preflight response.

Again, it could possibly be something other than CORS, but what? Can anyone please help? I’m happy to share the website where the app has been deployed as well as the HAR file.

Thank you,

R