< Previous | Contents | Next >

Notes:


All the examples of HS3 requests in this book assume AWS authentication.


image

To use a recognized Active Directory user account for access to HCP through the HS3 API, applications must use the SPNEGO protocol to negotiate the AD user authentication themselves. For more information on SPNEGO, see http://tools.ietf.org/html/rfc4559.

Chapter 3: Access and authentication 43

URLs for access to HCP


URLs for access to HCP

With the HS3 API, the service point (also called the endpoint) is a tenant. Every request you make to access HCP using HS3 is made within the context of a tenant.


The URL in a request identifies the target of the request. This target can be the tenant, a bucket within the tenant, or an object within a bucket within the tenant. The format you use for a URL depends on the target of the request and the authentication method being used.


An HCP system can have multiple tenants and, therefore, multiple service points. Each tenant has its own default configuration settings for new buckets. Buckets, therefore, can have different characteristics depending on the tenants within which you create them.


Each tenant also has its own set of user accounts. For access that requires you to be an authenticated user, you need to use a user account that’s defined for the applicable tenant.