[
https://issues.apache.org/jira/browse/HDDS-9265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Tutrinov updated HDDS-9265:
--------------------------------------
Description: For now the *awsAccessKey* for a user is a kerberos principal,
but a number of test tools (like k6, cosbench) validate the access key and
don't expect the special characters like '@' or '/' inside. Hence the access
key ID should be presented as same as the AWS's one (e.g. encode the principal
as base32 string) (was: For now the *awsAccessKey* for a user is a kerberos
principal, but a number of test tools (like k6) validate the access key and
don't expect the special characters like '@' or '/' inside. Hence the access
key ID should be presented as same as the AWS's one (e.g. encode the principal
as base32 string))
> S3G: AWS access key ID should meet the same pattern as for the original AWS
> API
> -------------------------------------------------------------------------------
>
> Key: HDDS-9265
> URL: https://issues.apache.org/jira/browse/HDDS-9265
> Project: Apache Ozone
> Issue Type: Task
> Affects Versions: 1.4.0
> Reporter: Vyacheslav Tutrinov
> Priority: Minor
>
> For now the *awsAccessKey* for a user is a kerberos principal, but a number
> of test tools (like k6, cosbench) validate the access key and don't expect
> the special characters like '@' or '/' inside. Hence the access key ID should
> be presented as same as the AWS's one (e.g. encode the principal as base32
> string)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
