-
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
Add Github identity provider automatically into the Keycloak server in time of launching of Eclipse Che Multi User #7899
Comments
added 4 types of client id/secret pairs for each qa-slave:
|
Done. after some discussion we come to conclusion that we should not put that
to any deploy script but add this to CHE docs |
|
@patlachance in docs we describe how to configure it manually with KC Admin panel. |
@riuvshin I agree that KC CLI doc is should be in KC but I thought that this particular line of code with useful and Che specific parameters could be included in Che’s doc. |
I think we can add this, @eivantsov WDYT? |
@riuvshin but we need GitHub app with the right redirect URL. Yes, we can add a provider with dummy data but it is helpful at all? Or do you mean adding such CLI instructions to docs? I think a UI is a better experience. But we can do that of course |
I mean should we have just an example of how to do the same but using CLI ? |
Yeah, that makes sense. Will do |
@riuvshin yes, exactly! |
Description
It may be useful to add Github identity provider automatically into the Keycloak server in time of launching of Eclipse Che Multi User to compensate removal of support of
CHE_OAUTH_GITHUB_CLIENTID
andCHE_OAUTH_GITHUB_CLIENTSECRET
variables as part of issue #5943.Command to add github provider through the Keycloak's Admin CLI:
Created provider can be observed in the Keycloak Administration Console:
Authorization callback URL
OS and version:
Eclipse Che 6.x
The text was updated successfully, but these errors were encountered: