You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ritesh H Shukla (Jira)" <ji...@apache.org> on 2021/10/21 20:39:00 UTC
[jira] [Updated] (HDDS-5883) Authenticate with OM as S3G (Client
side)
[ https://issues.apache.org/jira/browse/HDDS-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ritesh H Shukla updated HDDS-5883:
----------------------------------
Summary: Authenticate with OM as S3G (Client side) (was: Authenticate with OM as S3G)
> Authenticate with OM as S3G (Client side)
> -----------------------------------------
>
> Key: HDDS-5883
> URL: https://issues.apache.org/jira/browse/HDDS-5883
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ritesh H Shukla
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org