Signup/ login from backend API

[stephanie.chamblee]

Hi @david18,

Welcome to the Community!

Regarding the access_denied error, it’s possible that you need to update the authentication method within your application settings.

For public clients, “None” should be selected for the “Token Endpoint Authentication Method”:

You might also need to select a default directory for your tenant. This setting is located in the top-right dropdown menu. Click Settings and under “API Authorization Settings”, enter “Username-Password-Authentication” for Default Directory

This topic might be helpful as well:

Using the Request Owner Password Endpoint on a new dev account

Thanks @Carlos_Mostek, So finally got the /token endpoint working. I indicate below the exact config in case anyone else has the same issue in the future: URL endpoint: https://{AUTH0_DOMAIN}/oauth/token Post body: { "client_id": "***", "grant_type": "password", "username": "email@provider.com", "password": "***" } Client Application settings: The Client application who’s client ID you are using must be of type native and password must be checked within the Applications -> …

also can a user access_token contain the “user_metadata”: { “TaxId”:“1234567” }

Yes, you can add user metadata properties to the Access Token or ID Token using Rules. You may want to be careful about adding any sensitive information within a JWT because the payload is base64 encoded and easy to decode.

Here is an example of adding custom claims to an Access Token and an ID Token:

Sample Use Cases: Rules with Authorization