Chapter 21. Using the KDC Proxy in IdM


Some administrators might choose to make the default Kerberos ports inaccessible in their deployment. To allow users, hosts, and services to obtain Kerberos credentials, you can use the HTTPS service as a proxy that communicates with Kerberos via the HTTPS port 443.

In Identity Management (IdM), the Kerberos Key Distribution Center Proxy (KKDCP) provides this functionality.

On an IdM server, KKDCP is enabled by default and available at https://<server.idm.example.com>/KdcProxy. On an IdM client, you must change its Kerberos configuration to access the KKDCP.

21.1. Configuring an IdM client to use KKDCP

Configure Identity Management (IdM) clients to use Kerberos Key Distribution Center Proxy (KKDCP) to access Kerberos services through HTTPS port 443. This enables authentication when standard Kerberos ports are blocked by firewalls or network policies.

Prerequisites

  • You have root access to the IdM client.

Procedure

  1. Open the /etc/krb5.conf file for editing.
  2. In the [realms] section, enter the URL of the KKDCP for the kdc, admin_server, and kpasswd_server options:

    [realms]
    EXAMPLE.COM = {
      kdc = https://kdc.example.com/KdcProxy
      admin_server = https://kdc.example.com/KdcProxy
      kpasswd_server = https://kdc.example.com/KdcProxy
      default_domain = example.com
    }

    For redundancy, you can add the parameters kdc, admin_server, and kpasswd_server multiple times to indicate different KKDCP servers.

  3. Restart the sssd service to make the changes take effect:

    # systemctl restart sssd

Verify that the Kerberos Key Distribution Center Proxy (KKDCP) is enabled on an Identity Management (IdM) server to confirm that Kerberos clients can authenticate through the HTTPS proxy rather than connecting directly to the KDC.

On an IdM server, KKDCP is automatically enabled each time the Apache web server starts if the attribute and value pair ipaConfigString=kdcProxyEnabled exists in the directory. When enabled, the symbolic link /etc/httpd/conf.d/ipa-kdc-proxy.conf is created.

You can verify if the KKDCP is enabled on the IdM server, even as an unprivileged user.

Procedure

  • Check that the symbolic link exists:

    $ ls -l /etc/httpd/conf.d/ipa-kdc-proxy.conf
    lrwxrwxrwx. 1 root root 36 Jun 21  2020 /etc/httpd/conf.d/ipa-kdc-proxy.conf -> /etc/ipa/kdcproxy/ipa-kdc-proxy.conf

    The output confirms that KKDCP is enabled.

21.3. Disabling KKDCP on an IdM server

Disable the Kerberos Key Distribution Center Proxy (KKDCP) on Identity Management (IdM) servers to switch to direct KDC connectivity.

Prerequisites

  • You have root access to the IdM server.

Procedure

  1. Remove the ipaConfigString=kdcProxyEnabled attribute and value pair from the directory:

    # ipa-ldap-updater /usr/share/ipa/kdcproxy-disable.uldif
    Update complete
    The ipa-ldap-updater command was successful
  2. Restart the httpd service:

    # systemctl restart httpd.service

    KKDCP is now disabled on the current IdM server.

Verification

  • Verify that the symbolic link does not exist:

    $ ls -l /etc/httpd/conf.d/ipa-kdc-proxy.conf
    ls: cannot access '/etc/httpd/conf.d/ipa-kdc-proxy.conf': No such file or directory

21.4. Re-enabling KKDCP on an IdM server

Restore Kerberos Key Distribution Center Proxy (KKDCP) functionality on an Identity Management (IdM) server to enable clients to obtain Kerberos tickets through HTTPS.

Prerequisites

  • You have root access to the IdM server.

Procedure

  1. Add the ipaConfigString=kdcProxyEnabled attribute and value pair to the directory:

    # ipa-ldap-updater /usr/share/ipa/kdcproxy-enable.uldif
    Update complete
    The ipa-ldap-updater command was successful
  2. Restart the httpd service:

    # systemctl restart httpd.service

    KKDCP is now enabled on the current IdM server.

Verification

  • Verify that the symbolic link exists:

    $ ls -l /etc/httpd/conf.d/ipa-kdc-proxy.conf
    lrwxrwxrwx. 1 root root 36 Jun 21  2020 /etc/httpd/conf.d/ipa-kdc-proxy.conf -> /etc/ipa/kdcproxy/ipa-kdc-proxy.conf

