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
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,6 +90,17 @@ This article explains the considerations and steps for enabling LDAP with extend
90
90
91
91

92
92
93
+
8. <aname="ldap-search-scope"></a>Optional - If you have large topologies, and you use the Unix security style with a dual-protocol volume or LDAP with extended groups, you can use the **LDAP Search Scope** option to avoid "access denied" errors on Linux clients for Azure NetApp Files.
94
+
95
+
The **LDAP Search Scope** option is configured through the **[Active Directory Connections](create-active-directory-connections.md#create-an-active-directory-connection)** page.
96
+
97
+
To resolve the users and group from an LDAP server for large topologies, set the values of the **User DN**, **Group DN**, and **Group Membership Filter** options on the Active Directory Connections page as follows:
98
+
99
+
* Specify nested **User DN** and **Group DN** in the format of `OU=subdirectory,OU=directory,DC=domain,DC=com`.
100
+
* Specify **Group Membership Filter** in the format of `(gidNumber=*)`.
101
+
102
+

103
+
93
104
## Next steps
94
105
95
106
*[Create an NFS volume for Azure NetApp Files](azure-netapp-files-create-volumes.md)
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/create-active-directory-connections.md
+9-1Lines changed: 9 additions & 1 deletion
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: 01/07/2022
15
+
ms.date: 01/14/2022
16
16
ms.author: anfdocs
17
17
---
18
18
# Create and manage Active Directory connections for Azure NetApp Files
@@ -224,6 +224,12 @@ This setting is configured in the **Active Directory Connections** under **NetAp
224
224
225
225
You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status.
226
226
227
+
* **LDAP over TLS**
228
+
See [Configure ADDS LDAP over TLS](configure-ldap-over-tls.md) for information about this option.
See [Configure ADDS LDAP with extended groups for NFS volume access](configure-ldap-extended-groups.md#ldap-search-scope) for information about these options.
232
+
227
233
* **Security privilege users** <!-- SMB CA share feature -->
228
234
You can grant security privilege (`SeSecurityPrivilege`) to AD users or groups that require elevated privilege to access the Azure NetApp Files volumes. The specified AD users or groups will be allowed to perform certain actions on Azure NetApp Files SMB shares that require security privilege not assigned by default to domain users.
229
235
@@ -346,3 +352,5 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
346
352
* [Create a dual-protocol volume](create-volumes-dual-protocol.md)
| SMB |`Unix`| Windows to UNIX | UNIX (mode bits or NFSv4.x ACLs) |
58
58
| SMB |`Ntfs`| Windows to UNIX | NTFS ACLs (based on Windows SID accessing share) |
59
-
| NFSv3 |`Unix`| None | UNIX (mode bits or NFSv4.x ACLs) <br><br> Note that NFSv4.x ACLs can be applied using an NFSv4.x administrative client and honored by NFSv3 clients. |
59
+
| NFSv3 |`Unix`| None | UNIX (mode bits or NFSv4.x ACLs) <br><br> NFSv4.x ACLs can be applied using an NFSv4.x administrative client and honored by NFSv3 clients. |
60
60
| NFS |`Ntfs`| UNIX to Windows | NTFS ACLs (based on mapped Windows user SID) |
61
61
62
-
* If you have large topologies, and you use the `Unix` security style with a dual-protocol volume or LDAP with extended groups, Azure NetApp Files might not be able to access all servers in your topologies. If this situation occurs, contact your account team for assistance. <!-- NFSAAS-15123 -->
62
+
* The LDAP with extended groups feature supports the dual protocol of both [NFSv3 and SMB] and [NFSv4.1 and SMB] with the Unix security style. See [Configure ADDS LDAP with extended groups for NFS volume access](configure-ldap-extended-groups.md) for more information.
63
+
64
+
* If you have large topologies, and you use the Unix security style with a dual-protocol volume or LDAP with extended groups, you should use the **LDAP Search Scope** option on the Active Directory Connections page to avoid "access denied" errors on Linux clients for Azure NetApp Files. See [Configure ADDS LDAP with extended groups for NFS volume access](configure-ldap-extended-groups.md#ldap-search-scope) for more information.
65
+
63
66
* You don't need a server root CA certificate for creating a dual-protocol volume. It is required only if LDAP over TLS is enabled.
64
67
65
68
## Create a dual-protocol volume
@@ -92,13 +95,13 @@ To create NFS volumes, see [Create an NFS volume](azure-netapp-files-create-volu
92
95
* **Virtual network**
93
96
Specify the Azure virtual network (VNet) from which you want to access the volume.
94
97
95
-
The Vnet you specify must have a subnet delegated to Azure NetApp Files. The Azure NetApp Files service can be accessed only from the same Vnet or from a Vnet that is in the same region as the volume through Vnet peering. You can also access the volume from your on-premises network through Express Route.
98
+
The VNet you specify must have a subnet delegated to Azure NetApp Files. Azure NetApp Files can be accessed only from the same VNet or from a VNet that is in the same region as the volume through VNet peering. You can also access the volume from your on-premises network through Express Route.
96
99
97
100
* **Subnet**
98
101
Specify the subnet that you want to use for the volume.
99
102
The subnet you specify must be delegated to Azure NetApp Files.
100
103
101
-
If you have not delegated a subnet, you can click **Create new** on the Create a Volume page. Then in the Create Subnet page, specify the subnet information, and select **Microsoft.NetApp/volumes** to delegate the subnet for Azure NetApp Files. In each Vnet, only one subnet can be delegated to Azure NetApp Files.
104
+
If you have not delegated a subnet, you can click **Create new** on the Create a Volume page. Then in the Create Subnet page, specify the subnet information, and select **Microsoft.NetApp/volumes** to delegate the subnet for Azure NetApp Files. In each VNet, only one subnet can be delegated to Azure NetApp Files.
102
105
103
106

104
107
@@ -131,7 +134,7 @@ To create NFS volumes, see [Create an NFS volume](azure-netapp-files-create-volu
131
134
132
135
* If you want to enable SMB3 protocol encryption for the dual-protocol volume, select **Enable SMB3 Protocol Encryption**.
133
136
134
-
This feature enables encryption for only in-flight SMB3 data. It does not encrypt NFSv3 in-flight data. SMB clients not using SMB3 encryption will not be able to access this volume. Data at rest is encrypted regardless of this setting. See [SMB encryption](azure-netapp-files-smb-performance.md#smb-encryption) for additional information.
137
+
This feature enables encryption for only in-flight SMB3 data. It does not encrypt NFSv3 in-flight data. SMB clients not using SMB3 encryption will not be able to access this volume. Data at rest is encrypted regardless of this setting. See [SMB encryption](azure-netapp-files-smb-performance.md#smb-encryption) for more information.
135
138
136
139
* If you selected NFSv4.1 and SMB for the dual-protocol volume versions, indicate whether you want to enable **Kerberos** encryption for the volume.
You might be using the Unix security style with a dual-protocol volume or LDAP with extended groups features in combination with large LDAP topologies. In this case, you might encounter "access denied" errors on Linux clients when interacting with such Azure NetApp Files volumes. You can now use the **LDAP Search Scope** option to specify the LDAP search scope to avoid "access denied" errors.
28
+
25
29
*[Active Directory Domain Services (ADDS) LDAP user-mapping with NFS extended groups](configure-ldap-extended-groups.md) now generally available (GA)
26
30
27
31
The ADDS LDAP user-mapping with NFS extended groups feature is now generally available. You no longer need to register the feature before using it.
28
32
29
-
30
33
## December 2021
31
34
32
35
*[NFS protocol version conversion](convert-nfsv3-nfsv41.md) (Preview)
0 commit comments