From d989fbd796f84738f0059bdf0fe69fe3b29e1be7 Mon Sep 17 00:00:00 2001 From: adamaze Date: Tue, 14 Nov 2023 21:23:12 -0600 Subject: [PATCH] fix broken ldap wiki URLs --- src/docs/ad/ad-service-discovery.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/docs/ad/ad-service-discovery.rst b/src/docs/ad/ad-service-discovery.rst index f383fc9..123f2b5 100644 --- a/src/docs/ad/ad-service-discovery.rst +++ b/src/docs/ad/ad-service-discovery.rst @@ -23,7 +23,7 @@ When using the AD provider, by default SSSD clients utilize auto-discovery of Ac LDAP/CLDAP ping =============== -`CLDAP (Connection-Less LDAP) ping `_ is a way for clients to check the liveliness of a domain controller. Instead of LDAP where the communication is done over TCP protocol, the CLDAP ping is sent over UDP to be faster. It is often necessary for SSSD to try to find available domain controllers within a domain, or within an AD site. SSSD sends a LDAP ping during the service discovery phase by sending a `rootDSE `_ search of the **netlogon** attribute. If available, the AD domain controller will return site, forest, and domain information in the **netlogon** response. +`CLDAP (Connection-Less LDAP) ping `_ is a way for clients to check the liveliness of a domain controller. Instead of LDAP where the communication is done over TCP protocol, the CLDAP ping is sent over UDP to be faster. It is often necessary for SSSD to try to find available domain controllers within a domain, or within an AD site. SSSD sends a LDAP ping during the service discovery phase by sending a `rootDSE `_ search of the **netlogon** attribute. If available, the AD domain controller will return site, forest, and domain information in the **netlogon** response. .. seealso::