You can use your O365 credentials to login to Vcloud Director. This article describribes how you can configure O365 SAML authentication.
You need to have an active Copaco VMware Cloud subscription
You need to have an O365 environment
Login to the Vcloud director portal
Go to “Administration
click on "SAML" under the Identity Providers in the menu on the left
On the SAML Configuration page click on the URL next to "Metadata", this will download a file we need to upload to Azure AD
Now that we have the metadata file we can switch to Azure AD
. Login to https://portal.azure.com and login with your Admin credentials
Go to “Azure Active Directory”
In the list of items along the left of the page click on "Enterprise Applications"
Click on "New Application"
In the little window that opens, name your application (e.g. Copaco Vmware Cloud) and ensure "Integrate any other application you don't find in the gallery" is selected. Click "Create" once done
On the page that loads click on "Assign Users and Groups" and add the user or group you want to have access. Once done click on "Overview" on the left
Click on " single sign on" → SAML
At the top of the page click on "Upload metadata file" and select the file you downloaded from vCloud Director
select the file you downloaded from vCloud Director
In the window that appears enter your vCloud Tenant URL into the "Sign On URL" field. click "Save" at the top once done
Under the "SAML Signing Certificate" section, click the download button next to "Federation Metadata XML". We need to upload this to vCloud Director
Now that the Azure AD side is configured we need to go back to vCloud Director and finish the SAML configuration
Go back to vCloud and to the section where you downloaded the metadata file. Click on "Edit" on that page
Click on the "Identity Provider" tab at the top of the page, then click the slider to enable the SAML Identity Provider and upload the XML file you downloaded from Azure. Click "SAVE" to apply the settings
Now test logging in via SSO in an Incognito window, you should be directed to the Azure Login Portal instead of vCloud Director