-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Configure OpenShift oAuth client for the OpenShift oAuth provider by operator #16199
Comments
@tolusha adding |
setting P1 but I'm not sure about priority for this particular issue |
@vinokurig workspaces:start is a chectl command, you want to automate the creation of the client at the operator level right? |
In the case when |
It supposed to be automated at the operator level, but @davidfestal |
Currently I am stuck on getting the openshift endpoint url by |
Depends on #16488. It will bring the ability to use openshift oauth provider as a keycloack identity provider, similar to |
Since we have switched to keycloak authentication (#16488) the openshift oauth API uses existing OAuth client which is already created by the operator. |
Is your enhancement related to a problem? Please describe.
The OpenShift oAuth provider which was introduced by #15963 must be manually configured to corresponding OpenShift oAuth client: https://www.eclipse.org/che/docs/che-7/configuring-openshift-oauth/. We can get rid of manual configuring by applying a new option for
workspace:start
command in the che-operator (similar to--os-oauth
in thechectl
) which will create a new oAuth client for OpenShift and then propagate related values to the OpenShift oAuth provider.Describe the solution you'd like
Describe alternatives you've considered
Additional context
depends on #15963
The text was updated successfully, but these errors were encountered: