[
https://issues.apache.org/jira/browse/HDDS-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ritesh H Shukla updated HDDS-5885:
----------------------------------
Description:
Based on logic introduced in HDDS-4440 on the read path, if the requests has S3
Auth information then extract and validate. All subsequent identity to be based
on S3 Auth and not RPC thread local auth information.
# Introduce common utility method that can centralize this code and reused for
HDDS-4440 when GRPC is introduced.
was:Based on logic introduced in HDDS-4440 on the write path, if the requests
has S3 Auth information then extract and validate. All subsequent identity to
be based on S3 Auth and not RPC thread local auth information.
> On read requests extract the S3 Auth Info from Request
> ------------------------------------------------------
>
> Key: HDDS-5885
> URL: https://issues.apache.org/jira/browse/HDDS-5885
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ritesh H Shukla
> Priority: Major
>
> Based on logic introduced in HDDS-4440 on the read path, if the requests has
> S3 Auth information then extract and validate. All subsequent identity to be
> based on S3 Auth and not RPC thread local auth information.
> # Introduce common utility method that can centralize this code and reused
> for HDDS-4440 when GRPC is introduced.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
