I am trying to use Auth0 to validate a user’s email and password, calling it from server code using simple HTTP calls. What I am doing is equivalent to
The docs for the resource owner password credentials (ROPC) grant available at /oauth/token do not indicate the support for a parameter named connection so that explains why passing it does not have any effect.
You can configure you account to have a default connection by navigating to your account settings and providing the connection name in the Default Directory field.
As an alternative, if you read further on the ROPC docs you’ll find that the endpoint supports an additional grant where you can specific the connection to be used in the request body itself using the realm parameter name. See:
Thank you, @jmangelo, that got me over the hump. With a little more struggling with poor docs and error messages I have managed to get registration and login working. I hope that password reset will be simple!
Thank you, @jmangelo, that got me over the hump. With a little more struggling with poor docs and error messages I have managed to get registration and login working. I hope that password reset will be simple!
When you configure a database connection in the dashboard you will be asked to provide a name; anywhere that a connection name is required you should use the value you provided there. You can also check the name of existing connections through the dashboard.
What if you want to use multiple Passwordless Auth Connections?
You can’t use realm cause it doesn’t allow passwordless
authentication and you can’t use the Default Directory cause
it accepts only one connection.
Is there any other solution?
What if you want to use multiple Passwordless Auth Connections? You can’t use realm cause it doesn’t allow passwordless authentication and you can’t use the Default Directory cause it accepts only one connection. Is there any other solution?