Allow login using the CLI only

[Heitor]

It is frustrating to have to open a browser to log in a juju controller, afterall `juju` is a CLI tool.

It is common for us to have to log in multiple times consecutively, because the time it takes to start a browser in a remove SSH session to a server far away sometimes is greater than the timeout of a Juju command.

This is a weird pattern to log in.

Please add a way for us to log in using CLI tools only.

Some examples of CLI programs that allow us to login in the CLI and integrates well with other CLI tools:
- openSSH
- git

[Erik Lönroth (erik-lonroth)]

I totally agree. Swapping between a terminal and a web browser is a unnatural workflow and should be better off to prompt of use some kind of local cli credentials...

[Ian Booth (wallyworld)]

Have you tried the -B login option?

juju help login
...
Command Options:
-B, --no-browser-login (= false)
    Do not use web browser for authentication
...

In this case, a CLI based prompt for username, password, 2fa is used.

[Heitor (heitorpbittencourt)]

```
$ juju models -B
Opening an authorization web page in your browser.
If it does not open, please open this URL:
[...]
```

And no CLI based prompt.

Using Juju client 2.9.12

[Ian Booth (wallyworld)]

It seems you've found a bug in -B handling.

It works with juju login -B <controllername> but not it seems with other commands like juju models.

As a workaround for now, you can "juju login -B <controllername>".
(I tested with juju login -B jaas")

[Heitor (heitorpbittencourt)]

Ouch...

I tried with `juju login -B` and it didn´t work: it opened the browser again. The controller name makes a difference here.

Is it possible to configure Juju to use the CLI login as the default?