5.5

Table Of Contents
Prerequisites
NOTE This procedure assumes that you are logging in with credentials managed by a SAML identity
provider. Users whose credentials are managed by the vCloud Director integrated identity provider must
follow a different login workflow.
n
Verify that you know the login URL. See “Retrieve the Login URL and List of Supported API Versions,”
on page 43
n
Verify that you are logging in as a user whose identity is managed by the SAML identity provider
defined by your organization.
Procedure
1 Acquire the SAML assertion from your identity provider.
The system administrator must use the vSphere SSO Service as the identity provider.
2 Compress the assertion using GZIP.
3 Encode the compressed assertion a MIME Base64 encoding, as specified in RFC 1421.
4 Use the login URL to authenticate to the cloud.
POST a request to this URL. The request must include an Authorization header that specifies SIGN as
the authorization method and has the following attributes:
Table 32. Authorization Header Attributes and Values
Attribute Name Attribute Value
token
The compressed, encoded identity assertion from your
SAML identity provider.
signature Base64 encoded signature of the token XML (the
uncompressed identity assertion from your SAML
identity provider) generated using client's private key.
Required when using holder-of-key subject
confirmation.
signature_alg The algorithm used to generate the signature,
expressed as one of the values listed in
http://docs.oracle.com/javase/7/docs/technotes/guides/se
curity/StandardNames.html#Signature Required if
signature is present.
org
The name of your vCloud Director organization.
Defaults to org="system" if not specified.
See “Example: Create a Login Session Using a SAML Identity Provider,” on page 48.
5 Examine the response.
The response code indicates whether the request succeeded, or how it failed.
n
If the authentication header is missing, the server returns HTTP response code 403.
n
If the credentials supplied in the authentication header are invalid, the server returns HTTP
response code 401.
n
If the request is successful, the server returns HTTP response code 200 (OK) and headers that
include an authorization header of the form:
x-vcloud-authorization: token
This header must be included in each subsequent vCloud API request.
The Session element returned from a successful login contains one or more URLs from which you can
begin browsing.
Chapter 3 Exploring a Cloud
VMware, Inc. 47