OpenID Connect support (IBM Cloud)
See original GitHub issueKubebox always wants me to enter login information, whereas it just should use the defined one.
To login into our IBM cloud environment, we need to export the KUBECONFIG environment variable pointing to a configuration which includes the following:
apiVersion: v1
clusters:
- cluster:
certificate-authority: ...pem
The .pem file is in the same folder as the kubeconfig file. I’m guessing somehow it’s not read and thus I cannot pass the login screen.
Should this work out of the box? kubectl works without any problems.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Configuring OpenID Connect single sign-on in the custom ...
You can configure IBM Security Verify Access and mobile applications as OpenID Connect relying parties . Procedure. Navigate to the Sign-on tab. In...
Read more >OpenID Connect - IBM
OpenID Connect is a simple identity protocol and open standard that is built on the OAuth 2.0 protocol that enables client applications to...
Read more >Securing your APIs with OpenID Connect - IBM
IBM® API Connect for IBM Cloud supports OIDC provider flow by building on top of the existing OAuth 2 provider capabilities.
Read more >OIDC discovery document - IBM Cloud Docs
OpenID Connect supports a discovery protocol that contains information that you can use to configure your apps and authenticate users such as tokens...
Read more >Configuring OpenID Connect - IBM
The system supports authentication against an OpenID Connect (OIDC) provider. When enabled, the IBM Cloud Object Storage Manager™ will support single ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
After looking a little bit into the source, it seems like the certificate is not the problem but the lack of support for oidc user authentication which looks like: https://kubernetes.io/docs/reference/access-authn-authz/authentication/#option-1-oidc-authenticator
Any plans to support this?
Let me close this. Feel free to report any issues you might find.