You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/configure-ldap-extended-groups.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
12
12
ms.workload: storage
13
13
ms.tgt_pltfrm: na
14
14
ms.topic: how-to
15
-
ms.date: 03/15/2022
15
+
ms.date: 05/27/2022
16
16
ms.author: anfdocs
17
17
---
18
18
# Enable Active Directory Domain Services (ADDS) LDAP authentication for NFS volumes
@@ -24,7 +24,7 @@ Azure NetApp Files supports fetching of extended groups from the LDAP name servi
24
24
When it’s determined that LDAP will be used for operations such as name lookup and fetching extended groups, the following process occurs:
25
25
26
26
1. Azure NetApp Files uses an LDAP client configuration to make a connection attempt to the ADDS/AADDS LDAP server that is specified in the [Azure NetApp Files AD configuration](create-active-directory-connections.md).
27
-
1. If the TCP connection over the defined ADDS/AADDS LDAP service port is successful, then the Azure NetApp Files LDAP client attempts to “bind” (log in) to the ADDS/AADDS LDAP server (domain controller) by using the defined credentials in the LDAP client configuration.
27
+
1. If the TCP connection over the defined ADDS/AADDS LDAP service port is successful, then the Azure NetApp Files LDAP client attempts to “bind” (sign in) to the ADDS/AADDS LDAP server (domain controller) by using the defined credentials in the LDAP client configuration.
28
28
1. If the bind is successful, then the Azure NetApp Files LDAP client uses the RFC 2307bis LDAP schema to make an LDAP search query to the ADDS/AADDS LDAP server (domain controller).
29
29
The following information is passed to the server in the query:
@@ -98,7 +98,7 @@ The following information is passed to the server in the query:
98
98

99
99
100
100
7. Optional - You can enable local NFS client users not present on the Windows LDAP server to access an NFS volume that has LDAP with extended groups enabled. To do so, enable the **Allow local NFS users with LDAP** option as follows:
101
-
1.Click**Active Directory connections**. On an existing Active Directory connection, click the context menu (the three dots `…`), and select **Edit**.
101
+
1.Select**Active Directory connections**. On an existing Active Directory connection, select the context menu (the three dots `…`), and select **Edit**.
102
102
2. On the **Edit Active Directory settings** window that appears, select the **Allow local NFS users with LDAP** option.
103
103
104
104

@@ -119,5 +119,6 @@ The following information is passed to the server in the query:
119
119
*[Create an NFS volume for Azure NetApp Files](azure-netapp-files-create-volumes.md)
120
120
*[Create and manage Active Directory connections](create-active-directory-connections.md)
The NFS client configuration described in this article is part of the setup when you [configure NFSv4.1 Kerberos encryption](configure-kerberos-encryption.md) or [create a dual-protocol volume](create-volumes-dual-protocol.md). A wide variety of Linux distributions are available to use with Azure NetApp Files. This article describes configurations for two of the more commonly used environments: RHEL 8 and Ubuntu 18.04.
20
+
The NFS client configuration described in this article is part of the setup when you [configure NFSv4.1 Kerberos encryption](configure-kerberos-encryption.md) or [create a dual-protocol volume](create-volumes-dual-protocol.md) or [NFSv3/NFSv4.1 with LDAP](configure-ldap-extended-groups.md). A wide variety of Linux distributions are available to use with Azure NetApp Files. This article describes configurations for two of the more commonly used environments: RHEL 8 and Ubuntu 18.04.
0 commit comments