< Previous | Contents | Next >

URLs with HCP authentication

The format you use for the URL in an HS3 request depends on whether the target of the request and the authentication method being used. In an HS3 request that uses HCP authentication:


If the target of the request is a tenant, you use a URL in this format:


http[s]://tenant-name.hcp-domain name/hs3


Here’s an example in which the tenant name is europe:


https://europe.hcp.example.com/hs3


If the target of the request is a bucket, you use a URL in either of these formats:


http[s]://bucket-name.tenant-name.hcp-domain name/hs3 http[s]://tenant-name.hcp-domain name/hs3/bucket-name

In the first format above, the bucket name is part of the hostname. In

the second format, the bucket name follows the hostname and hs3

interface identifier.


Here’s are examples in which the tenant name is europe and the bucket name is finance:


https://finance.europe.hcp.example.com/hs3 https://europe.hcp.example.com/hs3/finance

If the target of the request is an object, you use a URL in either of these formats:


http[s]://bucket-name.tenant-name.hcp-domain name/hs3/object-name


http[s]://tenant-name.hcp-domain name/hs3/bucket-name/object-name


In the first format above, the bucket name is part of the hostname. In the second format, the bucket name follows the hostname and hs3 interface identifier.



210 Appendix B: Alternative authentication method

HCP authentication



Here’s are examples in which the tenant name is europe, the bucket name is finance, and the object name is Q4_2012.ppt:


https://finance.europe.hcp.example.com/hs3/Q4_2012.ppt https://europe.hcp.example.com/hs3/finance/Q4_2012.ppt

In these formats, the hs3 interface identifier is case sensitive and must be all lowercase.


image

image

Note: Do not use the hs3 interface identifier when using AWS authentication.

image


For additional information about URLs in HS3 requests, see “URLs for access to HCP” on page 44.