AUTHENTICATION REQUIRED Tip: Current context: unknown. Press q to quit.

[1337andre]

Hi want to try argonaut, but i have problems with authentication.

$ argocd login argocd.bla.de --sso
Performing authorization_code flow login: https://idp.bla.de/auth/realms/bla/protocol/openid-connect/auth?access_type=offline&client_id=app-argo&code_challenge=2-YnWuzk6A4xVQHhigNR44dEZT2lO3eUGFnOixYk6n0&code_challenge_method=S256&redirect_uri=http%3A%2F%2Flocalhost%3A8085%2Fauth%2Fcallback&response_type=code&scope=openid+profile+email+offline_access&state=BWASJBqHAVmsBCYUXTQIlVcM
Opening system default browser for authentication
Authentication successful
'andre.krueger@bla.de' logged in successfully
Context 'argocd.bla.de' updated

same issue without sso and admin access

argocd cli works fine for me, but i can not use argonaut

$ argocd context
CURRENT NAME SERVER

•    argocd.bla.de  argocd.bla.de
  

argocd cluster list
SERVER NAME VERSION STATUS MESSAGE PROJECT
https://api-1.bla.de:6443 hcp-stg-lb 1.31 Successful
https://api-2.bla.de:6443 hcp-pro-lb 1.31 Successful
https://kubernetes.default.svc hcp-inf 1.31 Successful

$ argocd version
argocd: v3.0.12+ed1e239
BuildDate: 2025-07-25T23:01:05Z
GitCommit: ed1e2397ef9af6d23b284e39d504308cdda1957b
GitTreeState: clean
GoVersion: go1.24.5
Compiler: gc
Platform: darwin/arm64
argocd-server: v3.1.0+03c4ad8
BuildDate: 2025-08-13T20:38:38Z
GitCommit: 03c4ad854c1e6d922a121cd40f505d9bc6e402da
GitTreeState: clean
GoVersion: go1.24.6
Compiler: gc
Platform: linux/amd64
Kustomize Version: v5.7.0 2025-06-28T07:00:07Z
Helm Version: v3.18.4+gd80839c
Kubectl Version: v0.33.1
Jsonnet Version: v0.21.0

[darksworm]

Could you share a redacted copy of your argocd config?
Be careful, it contains access tokens and such - I only care about which keys are present

The config should live in $XDG_CONFIG_HOME/argocd/config or ~/.config/argocd/config.

its also possible that argonaut failed to locate the config file, you can try pointing to it explicitly:

ARGOCD_CONFIG=/path/to/config argonaut

[1337andre]

hi thanks for response!

cat $HOME/.config/argocd/config
contexts:
- name: argocd.blub.de
  server: argocd.blub.de
  user: argocd.blub.de
current-context: argocd.blub.de
prompts-enabled: false
servers:
- grpc-web-root-path: ""
  server: argocd.blub.de
users:
- auth-token: <redacted>
  name: argocd.blub.de
  refresh-token: <redacted>

same issue with

ARGOCD_CONFIG=$HOME/.config/argocd/config argonaut

[darksworm]

Very curious - I don't immediately see what's wrong.

I'll add more descriptive error output to the authentication steps in the next couple days and get back to you for further testing

[darksworm]

@1337andre I've shipped a new version!

You should now see more information about what went wrong, and also logs (the app should show you how to see the logs on the error screen)

Please give the new version a go and share screenshots of the error and a copy-paste the logs if the problem still occurs.

[darksworm]

Since there has been no reply for more than 2 weeks, I'll consider this issue as stale and close it. If you still experience this, please open a new issue.

[1337andre]

Sorry for the late reply. I've been on vacation for the past few weeks.

here are the logs

{"level":30,"time":"2025-09-12T06:33:34.720Z","pid":18991,"hostname":"myhostname","context":"main","data":{"sessionId":"2025-09-12-06-33-34-718","logFile":"/var/folders/hj/p1gs1xmn77b6jl0cfnpw_yvh0000gn/T/argonaut-session-2025-09-12-06-33-34-718.log"},"msg":"Argonaut session started"}
{"level":30,"time":"2025-09-12T06:33:34.741Z","pid":18991,"hostname":"myhostname","context":"boot","msg":"Loading ArgoCD config…"}
{"level":20,"time":"2025-09-12T06:33:34.741Z","pid":18991,"hostname":"myhostname","msg":"Begin loading Argo CD cli config"}
{"level":20,"time":"2025-09-12T06:33:34.754Z","pid":18991,"hostname":"myhostname","context":"view:loading:clusters","msg":"Fetching API version"}
{"level":20,"time":"2025-09-12T06:33:34.867Z","pid":18991,"hostname":"myhostname","context":"view:loading:clusters","msg":"Fetched API version"}
{"level":50,"time":"2025-09-12T06:33:34.920Z","pid":18991,"hostname":"myhostname","context":"view:loading:clusters|auth","msg":"user info fetch fail: unable to get local issuer certificate"}
{"level":30,"time":"2025-09-12T06:33:37.914Z","pid":18991,"hostname":"myhostname","context":"view:auth-required:clusters|logs","msg":"Opening logs…"}

we use internal pki for certs. but custom root ca ist installed on my mac

[darksworm]

I believe the issue is clear now - the app is not correctly loading the trusted certs from the keychain.

For now, you can try supplying the cert like so

NODE_EXTRA_CA_CERTS=[your CA certificate file path] argonaut

Meanwhile I am working on v2.0 of the app, which will come out in the coming weeks, and I'll include a nicer, documented solution for this - most likely you'll still have to explicitly supply the trusted certs, as that seems to be the simplest portable solution no matter the host os.

[1337andre]

thanks a lot! now it works fine for me