[
https://issues.apache.org/jira/browse/HDDS-15861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabian Morgan updated HDDS-15861:
---------------------------------
Description:
Currently, actions such as GetObject, PutObject, etc are being sent in the
RequestContext for authorization on S3 requests even if the STS feature flag is
off. This ticket will correct that so no actions are sent if the STS feature
flag is off.
Separately, the AssumeRoleResponseInfo was setting secretAccessKey in the
toString() method. It doesn't appear to be printed anywhere currently, but it
is being removed now to prevent any future issues.
was:Currently, actions such as GetObject, PutObject, etc are being sent in
the RequestContext for authorization on S3 requests even if the STS feature
flag is off. This ticket will correct that so no actions are sent if the STS
feature flag is off.
> [STS] Actions must not be sent in RequestContext to Authorizer if feature
> flag is off
> -------------------------------------------------------------------------------------
>
> Key: HDDS-15861
> URL: https://issues.apache.org/jira/browse/HDDS-15861
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Fabian Morgan
> Assignee: Fabian Morgan
> Priority: Major
>
> Currently, actions such as GetObject, PutObject, etc are being sent in the
> RequestContext for authorization on S3 requests even if the STS feature flag
> is off. This ticket will correct that so no actions are sent if the STS
> feature flag is off.
> Separately, the AssumeRoleResponseInfo was setting secretAccessKey in the
> toString() method. It doesn't appear to be printed anywhere currently, but it
> is being removed now to prevent any future issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
