docs/doc/source/security/kubernetes/configure-oidc-auth-applications.rst

Configure OIDC Auth Applications

The oidc-auth-apps application is a system application that needs to be configured to use a remote Windows Active Directory server to authenticate users of the Kubernetes API. The oidc-auth-apps is packaged in the ISO and uploaded by default.

• You must have configured the Kubernetes kube-apiserver to use the oidc-auth-apps identity provider for validation of tokens in Kubernetes API requests, which use authentication. For more information on configuring the Kubernetes kube-apiserver, see Configure Kubernetes for OIDC Token Validation while Bootstrapping the System <configure-kubernetes-for-oidc-token-validation-while-bootstrapping-the-system> or Configure Kubernetes for OIDC Token Validation after Bootstrapping the System <configure-kubernetes-for-oidc-token-validation-after-bootstrapping-the-system>.

• You must have a signed certificate (dex-cert.pem file), and private key (dex-key.pem file) for the dex Identity Provider of oidc-auth-apps.

  This certificate must have the 's floating OAM IP Address in the list. If you are planning on defining and using a DNS name for the 's floating OAM IP Address, then this DNS name must also be in the list. Refer to the documentation for the external that you are using, in order to create a signed certificate and key.

  If you are using an intermediate to sign the dex certificate, include both the dex certificate (signed by the intermediate ), and the intermediate 's certificate (signed by the Root ) in that order, in dex-cert.pem.

• You must have the certificate of the (dex-ca.pem file) that signed the above certificate for the dex Identity Provider of oidc-auth-apps.

  If an intermediate was used to sign the dex certificate and both the dex certificate and the intermediate certificate was included in dex-cert.pem, then the dex-ca.pem file should contain the root 's certificate.

  If the signing (dex-ca.pem) is not a well-known trusted , you must ensure the system trusts the by specifying it either during the bootstrap phase of system installation, by specifying 'ssl_ca_cert: dex-ca.pem' in the ansible bootstrap overrides localhost.yml file, or by using the system certificate-install -m ssl_ca dex-ca.pem command.

1. Create the secret, local-dex.tls, with the certificate and key, to be used by the oidc-auth-apps, as well as the secret, dex-client-secret, with the 's certificate that signed the local-dex.tls certificate.

   For example, assuming the cert and key pem files for creating these secrets are in /home/sysadmin/ssl/, run the following commands to create the secrets:

   Note

   oidc-auth-apps looks specifically for secrets of these names in the kube-system namespace.

   For the generic secret dex-client-secret, the filename must be 'dex-ca.pem'.

   ~(keystone_admin)$ kubectl create secret tls local-dex.tls --cert=ssl/dex-cert.pem --key=ssl/dex-key.pem -n kube-system
   
   ~(keystone_admin)$ kubectl create secret generic dex-client-secret --from-file=/home/sysadmin/ssl/dex-ca.pem -n kube-system

   Create the secret wadcert with the 's certificate that signed the Active Directory's certificate using the following command:

   ~(keystone_admin)$ kubectl create secret generic wadcert --from-file=ssl/AD_CA.cer -n kube-system

2. Specify user overrides for oidc-auth-apps application, by using the following command:

   ~(keystone_admin)$ system helm-override-update oidc-auth-apps dex kube-system --values /home/sysadmin/dex-overrides.yaml

   The dex-overrides.yaml file contains the desired dex helm chart overrides (that is, the LDAP connector configuration for the Active Directory service, optional token expiry, and so on.), and volume mounts for providing access to the wadcert secret, described in this section.

   For the complete list of dex helm chart values supported, see Dex Helm Chart Values <https://github.com/helm/charts/blob/92b6289ae93816717a8453cfe62bad51cbdb 8ad0/stable/dex/values.yaml>__. For the complete list of parameters of the dex LDAP connector configuration, see Dex LDAP Connector Configuration <https://github.com/dexidp/dex/blob/master/Documentation/connectors/ldap. md>__.

   The example below configures a token expiry of ten hours, a single LDAP connector to an Active Directory service using HTTPS (LDAPS) using the wadcert secret configured in this section, the required Active Directory service login information (that is, bindDN, and bindPW), and example userSearch, and groupSearch clauses.

   config:
     expiry:
       idTokens: "10h"
     connectors:
     - type: ldap
       name: OpenLDAP
       id: ldap
       config:
         host: pv-windows-acti.cumulus.wrs.com:636
         rootCA: /etc/ssl/certs/adcert/AD_CA.cer
         insecureNoSSL: false
         insecureSkipVerify: false
         bindDN: cn=Administrator,cn=Users,dc=cumulus,dc=wrs,dc=com
         bindPW: Li69nux*
         usernamePrompt: Username
         userSearch:
           baseDN: ou=Users,ou=Titanium,dc=cumulus,dc=wrs,dc=com
           filter: "(objectClass=user)"
           username: sAMAccountName
           idAttr: sAMAccountName
           emailAttr: sAMAccountName
           nameAttr: displayName
         groupSearch:
           baseDN: ou=Groups,ou=Titanium,dc=cumulus,dc=wrs,dc=com
           filter: "(objectClass=group)"
           userAttr: DN
           groupAttr: member
           nameAttr: cn
   extraVolumes:
   - name: certdir
     secret:
       secretName: wadcert
   extraVolumeMounts:
   - name: certdir
     mountPath: /etc/ssl/certs/adcer

   If more than one Windows Active Directory service is required for authenticating the different users of the , multiple 'ldap' type connectors can be configured; one for each Windows Active Directory service.

   If more than one userSearch plus groupSearch clauses are required for the same Windows Active Directory service, multiple 'ldap' type connectors, with the same host information but different userSearch plus groupSearch clauses, should be used.

   Whenever you use multiple 'ldap' type connectors, ensure you use unique 'name:' and 'id:' parameters for each connector.

3. Use the system application-apply command to apply the configuration:

   ~(keystone_admin)$ system application-apply oidc-auth-apps