Skip to content

Commit e5d90a1

Browse files
Merge pull request #218501 from markwahl-msft/mwahl-ecma-ldap1
provisioning to on-prem LDAP: address formatting issues
2 parents ccb865a + a4c53ee commit e5d90a1

File tree

1 file changed

+14
-12
lines changed

1 file changed

+14
-12
lines changed

includes/active-directory-app-provisioning-ldap.md

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -79,26 +79,26 @@ C:\Windows\ADAM> ADAMInstall.exe /answer:answer.txt
7979
### Create containers and a service account for AD LDS
8080
The use the PowerShell script from [Appendix C](#appendix-c---populate-ad-lds-powershell-script). The script performs the following actions:
8181
- Creates a container for the service account that will be used with the LDAP connector
82-
- Creates a container for the cloud users. This container is where users will be provisioned to.
82+
- Creates a container for the cloud users, where users will be provisioned to
8383
- Creates the serve account in AD LDS
8484
- Enables the service account
8585
- Adds the service account to the AD LDS Administrators role
8686

8787
On the Windows Server virtual machine, you are using to test the LDAP connector run the script using Windows PowerShell with administrative privileges.
8888

89-
### Grant the NETWORK SERVICE read permissions to the SSL cert
89+
### Grant the NETWORK SERVICE read permissions to the SSL certificate
9090
In order to enable SSL to work, you need to grant the NETWORK SERVICE read permissions to our newly created certificate. To grant permissions, use the following steps.
9191

9292
1. Navigate to **C:\Program Data\Microsoft\Crypto\Keys**.
9393
2. Right-click on the system file located here. It will be a guid. This container is storing our certificate.
94-
a. Select properties.
95-
b. At the top, select the **Security** tab.
96-
c. Select **Edit**.
97-
d. Click **Add**.
98-
e. In the box, enter **Network Service** and select **Check Names**.
99-
f. Select **NETWORK SERVICE** from the list and click **OK**.
100-
g. Click **Ok**.
101-
h. Ensure the Network service account has read and read & execute permissions and click **Apply** and **OK**.
94+
- Select properties.
95+
- At the top, select the **Security** tab.
96+
- Select **Edit**.
97+
- Click **Add**.
98+
- In the box, enter **Network Service** and select **Check Names**.
99+
- Select **NETWORK SERVICE** from the list and click **OK**.
100+
- Click **Ok**.
101+
- Ensure the Network service account has read and read & execute permissions and click **Apply** and **OK**.
102102

103103
### Verify SSL connectivity with AD LDS
104104
Now that we have configured the certificate and granted the network service account permissions, test the connectivity to verify that it is working.
@@ -110,9 +110,9 @@ Now that we have configured the certificate and granted the network service acco
110110
- Server: APP3
111111
- Port: 636
112112
- Place a check in the SSL box
113-
[![Ldp connection configuration](media/active-directory-app-provisioning-ldap/ldp-2.png)</br>
113+
[![Ldp connection configuration](media/active-directory-app-provisioning-ldap/ldp-2.png)](media/active-directory-app-provisioning-ldap/ldp-2.png#lightbox)</br>
114114
5. You should see a response similar to the screenshot below.
115-
![Ldp connection configuration success](media/active-directory-app-provisioning-ldap/ldp-3.png)](media/active-directory-app-provisioning-ldap/ldp-3.png#lightbox)</br>
115+
[![Ldp connection configuration success](media/active-directory-app-provisioning-ldap/ldp-3.png)](media/active-directory-app-provisioning-ldap/ldp-3.png#lightbox)</br>
116116
6. At the top, under **Connection** select **Bind**.
117117
7. Leave the defaults and click **OK**.
118118
[![Ldp bind](media/active-directory-app-provisioning-ldap/ldp-4.png)](media/active-directory-app-provisioning-ldap/ldp-4.png#lightbox)</br>
@@ -316,6 +316,8 @@ If the error message is **Failed to create User**, then check the attributes tha
316316

317317
For more information, change to the **Troubleshooting & Recommendations** tab.
318318

319+
For other errors, see [troubleshooting on-premises application provisioning](../articles/active-directory/app-provisioning/on-premises-ecma-troubleshoot.md).
320+
319321
## Check that users were successfully provisioned
320322
After waiting, check your directory to ensure users are being provisioned. The following instructions illustrate how to check AD LDS.
321323

0 commit comments

Comments
 (0)