Feature Request: Support a flag to specify whether to authenticate as a user or machine about auth0-cli HOT 2 OPEN

Dear valued user,

We had considered those exact flags during initial implementation of the login function. However, we realized that there were flags that allowed you to "skip" the choice of login mechanism:

As User: auth0 login --domain <tenant-domain> --client-id <client-id> --client-secret <client-secret>

As Machine: auth0 login --no-input

Admittedly, the --no-input flag is not immediately intuitive and a --as-user could certainly be added in the future.

Does the above help?

from auth0-cli.

Hey @willvedd! 😆

Thanks! And I gotcha, that decision makes total sense. We are, admittedly, kind of applying the CLI in a use case it wasn't initially planned of being used for, I think. There are bound to be situations like this.

Thanks for the guidance examples! The "as user" guidance example you provided would work, but at least for this use case, where we have a lot of first-time users coming to Auth0 with clean tenants and unfamiliarity with the processes, it would be problematic from a DX perspective.

It would require considerably more work for the end user to craft the command, and guidance from ourselves in how to craft it, meaning lengthier quickstarts and READMEs, and more opportunity for errors by users during configuration.

There's a bit of a chicken-and-the-egg situation, too, for this use case. If you take a look at a quickstart that uses the CLI, as an example, users won't have the information necessary to craft the authentication command as you demo'd beforehand: https://auth0.com/docs/quickstart/webapp/laravel/01-login#sdk-configuration

(No fires on this (and my other) suggestion by the way, just rough areas I noticed that we could consider improving to ease CLI adoption for use with the SDKs! Just something to consider. ❤️)

from auth0-cli.