We’ve been using Auth0 for 2 months. At the beginning it ran smoothly with everything - we could log in, using username-password, Google, Facebook. But there was a moment when the username-password authentication stopped working - we have “login success” and “failed exchange - oauth.eu.auth0.com not found”. But when we log in, using Google/Facebook - “login success” - “exchange success”. We haven’t changed the code for Auth0 since August. Does anyone have any idea what’s going on?
Based on the information you provided I would check if you’re using the correct tenant names for the URL endpoints you’re calling. In particular, the {tenant} part in https://{tenant}.auth0.com needs to be consistent and associated with the correct tenant for which the transaction is being performed (aka the tenant associated with the client application in question). In this particular case, verify if oauth is the right tenant that should be being used. The reason is that some endpoints could be determining the tenant through other means and now they are more strict about it and enforce that the tenant is consistently provided; the fact some endpoints could determine the information based on something other than the URL is an implementation detail you should never depend on so be sure to always use the correct tenant information.
@jmangelo - we don’t provide it at all. There is no difference in our code between google/fb and username/password - but it works in one case, in another - not.
@jmangelo - we don’t provide it at all. There is no difference in our code between google/fb and username/password - but it works in one case, in another - not.
Even if it currently works for social connection that is just an implementation detail subject to change so down the line it may not work for username/password and also social. Even if at this point it works for social, the conclusion is the same, the tenant/domain needs to be correctly specified so if you’re not doing that you need to start doing it.