auth0 login should respect the --domain flag for personal credentials login

[davidharrigan]

Checklist

• I agree to the terms within the Auth0 Code of Conduct.

Describe the problem you'd like to have solved

My Auth0 account has many tenants. Selecting the correct tenant from the authorization consent UI is doable, but would be nice if the auth0 login --domain <tenant domain> worked for the device code flow login.

Describe the ideal solution

When --domain flag is provided for the device code login flow, the correct tenant is selected without having to search for it in the UI.

Alternatives and current workarounds

No response

Additional context

I believe this would work if we can pass the --domain value to the audience field here:

auth0-cli/internal/auth/auth.go

Line 153 in 54e9a30

"audience": []string{a.Audience},

instead of using the hardcoded wildcard audience defined here:

auth0-cli/internal/auth/auth.go

Line 53 in 54e9a30

Audience: "https://*.auth0.com/api/v2/",

[duedares-rvj]

@davidharrigan Thank you David for the recommendation. We have updated the login flow to respect the domain flag now.
Please note that since domain is a common param used by both machine login and user login, one should use the below command to login to a tenant directly in a user login flow:

auth0 login --domain <tenant domain> --no-input

The no-input flag indicates that there will be no further input (client-id and client-secret) and hence cli evaluates it as a user login flow.

This shall be included in the next upcoming release.

[davidharrigan]

thank you, looking forward to the next release :)

[ramya18101]

Hello @davidharrigan,
Apologies that we missed to update that the changes has been released part of v1.5.0 and closing this ticket, Please feel free to re-open the issue if you have any concerns.