I run VAULT_ADDR=https://vault.<mydomain>.io vault login -method=oidc in a shell on MacOS and see Google Chrome open, i'm asked to authenticate with credentials, then the browser redirects to http://localhost:8250/oidc/callback?code=[redacted]&state=[redacted]. Vault CLI however does not seem to receive that code, it eventually times out with
> $ VAULT_ADDR=https://vault.<mydomain>.io vault login -method=oidc
Complete the login via your OIDC provider. Launching browser to:
https://<mydomain>.okta.com/oauth2/default/v1/authorize?client_id=[redacted]&nonce=[redacted]&redirect_uri=http%3A%2F%2Flocalhost%3A8250%2Foidc%2Fcallback&response_type=code&scope=openid+profile+groups+email&state=[redacted]
Waiting for OIDC authentication to complete...
Error authenticating: Timed out waiting for response from provider
Vault CLI does seem to open listening port 8250 on localhost (before it times out, closes it after the timeout) so I'm puzzled...
I run
VAULT_ADDR=https://vault.<mydomain>.io vault login -method=oidc
in a shell on MacOS and see Google Chrome open, i'm asked to authenticate with credentials, then the browser redirects tohttp://localhost:8250/oidc/callback?code=[redacted]&state=[redacted]
. Vault CLI however does not seem to receive that code, it eventually times out withVault CLI does seem to open listening port 8250 on localhost (before it times out, closes it after the timeout) so I'm puzzled...