treasuremap/manifests/function/dex-aio
Zuul e190ae2af3 Merge "Changes in Treasuremap for HelmRepository function" 2021-06-09 20:41:52 +00:00
..
replacements Externalize KRM function versions 2021-06-03 14:07:21 -05:00
README.md Treasuremap - Dex, API server & LDAP integration 2021-05-12 14:48:48 +00:00
dex-cert-issuer.yaml Changes in dex function to work for both target cluster as well as sub-clusters along with few enhancements 2021-05-20 22:38:15 +05:30
dex-helmrelease.yaml Changes in Treasuremap for HelmRepository function 2021-06-09 20:28:47 +05:30
kustomization.yaml Changes in dex function to work for both target cluster as well as sub-clusters along with few enhancements 2021-05-20 22:38:15 +05:30

README.md

DEX-AIO function

The DEX-AIO function implements the Dex Authentication service. It contains the HelmRelease manifest for dex-aio, which contains the LDAP connector customization as well as certificates to be used.

The certificate (Secret) used by dex-aio will be generated by the cert-manager, which will be signed by CA that is generated in the Ephemeral cluster and copied to the Target cluster during the airshipctl phase run clusterctl-move operation.

Before you can deploy this helm release, you will need to update the following:

      ldap:
        bind_password: "your LDAP bind password"
        config:
          host: "your LDAP FQDN"
          bind_dn: "your LDAP bind username"

Also, in the same helm release you will need to update the search criteria for the user and group based on your LDAP schema. See the attributes under spec.values.ldap to update below:

      user_search:
        base_dn: dc=testservices,dc=test,dc=com
        filter: "(objectClass=person)"
        username: cn
        idAttr: cn
        emailAttr: name
        nameAttr: name
      group_search:
        base_dn: ou=groups,dc=testservices,dc=test,dc=com
        filter: "(objectClass=group)"
        userMatchers:
          userAttr: name
          groupAttr: member
        nameAttr: name