[che-operator] Enhancements in the way how OAuth2 providers can be configured

[skabashnyuk]

Is your task related to a problem? Please describe

• Github, Gitlab, Bitbucket should be configured in a similar way.
• Factory OAuth flow without Keycloak.

Describe the solution you'd like

• Should be possible to configure Gitlab from secret. In the same way, like it's made for Github and Bitbucket.[che-operator] Configure OAuth1 and OAuth2 integrations with K8s Secrets  #18932
• Github and Gitlab OAuth configs should be mounted as a file to che-server in the same way like it's made for Bitbucket
• Environemnt variables for clientid and secret. CHE_OAUTH2_GITHUB_CLIENTID__FILEPATH CHE_OAUTH2_GITHUB_CLIENTSECRET__FILEPATH
• Change path /home/user/eclipse-che/conf/oauth1/bitbucket/ - > /config/oauth1/bitbucket/ and /config/oauth2/github/ and /config/oauth2/gitlab/ see more Propagate Che user informations and preferences to DevWorkspaces #19061 (comment)
• Add CHE_INTEGRATION_GITLAB_SERVER__ENDPOINTS. Like https://github.com/eclipse-che/che-operator/blob/8e0966bed3c682f81bba2c2454ace33cb1e9c761/pkg/deploy/server/server_configmap.go#L314-L334

Release Notes Text

The way to configure GitHub, Bitbucket and Gitlab as Git service providers for Che workspaces has been made consistent and simpler.

[l0rd]

👍

[tolusha]

GitHub configuration secret:

kind: Secret
apiVersion: v1
metadata:
  name: github-oauth-config
  namespace: <...> 
  labels:
    app.kubernetes.io/part-of: che.eclipse.org
    app.kubernetes.io/component: oauth-scm-configuration
  annotations:
    che.eclipse.org/oauth-scm-server: github
type: Opaque
data:
  id: <...> 
  secret: <...> 

Mount env to che-server deployment:

• CHE_OAUTH2_GITHUB_CLIENTID__FILEPATH with content of id key to location /che-conf/oauth/github/id
• CHE_OAUTH2_GITHUB_CLIENTSECRET__FILEPATH with content of secret key to location /che-conf/oauth/github/secret

[tolusha]

GitLab configuration secret:

kind: Secret
apiVersion: v1
metadata:
  name: gitlab-oauth-config
  namespace: <...> 
  labels:
    app.kubernetes.io/part-of: che.eclipse.org
    app.kubernetes.io/component: oauth-scm-configuration
  annotations:
    che.eclipse.org/oauth-scm-server: gitlab
    che.eclipse.org/scm-server-endpoint: <...>  # optional
type: Opaque
data:
  id: <...> 
  secret: <...> 

Mount env to che-server deployment:

• CHE_OAUTH_GITLAB_CLIENTID__FILEPATH with content of id key to location /che-conf/oauth/gitlab/id
• CHE_OAUTH_GITLAB_CLIENTSECRET__FILEPATH with content of secret key to location /che-conf/oauth/gitlab/secret

Configmap:

• CHE_INTEGRATION_GITLAB_SERVER__ENDPOINTS with content of che.eclipse.org/scm-server-endpoint to che configmap

[devstudio-release]

sync'd to Red Hat JIRA https://issues.redhat.com/browse/CRW-2373

[max-cx]

@tolusha, do we need to add any new content to the Installation Guide or Administration Guide or End-user Guide?

Yes/No?

[max-cx]

@tolusha, I updated the Release Notes Text for this issue:

---

= Standardized configuration of OAuth 2.0 for GitLab, GitHub, and Bitbucket

This enhancement standardizes and simplifies the use of Secret config files for OAuth 2.0 configuration of git-hosting services (Gitlab, Github, and Bitbucket) for Che workspaces.

---

Feel free to okay, comment, or correct it in https://issues.redhat.com/browse/CRW-2373.
Thanks!