Using Active Directory server as an authentication source (Federation)
Learn how to use you Active Directory server as an authentication source for your vSphere users.
Learn how to use you Active Directory server as an authentication source for your vSphere users.
Last updated 5th December 2022
This guide aims at explaining the details of implementing an Active Directory server as an authentication source on the OVHcloud Hosted Private Cloud.
Discover how to use your Active Directory server as an authentication source for your vSphere users.
vCenter to Active Directory connection is done using LDAPS protocol exposed by the Active Directory server.
Preparing configuration setup, you need to retrieve the following information:
For more information, you can refer to the VMware documentation.
In addition to the previous information, you will need to retrieve the SSL certificate fingerprint (SHA1 Fingerprint) of the Active Directory LDAPS service.
You can retrieve this information with the method of your choice.
Get-ChildItem -Path Cert:\LocalMachine\MY | Select-Object -property FriendlyName, Subject, NotBefore, NotAfter, @{label='Thumbprint';'Expression'={$_.thumbprint -replace '(..(?!$))','$1:'}}
Here, it is the value on the right side of the colon sign:
> Thumbprint : BB:46:CA:6B:FC:92:4E:96:B4:BB:6E:44:7E:8F:AD:4C:C9:32:AB:AB
openssl s_client -connect ad.example.com:636 < /dev/null 2>/dev/null | openssl x509 -fingerprint -noout -in /dev/stdin
Here, it is the value on the right side of the equal sign:
> SHA1 Fingerprint=BB:46:CA:6B:FC:92:4E:96:B4:BB:6E:44:7E:8F:AD:4C:C9:32:AB:AB
Retrieve your Hosted Private Cloud IP address with the method of your choice.
You can use this command on the Active Directory server or any remote Windows machine:
nslookup pcc-198-51-100-121.ovh.com
Here, it is the value at the end of the last line:
> Address: 198.51.100.121
You can alternatively use the following command (from a remote Linux/Unix/Mac machine):
host pcc-198-51-100-121.ovh.com
Here, it is the value at the end of the line:
> pcc-198-51-100-121.ovh.com has address 198.51.100.121
Use the retrieved IP address to allow your Hosted Private Cloud to access the Active Directory LDAPS server (by default on TCP port 636).
This operation can be done on your Active Directory server firewall or your company firewall.
Here is a firewall rule configuration example:
Remote IP address (source) | Local IP address (destination) | Remote port (source) | Local port (destination) | Protocol |
---|---|---|---|---|
198.51.100.121 | All addresses | All ports | 636 | TCP |
Adapt this configuration to your company and apply that rule on your firewall.
From your OVHcloud Control Panel, go to the OVHcloud VMware cluster settings.
Go to the Users
tab and click Add an Active Directory LDAPS
in the Active Directories (LDAPS) section.
Enter the following information :
Then click Submit
.
A window will pop up to show progress, wait until it's fully completed and click Close
.
If a parameter is not valid, the task will be cancelled before reaching 100%. In this case, wait a few minutes for the cancellation to be complete before relaunching the configuration.
You can allow an Active Directory user to access your Hosted Private Cloud from your OVHcloud Control Panel.
Click Import User
.
Select your Active Directory, click Import User
, enter your Active Directory Username in the UPN format (user@example.com) and click Next
.
A task status window appears, wait until it's fully completed and click Close
.
A new user will be displayed in the Control Panel. You can use this user to log in to the vSphere interface.
By default, the user does not have any permission on your Hosted Private Cloud. It will be able to connect to your Hosted Private Cloud but it will not have any access. You can adjust the permissions from the OVHcloud Control Panel.
You can authorise directly a set of users (groups) from your Active Directory server to access your Hosted Private Cloud from the OVHcloud Control Panel.
Click on Import user
.
Select your Active Directory, click Import Group
, type the name of your group
and click Next
.
A task status window appears, wait until it's fully completed and click Close
. Select your Active Directory, click Import Group
, type your group name and click Next
.
The group appears in the users list for your cluster, and members of this group can log in to your cluster’s administration interface.
By default, the group does not have any permission on your Hosted Private Cloud. Its members will be able to connect to your Hosted Private Cloud but they will not have any access. You can adjust the permissions from the OVHcloud Control Panel.
You can use the OVHcloud API to perform the same operations (adding a directory and allowing a group or user to connect to your vCenter interface).
Retrieve your « serviceName » using the following API call:
Then, use the following API call to add your Active Directory server as an authentication source.
You will have to specify information retrieved from the previous steps. Do not check the "noSsl" checkbox.
Make sure the return operation is successful. You can follow its progress in the OVHcloud Control Panel in your Hosted Private Cloud Operations
tab.
If the provided information is invalid, the operation will be cancelled and a message will show the returned error.
You can allow an Active Directory user to access your Hosted Private Cloud through the OVHcloud API.
Retrieve your « activeDirectoryId » using the following API call:
Then, use the following API call to allow an Active Directory user to access your Hosted Private Cloud.
You will have to specify the "pre-Windows 2000" username as it is inside your Active Directory.
Make sure the return operation is successful. You can follow its progress in the OVHcloud Control Panel in your Hosted Private Cloud Operations
tab.
If the provided information is invalid, the operation will be cancelled and a message will show the returned error.
Once allowed, the user and its permissions will be manageable directly from your OVHcloud Control Panel as any other Hosted Private Cloud user.
You can allow directly an Active Directory user set (group) to access your Hosted Private Cloud through the OVHcloud API.
Retrieve your « activeDirectoryId » using the following API call:
Then, use the following API call to allow an Active Directory group to access your Hosted Private Cloud.
You will have to specify the "pre-Windows 2000" group name as it is inside your Active Directory.
Make sure the return operation is successful. You can follow its progress in the OVHcloud Control Panel in your Hosted Private Cloud Operations
tab.
If the provided information is invalid, the operation will be cancelled and a message will show the returned error.
Join our community of users on https://community.ovh.com/en/.
Please feel free to give any suggestions in order to improve this documentation.
Whether your feedback is about images, content, or structure, please share it, so that we can improve it together.
Your support requests will not be processed via this form. To do this, please use the "Create a ticket" form.
Thank you. Your feedback has been received.
Access your community space. Ask questions, search for information, post content, and interact with other OVHcloud Community members.
Discuss with the OVHcloud community