Michael Andrews

Yeah - this is still happening. I'm on 2.10.9.

It's a hardcoded info log https://github.com/argoproj/argo-cd/blob/f358e8ddbab3af0de50ee18584b38f588a71ed2b/util/settings/settings.go#L1540

This really needs to get fixed. Priority should be: * `alb.ingress.kubernetes.io/tag` * `IngressClassParams` * then `--default-tags` on the controller args. It is _very_ odd to have `default-tags` be an "override"...

Just found this - and it is blocking a big release for us. We're moving from the bundled dex to our company IdP. When NOT using PKCE the redir is...

To clarify - we were using Dex previously and we added the `redirectURI` to the connectors config which is probabaly why the redirect contained the correct path. I actually do...

One more thing - the path is not taken into account when redirecting to `/applications` after the flow succeeds. It should. For now I have worked around both these issues...

Could probably just use the settings from the argocd server params to construct the URL. Example: ```yaml configs: params: server.rootpath: /argocd ```

I will also add that the session expiration flow seems to not take into account PKCE when enabled. Tries to re-auth using /auth/callback without "code" flow. And the PKCE error...

To recap all the issues here: * Base path is not taken into account when constructing the `/pkce/verify` path. * Base path is not taken into account when constructing the...

Also, valid args are not listed in the help. I think there is an issue for this already. This might be what keeps me using sub-commands.