Este contenido no está disponible en el idioma seleccionado.

Chapter 12. TLS-e for DCN


You can enable TLS (transport layer security) on clouds designed for distributed compute node infrastructure. You have the option of either enabling TLS for public access only, or enabling TLS on every network with TLS-e, which allows for encryption on all internal and external dataflows.

You cannot enable public access on edge stacks as edge sites do not have public endpoints. For more information on TLS for public access, see Enabling SSL/TLS on Overcloud Public Endpoints.

12.1. Deploying distributed compute node architecture with TLS-e

When you configure TLS-e on Red Hat OpenStack Platform (RHOSP) distributed compute node architecture with Red Hat Identity Manager (IdM), take the following actions based on the version of Red Hat Enterprise Linux deployed for Red Hat Identity Manager.

Note

Due to differences in design between the central and edge locations, do not include the following files in edge stacks:

tls-everywhere-endpoints-dns.yaml
This file is ignored at edge sites, the endpoints that it sets are overridden by the endpoints exported from the central stack.
haproxy-public-tls-certmonger.yaml
This file causes a failed deployment as there are no public endpoints at the edge.

Procedure

  • If you are running Red Hat Enterprise Linux (RHEL) 8.2, you must upgrade RHEL to version 8.4, and then follow the directions for RHEL 8.4
  • If you are running RHEL 8.4, modify the ipa-ext.conf and ipa-options-ext.conf files:

    1. Add trusted subnets to the access control list (ACL) in the ipa-ext.conf file:

       acl "trusted_network" {
         localnets;
         localhost;
         192.168.24.0/24;
         192.168.25.0/24;
       };
    2. Allow recursion and query cache in the /etc/named/ipa-options-ext.conf file:

      allow-recursion { trusted_network; };
      allow-query-cache { trusted_network; };
    3. Restart the `named-pkcs11 service:

      systemctl restart named-pkcs11
  • If you are running a version of RHEL 7, you must add an access control instruction for your domain manually.

    1. Run the following commands on Red Hat Identity Manager to configure the ACI.

      ADMIN_PASSWORD=<redhat_01>
      DOMAIN_LEVEL_1=<local>
      DOMAIN_LEVEL_2=<redhat>
      
      cat << EOF | ldapmodify -x -D "cn=Directory Manager" -w ${ADMIN_PASSWORD}
      dn: cn=dns,dc=${DOMAIN_LEVEL_2},dc=${DOMAIN_LEVEL_1}
      changetype: modify
      add: aci
      aci: (targetattr = "aaaarecord || arecord || cnamerecord || idnsname || objectclass || ptrrecord")(targetfilter = "(&(objectclass=idnsrecord)(|(aaaarecord=)(arecord=)(cnamerecord=)(ptrrecord=)(idnsZoneActive=TRUE)))")(version 3.0; acl "Allow hosts to read DNS A/AAA/CNAME/PTR records"; allow (read,search,compare) userdn = "ldap:///fqdn=*,cn=computers,cn=accounts,dc=${DOMAIN_LEVEL_2},dc=${DOMAIN_LEVEL_1}";)
      EOF
  • Replace <redhat_01> with the administrative password that you want to set.
  • Replace <local> with the top-level domain.
  • Replace <redhat> with the second-level domain.

Additional resources

Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2026 Red Hat
Volver arriba