cloudron cli 7.1.0 / instance 9.1.3 login

[timconsidine]

Weird.
I upgraded my CLI installation to 7.1.0.
Cannot login from laptop terminal to my.example.com
Constantly throws me to browser localhost address which fails with a message .

Safari can’t open the page
“http://localhost:1312/callback?code=IkBfP7hAchXf7CuoLvZsd1SVOiAAVm7b17j1pY35no0&state=4aa18a1e97cac91cc1391b53a03d4f95&iss=https%3A%2F%2Fmy.example.uk%2Fopenid”.

some HTTP vs HTTPS issue

• on 9.1.3
• Switched the docker registry in my Cloudron dashboard
• Changed my cloudron instance user password (general rotation)
• uninstalled CLI
• deleted ~/.cloudron.json
• reinstalled CLI

I'm losing the plot.
Is this related to login change (see below) ?
Or to my Safari installation (other problems faced) ?

% cloudron login --help
Usage: cloudron login [options] [cloudron]

Login to cloudron

Options:
  -u, --username <username>  Username [will be removed after Cloudron 9.1]
  -p, --password <password>  Password [will be removed after Cloudron 9.1]
  -h, --help                 display help for command

[timconsidine]

Would it not be easier to support use of a token for cloudron login ?

% cloudron login --token ffb1bc87d9ef8127f41aae7a7f950xxxxxxxxxxxxxxxxxxxxx --server my.example.uk
Cloudron Domain (e.g. my.example.com): my.example.uk
Opening browser for authentication...

Browser involvement seems bit retrograde to me ...

[james]

Hello @timconsidine

Thanks for the report.
We have to validate this with safari.

As an alternative method you can generate the ~/.cloudron.json manually with a pre-generated cloudron API token that has read-write access.

{
  "cloudrons": {
    "default": "my.cloudron.dev",
        "my.cloudron.dev": {
            "apiEndpoint": "my.cloudron.dev",
            "token": "$YOUR_TOKEN_GOES_HERE"
        },
  }
}

Or with a script using jq or yq:

jq -n '
{
  cloudrons: {
    default: env.CLOUDRON_DOMAIN,
    (env.CLOUDRON_DOMAIN): {
      apiEndpoint: env.CLOUDRON_DOMAIN,
      token: env.CLOUDRON_TOKEN
    }
  }
}' > ~/.cloudron.json

or

yq -n '
{
  "cloudrons": {
    "default": strenv(CLOUDRON_DOMAIN),
    (strenv(CLOUDRON_DOMAIN)): {
      "apiEndpoint": strenv(CLOUDRON_DOMAIN),
      "token": strenv(CLOUDRON_TOKEN)
    }
  }
}' > ~/.cloudron.json

[james]

Hello @timconsidine

@timconsidine said:

Browser involvement seems bit retrograde to me ...

Yes and No.
We had to make this switch to also support passkeys and other future webauthn validations.
Other tools like npm cli or docker cli have also made the switch to the browser style auth flow.

[girish]

@timconsidine I published a 7.1.1 which explicitly listens on IPv4. Can you check if that fixes anything? It's probably a Mac issue and not safari specifc. Do you have any more details on the error?