[
https://issues.apache.org/jira/browse/HDDS-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ritesh H Shukla updated HDDS-5884:
----------------------------------
Description: 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.
(was: S3G now has kerberos identity added as part of fixes for reading
encrypted buckets.
S3G will no longer proxy the S3 API users' credentials but will authenticate
itself for secure Hadoop RPC communication.
Thus, as far as Hadoop RPC is concerned it will validate S3G as a secure entity
talking with OM.)
> On write requests extract the S3 Auth Info from Request
> -------------------------------------------------------
>
> Key: HDDS-5884
> URL: https://issues.apache.org/jira/browse/HDDS-5884
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ritesh H Shukla
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
