https://oauth-openshift.apps.<cluster-name>.<cluster-domain>/oauth2callback/<idp-provider-name>
Configure a github
identity provider to validate user names and passwords
against GitHub or GitHub Enterprise’s OAuth authentication server. OAuth
facilitates a token exchange flow between
OpenShift Dedicated and GitHub or GitHub Enterprise.
You can use the GitHub integration to connect to either GitHub or GitHub
Enterprise. For GitHub Enterprise integrations, you must provide the hostname
of your instance and can optionally provide a ca
certificate bundle to use in
requests to the server.
The following steps apply to both GitHub and GitHub Enterprise unless noted. |
Configuring GitHub authentication allows users to log in to OpenShift Dedicated with their GitHub credentials. To prevent anyone with any GitHub user ID from logging in to your OpenShift Dedicated cluster, you can restrict access to only those in specific GitHub organizations.
To use GitHub or GitHub Enterprise as an identity provider, you must register an application to use.
Register an application on GitHub:
For GitHub, click Settings → Developer settings → OAuth Apps → Register a new OAuth application.
For GitHub Enterprise, go to your GitHub Enterprise home page and then click Settings → Developer settings → Register a new application.
Enter an application name, for example My OpenShift Install
.
Enter a homepage URL, such as
https://oauth-openshift.apps.<cluster-name>.<cluster-domain>
.
Optional: Enter an application description.
Enter the authorization callback URL, where the end of the URL contains the
identity provider name
:
https://oauth-openshift.apps.<cluster-name>.<cluster-domain>/oauth2callback/<idp-provider-name>
For example:
https://oauth-openshift.apps.example-openshift-cluster.com/oauth2callback/github/
Click Register application. GitHub provides a Client ID and a Client Secret. You need these values to complete the identity provider configuration.