The following information is not currently addressed by the Big Data Extensions product guides.
When installing Big Data Extensions on vSphere 5.1 or later, you must use vCenter Single Sign-On (SSO) to provide user authentication. When logging in to vSphere 5.1 you pass authentication to the vCenter Single Sign-On server, which you can configure with multiple identity sources such as Active Directory and OpenLDAP. On successful authentication your username and password is exchanged for a security token, which is used to access vSphere components such as Big Data Extensions.
The documentation provided with this Beta release incorrectly states that if you do not enable vCenter SSO, a default administrator credential is used, which you can change at a later time. In fact both the Big Data Extensions plug-in installed within the vSphere Web Client, and the Serengeti Command-Line Interface console will fail to authenticate if SSO is not enabled.
Workaround:
- When deploying Big Data Extensions on vSphere 5.1 or later, ensure that your environment includes vCenter Single Sign-On.
- Provide a vCenter Single Sign-On Look-up Service URL when prompted to do so during the installation procedure. The Serengeti management server and vSphere Web client must use the same SSO service.
The default vCenter Single Sign-On Look-up Service URL is:
https://<SSO_host_FQDN_or_IP>:7444/lookupservice/sdk
where:
SSO_host_FQDN_or_IP is the Fully Qualified Domain Name (FQDN) or IP address of the SSO service.
7444 is the default vCenter Single Sign-On HTTPS port number. If you used a different port number when you installed vCenter Single Sign-On, use that port number.