Configuring a basic authentication identity provider

Configure a basic-authentication identity provider for users to log in to OKD with credentials validated against a remote identity provider. Basic authentication is a generic back-end integration mechanism.

About identity providers in OKD

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.

About basic authentication

Basic authentication is a generic back-end integration mechanism that allows users to log in to OKD with credentials validated against a remote identity provider.

Because basic authentication is generic, you can use this identity provider for advanced authentication configurations.

With basic authentication configured, users send their user name and password to OKD, which then validates those credentials against a remote server by making a server-to-server request, passing the credentials as a basic authentication header. This requires users to send their credentials to OKD during login.

User names and passwords are validated against a remote URL that is protected by basic authentication and returns JSON.

A 401 response indicates failed authentication.

A non-200 status, or the presence of a non-empty “error” key, indicates an error:

{"error":"Error message"}

A 200 status with a sub (subject) key indicates success:

{"sub":"userid"} (1)

A successful response can optionally provide additional data, such as:

• A display name using the name key. For example:

  {"sub":"userid", "name": "User Name", ...}

• An email address using the email key. For example:

  {"sub":"userid", "email":"user@example.com", ...}

• A preferred user name using the preferred_username key. This is useful when the unique, unchangeable subject is a database key or UID, and a more human-readable name exists. This is used as a hint when provisioning the OKD user for the authenticated identity. For example:

  {"sub":"014fbff9a07c", "preferred_username":"bob", ...}

Creating the secret

Identity providers use OKD Secret objects in the openshift-config namespace to contain the client secret, client certificates, and keys.

• You can define an OKD 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 OKD 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

Creating a config map

Identity providers use OKD ConfigMap objects in the openshift-config namespace to contain the certificate authority bundle. These are primarily used to contain certificate bundles needed by the identity provider.

Procedure

• Define an OKD ConfigMap object containing the certificate authority by using the following command. The certificate authority must be stored in the ca.crt key of the ConfigMap object.

  $ oc create configmap ca-config-map --from-file=ca.crt=/path/to/ca -n openshift-config

Sample basic authentication CR

The following custom resource (CR) shows the parameters and acceptable values for a basic authentication identity provider.

Basic authentication CR

apiVersion: config.openshift.io/v1
kind: OAuth
metadata:
  name: cluster
spec:
  identityProviders:
  - name: basicidp (1)
    mappingMethod: claim (2)
    type: BasicAuth
    basicAuth:
      url: https://www.example.com/remote-idp (3)
      ca: (4)
        name: ca-config-map
      tlsClientCert: (5)
        name: client-cert-secret
      tlsClientKey: (6)
        name: client-key-secret

Additional resources

• See Identity provider parameters for information on parameters, such as mappingMethod, that are common to all identity providers.

Adding an identity provider to your clusters

After you install your cluster, add an identity provider to it so your users can authenticate.

Prerequisites

• Create an OKD cluster.

• Create the custom resource (CR) for your identity providers.

• You must be logged in as an administrator.

Procedure

1. Apply the defined CR:

   $ oc apply -f </path/to/CR>

   If a CR does not exist, oc apply creates a new CR and might trigger the following warning: Warning: oc apply should be used on resources created by either oc create —save-config or oc apply. In this case you can safely ignore this warning.

2. Log in to the cluster as a user from your identity provider, entering the password when prompted.

   $ oc login -u <username>

3. Confirm that the user logged in successfully, and display the user name.

   $ oc whoami

Example Apache HTTPD configuration for basic identity providers

The basic identify provider (IDP) configuration in OKD 4 requires that the IDP server respond with JSON for success and failures. You can use CGI scripting in Apache HTTPD to accomplish this. This section provides examples.

Example /etc/httpd/conf.d/login.conf

<VirtualHost *:443>
  # CGI Scripts in here
  DocumentRoot /var/www/cgi-bin
  # SSL Directives
  SSLEngine on
  SSLCipherSuite PROFILE=SYSTEM
  SSLProxyCipherSuite PROFILE=SYSTEM
  SSLCertificateFile /etc/pki/tls/certs/localhost.crt
  SSLCertificateKeyFile /etc/pki/tls/private/localhost.key
  # Configure HTTPD to execute scripts
  ScriptAlias /basic /var/www/cgi-bin
  # Handles a failed login attempt
  ErrorDocument 401 /basic/fail.cgi
  # Handles authentication
  <Location /basic/login.cgi>
    AuthType Basic
    AuthName "Please Log In"
    AuthBasicProvider file
    AuthUserFile /etc/httpd/conf/passwords
    Require valid-user
  </Location>
</VirtualHost>

Example /var/www/cgi-bin/login.cgi

#!/bin/bash
echo "Content-Type: application/json"
echo ""
echo '{"sub":"userid", "name":"'$REMOTE_USER'"}'
exit 0

Example /var/www/cgi-bin/fail.cgi

#!/bin/bash
echo "Content-Type: application/json"
echo ""
echo '{"error": "Login failure"}'
exit 0

File requirements

These are the requirements for the files you create on an Apache HTTPD web server:

• login.cgi and fail.cgi must be executable (chmod +x).

• login.cgi and fail.cgi must have proper SELinux contexts if SELinux is enabled: restorecon -RFv /var/www/cgi-bin, or ensure that the context is httpd_sys_script_exec_t using ls -laZ.

• login.cgi is only executed if your user successfully logs in per Require and Auth directives.

• fail.cgi is executed if the user fails to log in, resulting in an HTTP 401 response.

Basic authentication troubleshooting

The most common issue relates to network connectivity to the backend server. For simple debugging, run curl commands on the master. To test for a successful login, replace the <user> and <password> in the following example command with valid credentials. To test an invalid login, replace them with false credentials.

$ curl --cacert /path/to/ca.crt --cert /path/to/client.crt --key /path/to/client.key -u <user>:<password> -v https://www.example.com/remote-idp

Successful responses

A 200 status with a sub (subject) key indicates success:

{"sub":"userid"}

The subject must be unique to the authenticated user, and must not be able to be modified.

A successful response can optionally provide additional data, such as:

• A display name using the name key:

  {"sub":"userid", "name": "User Name", ...}

• An email address using the email key:

  {"sub":"userid", "email":"user@example.com", ...}

• A preferred user name using the preferred_username key:

  {"sub":"014fbff9a07c", "preferred_username":"bob", ...}

  The preferred_username key is useful when the unique, unchangeable subject is a database key or UID, and a more human-readable name exists. This is used as a hint when provisioning the OKD user for the authenticated identity.

Failed responses

• A 401 response indicates failed authentication.

• A non-200 status or the presence of a non-empty “error” key indicates an error: {"error":"Error message"}