$ oc create secret generic <secret_name> --from-literal=clientSecret=<secret> -n openshift-config
Configure a google
identity provider using
Google’s OpenID Connect integration.
Using Google as an identity provider requires users to get a token using
|
Using Google as an identity provider allows any Google user to authenticate to your server.
You can limit authentication to members of a specific hosted domain with the
|
By default, only a kubeadmin
user exists on your cluster. To specify an
identity provider, you must create a custom resource (CR) that describes
that identity provider and add it to the cluster.
OpenShift Container Platform user names containing |
Identity providers use OpenShift Container Platform Secret
objects in the openshift-config
namespace to contain the client secret, client certificates, and keys.
You can define an OpenShift Container Platform Secret
object containing a string
by using the following command.
$ oc create secret generic <secret_name> --from-literal=clientSecret=<secret> -n openshift-config
You can define an OpenShift Container Platform Secret
object containing the contents of a
file, such as a certificate file, by using the following command.
$ oc create secret generic <secret_name> --from-file=/path/to/file -n openshift-config
The following custom resource (CR) shows the parameters and acceptable values for a Google identity provider.
apiVersion: config.openshift.io/v1
kind: OAuth
metadata:
name: cluster
spec:
identityProviders:
- name: googleidp (1)
mappingMethod: claim (2)
type: Google
google:
clientID: {...} (3)
clientSecret: (4)
name: google-secret
hostedDomain: "example.com" (5)
1 | This provider name is prefixed to the Google numeric user ID to form an identity name. It is also used to build the redirect URL. |
2 | Controls how mappings are established between this provider’s identities and user objects. |
3 | The client ID of a registered
Google project. The project must be configured with a redirect URI of
https://oauth-openshift.apps.<cluster-name>.<cluster-domain>/oauth2callback/<idp-provider-name> . |
4 | Reference to an OpenShift Container Platform Secret object containing the client secret
issued by Google. |
5 | A
hosted domain
used to restrict sign-in accounts. Optional if the lookup mappingMethod
is used. If empty, any Google account is allowed to authenticate. |
See Identity provider parameters for information on parameters, such as mappingMethod
, that are common to all identity providers.
After you install your cluster, add an identity provider to it so your users can authenticate.
Create an OpenShift Container Platform cluster.
Create the custom resource (CR) for your identity providers.
You must be logged in as an administrator.
Apply the defined CR:
$ oc apply -f </path/to/CR>
If a CR does not exist, |
Obtain a token from the OAuth server.
As long as the kubeadmin
user has been removed, the oc login
command provides instructions on how to access a web page where you can retrieve the token.
You can also access this page from the web console by navigating to (?) Help → Command Line Tools → Copy Login Command.
Log in to the cluster, passing in the token to authenticate.
$ oc login --token=<token>
This identity provider does not support logging in with a user name and password. |
Confirm that the user logged in successfully, and display the user name.
$ oc whoami