Hi Fawad
You first need to verify that you can access LDAP on 636 using the LDP tool on the Active Directory server Domain controller that you are attempting to query. To access the tool select Run from the Start menu and type "ldp" complete the server name using the full FQDN type in port 636 and Check the SSL Checkbox
Once you have clicked OK the tool will attempt to connect and if successful will look like this below:-
In order to query the Active Directory you will need to create a user account to use to create the BIND between the SVM Server and the AD, you can also test this using the tool to make sure it authenticates successfully.
In the LDP tool "Connection" menu select "BIND" and complete the tool with the user account you have created to use for the BIND then select the "bind with credentials" option in Windows environment it is best if you use the username@domain format as I have below:
Click on the "OK" button you should see an output similar to below confirming authentication.
So now we know we can connect to the AD using Port 636 SSL and we can successfully BIND the credentials.
The next part we need to find out is where do we collect a list of user accounts from, these may be in a specific OU (Organisation Unit) to find out what the location of this is open your active directory Users and Computers and look for the OU that contains your users accounts:-
In the left-hand pane select the OU which contains your users, right-click on the folder and select "Properties" and select the Attribute Editor, scroll down till you come to "distinguishedName" as below:-
Double Click on the "distinguishedName" attribute and you will get this as below:-
This is the path you will need to enter into the SVM LDAP configuration process.
The next parameter we need to find out is the what is the distinguishing attribute that defines each user, in the Windows LDAP environment we will use the "sAMAccountName" attribute as the UID for SVM, so enter in sAMAccountName in the SVM LDAP Configuration process.
Below is a screenshot of a user account showing the sAMAccountName parameter that this is the Username
Notes:
If you are unable to connect to the AD using the LDAP Tool on Port 636 it may be that you are not using a Windows CA Certification authority in the domain issuing Server Certificates to domain controllers, if you are not using Windows PKI in your environment you will have to either look at using Active Directory Lightweight Directory Services Role and configure this with SSL.
Hi Fawad
You first need to verify that you can access LDAP on 636 using the LDP tool on the Active Directory server Domain controller that you are attempting to query. To access the tool select Run from the Start menu and type "ldp" complete the server name using the full FQDN type in port 636 and Check the SSL Checkbox
Once you have clicked OK the tool will attempt to connect and if successful will look like this below:-
In order to query the Active Directory you will need to create a user account to use to create the BIND between the SVM Server and the AD, you can also test this using the tool to make sure it authenticates successfully.
In the LDP tool "Connection" menu select "BIND" and complete the tool with the user account you have created to use for the BIND then select the "bind with credentials" option in Windows environment it is best if you use the username@domain format as I have below:
Click on the "OK" button you should see an output similar to below confirming authentication.
So now we know we can connect to the AD using Port 636 SSL and we can successfully BIND the credentials.
The next part we need to find out is where do we collect a list of user accounts from, these may be in a specific OU (Organisation Unit) to find out what the location of this is open your active directory Users and Computers and look for the OU that contains your users accounts:-
In the left-hand pane select the OU which contains your users, right-click on the folder and select "Properties" and select the Attribute Editor, scroll down till you come to "distinguishedName" as below:-
Double Click on the "distinguishedName" attribute and you will get this as below:-
This is the path you will need to enter into the SVM LDAP configuration process.
The next parameter we need to find out is the what is the distinguishing attribute that defines each user, in the Windows LDAP environment we will use the "sAMAccountName" attribute as the UID for SVM, so enter in sAMAccountName in the SVM LDAP Configuration process.
Below is a screenshot of a user account showing the sAMAccountName parameter that this is the Username
Notes:
If you are unable to connect to the AD using the LDAP Tool on Port 636 it may be that you are not using a Windows CA Certification authority in the domain issuing Server Certificates to domain controllers, if you are not using Windows PKI in your environment you will have to either look at using Active Directory Lightweight Directory Services Role and configure this with SSL.
