Skip to main content
Hitachi Vantara Knowledge

Alternative authentication method


As an alternative to the AWS method of authentication, you can use the HCP method. You might choose to do this, for example, if you’re writing an application that uses both the S3 compatible API and the REST API. With the REST API, HCP supports only its own authentication method.

With HCP authentication, the format of the URLs you use in S3 compatible requests differs from the format used with AWS authentication.

This this section of the Help describes the URLs you can use in S3 compatible requests when using HCP authentication. It also explains how to provide credentials or request anonymous access with this authentication method.

For information on AWS authentication and the URLs you can use with that authentication method, see Access and authentication.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

URLs with HCP authentication


The format you use for the URL in an S3 compatible request depends on whether the target of the request and the authentication method being used. In an S3 compatible 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.

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

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

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

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

NoteWebHelp.png

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

For additional information about URLs in S3 compatible requests, see URLs for access to HCP.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

HCP authentication


To provide credentials for HCP authentication, you use the Authorization request header with a value in the format shown below:

Authorization: HCP access-key:secret-key

In this format:

access-key is the Base64-encoded username for your user account.

secret-key is the MD5-hashed password for your user account.

Here’s an example of an Authorization header for HCP authentication:

Authorization: HCP bGdyZWVu:35dc4c4aa08fe0deab7e292e00eb8e97

With HCP authentication, the Authorization header for requesting anonymous access looks like this:

Authorization: HCP all_users:

For more information on user authentication, see Authentication. For information on changing the password for your user account, see, Changing your password.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.