Hello,
Currently, I am the Sysadmin for three HCP Systems (and possibly more), and some of my end-users have encountered several problems when trying to use the namespaces (buckets) I provided with S3.
First, when some end-users (and I) try to access the buckets on HS3, I receive this error: "SignatureDoesNotMatch." This is puzzling because I created the account to access the buckets and copied the authorization token from the screen to run in Postman. The Authorization Header was: Authorization: AWS Token
.
Second, after the end-user managed to upload some files to HS3 using the AWS SDK (with anonymous access), the names for files and folders are completely random (no idea why), and they are 17 characters long (like "SgPTmk64oGDzpJgod"). They had a previous S3 bucket using Dell ECS, and this problem didn't exist before.
Third, one of my end-users is having problems with the HCP self-signed certificate. They are trying to deploy OpenText on Windows using HS3, and they are encountering this issue: "This CA root certificate is not trusted because it is not in the trusted root certification store." They have suggested creating a new domain, for which they have the root certificate.
I know Hitachi HCP allows creating a new domain using a PKCS12 certificate, but when I tried to create it, I received this error: "Unable to upload certificate for domain hcp4.able.com because the common name for the certificate does not match the domain name."
Fourth, after creating a new domain, how do I create a tenant for it? When I try to create a new tenant, it keeps reverting to the old domain.
Thank you.
------------------------------
Luu Hung Anh
Viettel
------------------------------