Configure the Identity Management (IdM) KKDCP server to use TCP when communicating with Active Directory realms. TCP transport improves reliability when connecting to multiple Kerberos servers in AD environments.

Prerequisites

  • You have root access.

Procedure

  1. Set the use_dns parameter in the [global] section of the /etc/ipa/kdcproxy/kdcproxy.conf file to false.

    [global]
    use_dns = false
  2. Put the proxied realm information into the /etc/ipa/kdcproxy/kdcproxy.conf file. For example, for the [AD.EXAMPLE.COM] realm with proxy list the realm configuration parameters as follows:

    [AD.EXAMPLE.COM]
    kerberos = kerberos+tcp://1.2.3.4:88 kerberos+tcp://5.6.7.8:88
    kpasswd = kpasswd+tcp://1.2.3.4:464 kpasswd+tcp://5.6.7.8:464
    Important

    The realm configuration parameters must list multiple servers separated by a space, as opposed to /etc/krb5.conf and kdc.conf, in which certain options may be specified multiple times.

  3. Restart Identity Management (IdM) services:

    # ipactl restart

Configure the Identity Management (IdM) Kerberos Key Distribution Center Proxy (KKDCP) server to enable DNS-based KDC discovery for Active Directory (AD) realms already declared in the MIT Kerberos configuration. Use this approach when your AD realms are defined in /etc/krb5.conf or /etc/krb5.conf.d/. In a standard IdM deployment with an AD trust, this is the case by default.

Prerequisites

  • You have root access.
  • Your AD realms are declared in the MIT Kerberos configuration (/etc/krb5.conf or /etc/krb5.conf.d/).

Procedure

  1. In the /etc/ipa/kdcproxy/kdcproxy.conf file, in the [global] section, set configs = mit and use_dns = true:

    [global]
    configs = mit
    use_dns = true

    The configs = mit setting imports the MIT Kerberos configuration into kdcproxy, making realms declared there available for DNS-based KDC discovery.

  2. Optional: To re-enable DNS-based KDC discovery for all realms, add the dns_realm_discovery parameter to the [global] section.

    Warning

    Red Hat recommends against setting dns_realm_discovery = true. It restores the pre-CVE-2025-59088 behavior and enables any client to trigger DNS SRV record lookups for arbitrary realm names, which can be exploited to probe internal network addresses and exfiltrate data via server-side request forgery.

    [global]
    configs = mit
    use_dns = true
    dns_realm_discovery = true
  3. Restart Identity Management (IdM) services:

    # ipactl restart

Configure the Identity Management (IdM) KKDCP server to enable DNS-based KDC discovery for Active Directory (AD) realms by declaring them explicitly in the kdcproxy configuration. Use this approach when your AD realms are not defined in the MIT Kerberos configuration, or when configs = mit is not set.

Prerequisites

  • You have root access.

Procedure

  1. In the /etc/ipa/kdcproxy/kdcproxy.conf file, in the [global] section, set the use_dns parameter to true:

    [global]
    use_dns = true
  2. Add a dedicated section for each Active Directory realm that should use DNS-based KDC discovery. Empty sections are sufficient to add a realm to the allow-list. For example:

    [SUB1.AD.EXAMPLE.COM]
    [SUB2.AD.EXAMPLE.COM]

    To include all sub-realms within an AD forest without listing each one individually, use a wildcard section prefixed with *. For example, [*AD.EXAMPLE.COM] matches AD.EXAMPLE.COM, SUB.AD.EXAMPLE.COM, and any deeper subdomains within that forest, but does not match MYAD.EXAMPLE.COM:

    [*AD.EXAMPLE.COM]
  3. Optional: If you cannot add dedicated realm sections, you can re-enable DNS-based KDC discovery for all realms by adding the dns_realm_discovery parameter to the [global] section.

    Warning

    Red Hat recommends against setting dns_realm_discovery = true. It restores the pre-CVE-2025-59088 behavior and enables any client to trigger DNS SRV record lookups for arbitrary realm names, which can be exploited to probe internal network addresses and exfiltrate data via server-side request forgery.

    [global]
    use_dns = true
    dns_realm_discovery = true
  4. Restart Identity Management (IdM) services:

    # ipactl restart
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat Documentation

Legal Notice

Theme

© 2026 Red Hat
Back to top