To ensure that an OpenStack Swift service that uses Keystone V3 can authenticate with ECS, you must ensure that the Swift and ECS configurations are consistent.
The following prerequisites apply:
Ensure that you have credentials for the Swift service administrator account. These credentials are required so that ECS can authenticate with the Keystone service.
Ensure that you have the identity of the Keystone project to which Swift users access ECS belong.
Ensure that you have the credentials for an ECS System Administrator account.
Ensure that the ECS endpoint has been added to the Swift service catalog and is correctly formatted.
You must ensure that the endpoints are located in the "default" Keystone domain.
Log into the ECS Portal as a System Administrator.
Create an authentication provider that specifies the Keystone V3 service endpoint and the credentials of an administrator account that can be used to validate tokens.
Create an ECS namespace that has the same ID as the Keystone project/account that the users want to authenticate belong to.
Obtain the Keystone project ID.
In the ECS Portal, select
Manage > Namespace > New Namespace
Enter the name of the namespace.
This should be the name of the Swift project.
Enter the namespace administrator account as the
User Admin.
This should be the name of a management user that has previously been created.
Configure any other namespace settings that you require.
For more information about Namespace settings and about creating users in ECS, see the
ECS Administration Guide which is available from the
https://www.dell.com/support/.
Once the namespace is created, users belonging to the corresponding Keystone project, and who have a token that is scoped to that project, can authenticate with ECS (through ECS communicating with the Keystone authentication provider) and use the Swift API to access the ECS object store.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\