Accounts

In the context of this book, the term HSwift account is synonymous with the terms HCP tenant and Keystone HCP tenant. Each term pertains to its individual interface. In order to use an HSwift account with the HSwift API, the HSwift account must be associated with an HCP tenant with the same name as the HSwift account.

Once an HSwift account is created, you need to authenticate when you store and manage containers and objects. If you want to use Keystone authentication, you need to include a Authentication header and a Keystone authentication token with your command. This token verifies that you are authorized to work with containers and objects on the HSwift account. For more information about integrating your HSwift with HCP and Keystone, see Keystone integration.

If you choose to authenticate with an alternative authentication method, you can use local authentication to access your HSwift account. This method requires that you generate a temporary authentication token with your HCP user account (not your HSwift account) credentials. For more information on alternative authentication methods, see Alternate authentication methods.

Note: Your HSwift account and HCP user account are not the same. The HSwift account is the name of your HCP tenant in the context of the HSwift API. Your HCP user account is a set of credentials that gives an HCP user access to other interfaces. For more information on HCP user accounts, see Administering HCP.

Trademarks and Legal Disclaimer

© 2016 Hitachi Data Systems Corporation. All rights reserved.