Hello, I've installed both dex and dex-k8s-authenticator to use Goog

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="37

You must be logged in to the server about dex-k8s-authenticator HOT 3 CLOSED

mintel commented on June 6, 2024 1

You must be logged in to the server

from dex-k8s-authenticator.

Comments (3)

nabadger commented on June 6, 2024 1

@FuzzOli87 So I would start by looking at the kubeconfig that you have generated.

At this point it's really about that config, Kubernetes, and the Dex server (for refreshing tokens)

So some things to check:

Confirm you are using the generated config
Confirm you can reach the idp-issuer-url
Check that the expected k8s context is in use via kubectl config get-contexts - if you have multiple contexts (users/clusters) configured, this will tell you what context you're actually using

I would also look at the generated id-token in the kubeconfig file.

It's a JWT token which is comprised of 3 parts separated by .

If you grab the middle component and base64 decode it you should be able to confirm the groups that the user have (this is the same level of information that dex-k8s-authenticator provides you when generate the kubeconfig details).

If that all looks good - you may want to look at your kube-apiserver logs

from dex-k8s-authenticator.

nabadger commented on June 6, 2024

Closing for now - let me know if you still have issues.

from dex-k8s-authenticator.