-
Notifications
You must be signed in to change notification settings - Fork 180
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
Probleme using OIDC authentification #39
Comments
|
Hey. Got the Exact same problem. It would be good to have some debug information. I know that this often happens with X509 Self Signed Certfs. Got it fixed by using a LetsEncrypt cert. There should be a better error message for helping us understanding. |
@JrCs Have you resolved it ? |
As a temporary workaround you can set node env var
This make it work but this is not really secure. A fix to provide a custom RootCa would be great :) |
No it's not resolved for me. |
Same here for 1.19.7 cluster. It did not work even when I added the binding to |
I have exactly the same problem. It works fine with minikube, but in cluster v1.20 it fails. Any chance to find the solution? |
Hi guys, could you firstly check your server logs? |
Same issue from when using OIDC In UI logs i tried set the env variable |
New stable was released and we fixed two pieces of documentation flaws. |
Hi when i try to use my oidc (keycloak) with k8dash it doesn't work.
In the pod logs i have:
and in the browser network tab for the path:
/apis/authorization.k8s.io/v1/selfsubjectrulesreviews
i have the response:I don't understand why k8dash use the system:anonymous account.
I use k8s version 1.15.4
The text was updated successfully, but these errors were encountered: