Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenID Connect support #118

Open
rcny opened this issue Sep 12, 2019 · 1 comment
Open

OpenID Connect support #118

rcny opened this issue Sep 12, 2019 · 1 comment

Comments

@rcny
Copy link

rcny commented Sep 12, 2019

Hello!

Just stumbled upon this really amazing tool, but it's impossible for me to use it in my daily job routines because of lack of the OIDC authn. Is there any possibility for this authn strategy to appear in Click in the foreseeable future?

[some-context] [some-ns] [none] > nodes
No update command specified, can't update
Couldn't get an authentication token. You can try exiting Click and running a kubectl command against the cluster to refresh it. Also please report this error on the Click github page.
Server Error: nodes is forbidden: User "system:anonymous" cannot list resource "nodes" in API group "" at the cluster scope

User configuration from my kubeconfig file (values were edited):

- name: mrcat
  user:
    auth-provider:
      config:
        client-id: blah
        client-secret: wow
        id-token: blah
        idp-certificate-authority-data: wow
        idp-issuer-url: https://blah
        refresh-token: wow
      name: oidc
@ITman1
Copy link

ITman1 commented Feb 21, 2020

I do use OIDC thanks to this small hack: ITman1@b3c41cd It is of course not viable solution because it does not refresh tokens so you have to do auth again - time to time...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants