Disable OIDC provider and enable it post installation through installer=operator
See original GitHub issueSummary
Che Version: 7.51.0 Chectl Version : 7.51.0
While installing we are using chectl with --skip-oidc-provider-check
and the pods are up however the che pods are trying to use the default oidc provier.
However, we want eclipce-che to use some other oidc provider however we are not sure how to provide that, we went through the documentation and we observered to edit the CRD checluster however the documentation provided is for org.eclipse.che/v1
and we are using org.eclipse.che/v2
Please guide us to the appropriate documentation or share the URL’s which can help us to fix this problem.
Thanks in Advance
Relevant information
No response
Issue Analytics
- State:
- Created a year ago
- Comments:12 (5 by maintainers)
Top Results From Across the Web
Eclipse che 7.43.0 is always failing to deploy with k8s ... - GitHub
Summary Hi, I'm trying to install eclipse-che 7.43.0 on kubernetes cluster. This is always failing with error that Kubernetes API Server ...
Read more >Creating an IAM OIDC provider for your cluster - Amazon EKS
Your cluster has an OpenID Connect (OIDC) issuer URL associated with it. To use AWS Identity and Access Management (IAM) roles for service...
Read more >Configuring an OpenID Connect identity provider
Configure the oidc identity provider to integrate with an OpenID Connect identity provider using an Authorization Code Flow.
Read more >Red Hat CodeReady Workspaces 2.15 Installation Guide
UNINSTALLING CODEREADY WORKSPACES AFTER CRWCTL INSTALLATION ... provider will be deployed by the Operator and you will need to provide.
Read more >OpenID Connect (OIDC) authorization code flow mechanism
Then, the application exchanges this code with the OIDC provider for an ID token ... is disabled by default; let's build again by...
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
Is it possible to configure one OIDC provider, for example, named A, for the cluster but limit the access of Openshift users so that only the users from the oidc provider A can access to the checluster, but not all Openshift cluster users can access it since the cluster may have multiple oidc providers configured. @amisevsk @sparkoo @tolusha.
you have to have configured oidc provider for your cluster and same oidc must be used for Che. It’s used to authenticate and authorize users, so there is no way around it.