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
title: Configure Secure LDAP (LDAPS) in Azure AD Domain Services | Microsoft Docs
3
-
description: Configure Secure LDAP (LDAPS) for an Azure AD Domain Services managed domain
2
+
title: Enable Secure LDAP (LDAPS) in Azure AD Domain Services | Microsoft Docs
3
+
description: Enable Secure LDAP (LDAPS) for an Azure AD Domain Services managed domain
4
4
services: active-directory-ds
5
5
documentationcenter: ''
6
6
author: mahesh-unnikrishnan
@@ -14,17 +14,17 @@ ms.workload: identity
14
14
ms.tgt_pltfrm: na
15
15
ms.devlang: na
16
16
ms.topic: article
17
-
ms.date: 06/27/2018
17
+
ms.date: 08/01/2018
18
18
ms.author: maheshu
19
19
20
20
---
21
-
# Configure secure LDAP (LDAPS) for an Azure AD Domain Services managed domain
21
+
# Enable secure LDAP (LDAPS) for an Azure AD Domain Services managed domain
22
22
23
23
## Before you begin
24
-
Ensure you've completed[Task 2 - export the secure LDAP certificate to a .PFX file](active-directory-ds-admin-guide-configure-secure-ldap-export-pfx.md).
24
+
Complete[Task 2 - export the secure LDAP certificate to a .PFX file](active-directory-ds-admin-guide-configure-secure-ldap-export-pfx.md).
25
25
26
26
27
-
## Task 3 - enable secure LDAP for the managed domain using the Azure portal
27
+
## Task 3: Enable secure LDAP for the managed domain using the Azure portal
28
28
To enable secure LDAP, perform the following configuration steps:
29
29
30
30
1. Navigate to the **[Azure portal](https://portal.azure.com)**.
@@ -44,7 +44,7 @@ To enable secure LDAP, perform the following configuration steps:
44
44
4. By default, secure LDAP access to your managed domain is disabled. Toggle **Secure LDAP** to **Enable**.
5. By default, secure LDAP access to your managed domain over the internet is disabled. Toggle **Allow secure LDAP access over the internet** to **Enable**, if desired.
47
+
5. By default, secure LDAP access to your managed domain over the internet is disabled. Toggle **Allow secure LDAP access over the internet** to **Enable**, if you need to.
48
48
49
49
> [!WARNING]
50
50
> When you enable secure LDAP access over the internet, your domain is susceptible to password brute force attacks over the internet. Therefore, we recommend setting up an NSG to lock down access to required source IP address ranges. See the instructions to [lock down LDAPS access to your managed domain over the internet](#task-5---lock-down-secure-ldap-access-to-your-managed-domain-over-the-internet).
@@ -54,9 +54,9 @@ To enable secure LDAP, perform the following configuration steps:
54
54
55
55
7. Specify the **Password to decrypt .PFX file**. Provide the same password you used when exporting the certificate to the PFX file.
56
56
57
-
8. When you are done, click the **Save** button.
57
+
8. When you're done, click the **Save** button.
58
58
59
-
9. You see a notification that informs you secure LDAP is being configured for the managed domain. Until this operation is complete, you cannot modify other settings for the domain.
59
+
9. You see a notification that informs you secure LDAP is being configured for the managed domain. Until this operation is complete, you can't modify other settings for the domain.
60
60
61
61

62
62
@@ -65,84 +65,5 @@ To enable secure LDAP, perform the following configuration steps:
65
65
>
66
66
>
67
67
68
-
<br>
69
-
70
-
## Task 4 - configure DNS to access the managed domain from the internet
71
-
> [!NOTE]
72
-
> **Optional task** - If you do not plan to access the managed domain using LDAPS over the internet, skip this configuration task.
73
-
>
74
-
>
75
-
76
-
Before you begin this task, ensure you have completed the steps outlined in [Task 3](#task-3---enable-secure-ldap-for-the-managed-domain-using-the-azure-portal-preview).
77
-
78
-
Once you have enabled secure LDAP access over the internet for your managed domain, you need to update DNS so that client computers can find this managed domain. At the end of task 3, an external IP address is displayed on the **Properties** tab in **EXTERNAL IP ADDRESS FOR LDAPS ACCESS**.
79
-
80
-
Configure your external DNS provider so that the DNS name of the managed domain (for example, 'ldaps.contoso100.com') points to this external IP address. For example, create the following DNS entry:
81
-
82
-
ldaps.contoso100.com -> 52.165.38.113
83
-
84
-
That's it - you are now ready to connect to the managed domain using secure LDAP over the internet.
85
-
86
-
> [!WARNING]
87
-
> Remember that client computers must trust the issuer of the LDAPS certificate to be able to connect successfully to the managed domain using LDAPS. If you are using a publicly trusted certification authority, you do not need to do anything since client computers trust these certificate issuers. If you are using a self-signed certificate, install the public part of the self-signed certificate into the trusted certificate store on the client computer.
88
-
>
89
-
>
90
-
91
-
92
-
## Task 5 - lock down secure LDAP access to your managed domain over the internet
93
-
> [!NOTE]
94
-
> If you have not enabled LDAPS access to the managed domain over the internet, skip this configuration task.
95
-
>
96
-
>
97
-
98
-
Before you begin this task, ensure you have completed the steps outlined in [Task 3](#task-3---enable-secure-ldap-for-the-managed-domain-using-the-azure-portal-preview).
99
-
100
-
Exposing your managed domain for LDAPS access over the internet represents a security threat. The managed domain is reachable from the internet at the port used for secure LDAP (that is, port 636). Therefore, you can choose to restrict access to the managed domain to specific known IP addresses. For improved security, create a network security group (NSG) and associate it with the subnet where you have enabled Azure AD Domain Services.
101
-
102
-
The following table illustrates a sample NSG you can configure, to lock down secure LDAP access over the internet. The NSG contains a set of rules that allow inbound secure LDAP access over TCP port 636 only from a specified set of IP addresses. The default 'DenyAll' rule applies to all other inbound traffic from the internet. The NSG rule to allow LDAPS access over the internet from specified IP addresses has a higher priority than the DenyAll NSG rule.
103
-
104
-

## Bind to the managed domain over LDAP using LDP.exe
111
-
You can use the LDP.exe tool which is included in the Remote Server Administration tools package to bind and search over LDAP.
112
-
113
-
First, open LDP and connect to the managed domain. Click **Connection** and click **Connect...** in the menu. Specify the DNS domain name of the managed domain. Specify the port to use for connections. For LDAP connections, use port 389. For LDAPS connections use port 636. Click **OK** button to connect to the managed domain.
114
-
115
-
Next, bind to the managed domain. Click **Connection** and click **Bind...** in the menu. Provide the credentials of a user account belonging to the 'AAD DC Administrators' group.
116
-
117
-
Select **View**, and then select **Tree** in the menu. Leave the Base DN field blank, and click OK. Navigate to the container that you want to search, right-click the container, and select Search.
118
-
119
-
> [!TIP]
120
-
> - Users and groups synchronized from Azure AD are stored in the **AADDC Users** container. The search path for this container looks like ```CN=AADDC\ Users,DC=CONTOSO100,DC=COM```.
121
-
> - Computer accounts for computers joined to the managed domain are stored in the **AADDC Computers** container. The search path for this container looks like ```CN=AADDC\ Computers,DC=CONTOSO100,DC=COM```.
122
-
>
123
-
>
124
-
125
-
More information - [LDAP query basics](https://technet.microsoft.com/library/aa996205.aspx)
126
-
127
-
128
-
## Troubleshooting
129
-
If you have trouble connecting to the managed domain using secure LDAP, perform the following troubleshooting steps:
130
-
* Ensure that the issuer chain of the secure LDAP certificate is trusted on the client. You may choose to add the Root certification authority to the trusted root certificate store on the client to establish the trust.
131
-
* Verify that the LDAP client (for example, ldp.exe) connects to the secure LDAP endpoint using a DNS name, not the IP address.
132
-
* Verify the DNS name the LDAP client connects to resolves to the public IP address for secure LDAP on the managed domain.
133
-
* Verify the secure LDAP certificate for your managed domain has the DNS name in the Subject or the Subject Alternative Names attribute.
134
-
* If you are connecting via secure LDAP over the internet, ensure the NSG settings for the virtual network allow the traffic to port 636 from the internet.
135
-
136
-
If you still have trouble connecting to the managed domain using secure LDAP, [contact the product team](active-directory-ds-contact-us.md) for help. Include the following information to help diagnose the issue better:
137
-
* A screenshot of ldp.exe making the connection and failing.
138
-
* Your Azure AD tenant ID, and the DNS domain name of your managed domain.
139
-
* Exact user name that you are trying to bind as.
140
-
141
-
142
-
## Related content
143
-
*[Azure AD Domain Services - Getting Started guide](active-directory-ds-getting-started.md)
144
-
*[Administer an Azure AD Domain Services managed domain](active-directory-ds-admin-guide-administer-domain.md)
Copy file name to clipboardExpand all lines: articles/active-directory-domain-services/active-directory-ds-admin-guide-configure-secure-ldap-export-pfx.md
+14-11Lines changed: 14 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Configure Secure LDAP (LDAPS) in Azure AD Domain Services | Microsoft Docs
3
-
description: Configure Secure LDAP (LDAPS) for an Azure AD Domain Services managed domain
2
+
title: Create a secure LDAP certificate for an Azure AD Domain Services manage domain | Microsoft Docs
3
+
description: Create a secure LDAP certificate for an Azure AD Domain Services manage domain
4
4
services: active-directory-ds
5
5
documentationcenter: ''
6
6
author: mahesh-unnikrishnan
@@ -14,20 +14,20 @@ ms.workload: identity
14
14
ms.tgt_pltfrm: na
15
15
ms.devlang: na
16
16
ms.topic: article
17
-
ms.date: 06/30/2017
17
+
ms.date: 08/01/2017
18
18
ms.author: maheshu
19
19
20
20
---
21
-
# Configure secure LDAP (LDAPS) for an Azure AD Domain Services managed domain
21
+
# Create a .PFX file with the secure LDAP (LDAPS) certificate for a managed domain
22
22
23
23
## Before you begin
24
-
Ensure you've completed [Task 1 - obtain a certificate for secure LDAP](active-directory-ds-admin-guide-configure-secure-ldap.md).
24
+
Complete [Task 1: obtain a certificate for secure LDAP](active-directory-ds-admin-guide-configure-secure-ldap.md).
25
25
26
26
27
-
## Task 2 - export the secure LDAP certificate to a .PFX file
28
-
Before you start this task, ensure that you have obtained the secure LDAP certificate from a public certification authority or have created a self-signed certificate.
27
+
## Task 2: Export the secure LDAP certificate to a .PFX file
28
+
Before you start this task, get the secure LDAP certificate from a public certification authority or create a self-signed certificate.
29
29
30
-
Perform the following steps, to export the LDAPS certificate to a .PFX file.
30
+
To export the LDAPS certificate to a .PFX file:
31
31
32
32
1. Press the **Start** button and type **R**. In the **Run** dialog, type **mmc** and click **OK**.
33
33
@@ -51,7 +51,7 @@ Perform the following steps, to export the LDAPS certificate to a .PFX file.
51
51
8. In the MMC window, click to expand **Console Root**. You should see the Certificates snap-in loaded. Click **Certificates (Local Computer)** to expand. Click to expand the **Personal** node, followed by the **Certificates** node.
52
52
53
53

54
-
9. You should see the self-signed certificate we created. You can examine the properties of the certificate to ensure the thumbprint matches that reported on the PowerShell windows when you created the certificate.
54
+
9. You should see the self-signed certificate we created. You can examine the properties of the certificate to verify the thumbprint matches that reported on the PowerShell windows when you created the certificate.
55
55
10. Select the self-signed certificate and **right click**. From the right-click menu, select **All Tasks** and select **Export...**.
@@ -66,6 +66,7 @@ Perform the following steps, to export the LDAPS certificate to a .PFX file.
66
66
> You MUST export the private key along with the certificate. If you provide a PFX that does not contain the private key for the certificate, enabling secure LDAP for your managed domain fails.
67
67
>
68
68
>
69
+
69
70
13. On the **Export File Format** page, select **Personal Information Exchange - PKCS #12 (.PFX)** as the file format for the exported certificate.
@@ -74,14 +75,16 @@ Perform the following steps, to export the LDAPS certificate to a .PFX file.
74
75
> Only the .PFX file format is supported. Do not export the certificate to the .CER file format.
75
76
>
76
77
>
77
-
14. On the **Security** page, select the **Password** option and type in a password to protect the .PFX file. Remember this password since it will be needed in the next task. Click **Next** to proceed.
78
+
79
+
14. On the **Security** page, select the **Password** option and type in a password to protect the .PFX file. Remember this password since it will be needed in the next task. Click **Next**.
78
80
79
81

80
82
81
83
> [!NOTE]
82
84
> Make a note of this password. You need it while enabling secure LDAP for this managed domain in [Task 3 - enable secure LDAP for the managed domain](active-directory-ds-admin-guide-configure-secure-ldap-enable-ldaps.md)
83
85
>
84
86
>
87
+
85
88
15. On the **File to Export** page, specify the file name and location where you'd like to export the certificate.
86
89
87
90

@@ -91,4 +94,4 @@ Perform the following steps, to export the LDAPS certificate to a .PFX file.
91
94
92
95
93
96
## Next step
94
-
[Task 3 - enable secure LDAP for the managed domain](active-directory-ds-admin-guide-configure-secure-ldap-enable-ldaps.md)
97
+
[Task 3: enable secure LDAP for the managed domain](active-directory-ds-admin-guide-configure-secure-ldap-enable-ldaps.md)
0 commit comments