I don’t know why, The account handles two tenants, the production one with same settings is okay, but the dev one isn’t. I hope you can help me, because this is preventing us user creation normally, for creating users we need to go to machine to machine application and set token endpoint to POST instead of NONE, and after creating the user we need to set it back to NONE for login and this is really annoying because we have the client app ready for a normal operation, not this, and for creating users I need to do it to the backend level. Please help with this.
I’ve checked all answer, nothing has changed, the application still redirecting. And the weird thing here is that we have a production environment running without this issue. Same branch deployed, so I know is not a code issue.
Up for this topic. I’m having the same issue since the beginning of this week. In my case this is happening for a specific user, when I tried with others It works as expected - It’s worth saying I also have multiple environments, the issue doesn’t happen on live as I’m able to login with my user perfectly however It doesn’t work in my local env.
The issue “seems” related to the other links Konrad shared - I’m checking if one of these can help me to find a solution but nothing so far.
Did you get some solution about this? This guy @konrad.sopala told me “send a dm” but until now I have no answer, not even telling me, hey I won’t help you
I ended up figuring it out. I was using a call to get an access token silently, and while I was properly specifying the audience I needed for that call, I wasn’t doing it in the Auth0ProviderWithNavigate file, so I had to add the audience to the Auth0 Provider like this:
<Auth0Provider
domain={domain}
clientId={clientId}
cacheLocation="localstorage"
authorizationParams={{
audience: process.env.REACT_APP_API_SERVICE_AUDIENCE, // I had to add this
redirect_uri: redirectUri,
}}
onRedirectCallback={onRedirectCallback}
>
{children}
</Auth0Provider>
Hi @edinson.martinez , If you’re facing this issue on one particular machine and not in all other machines, It could be due to incorrect system time configuration. We faced a similar infinite loop issue on one machine where the system time wasn’t configured correctly.