hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anu Engineer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-938) Add Client APIs for using S3 Auth interface
Date Wed, 02 Jan 2019 21:37:00 GMT

    [ https://issues.apache.org/jira/browse/HDDS-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732449#comment-16732449

Anu Engineer commented on HDDS-938:

{quote}Instead of passing username, can we get the Kerberos userID at OM end, instead of checking
whether the passed user is same as the caller identity which simplifies the logic?
Should we go ahead with this patch for now and when the HDDS-4 is complete,we can make that
compulsory. Hence I was suggesting the future JIRA. We probably will have to make sure that
S3gateway and ozone can run properly in the insecure mode too, that is if a user does not
enable security we will still be able to work properly.

> Add Client APIs for using S3 Auth interface
> -------------------------------------------
>                 Key: HDDS-938
>                 URL: https://issues.apache.org/jira/browse/HDDS-938
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>          Components: S3
>            Reporter: Anu Engineer
>            Assignee: Dinesh Chitlangia
>            Priority: Major
>         Attachments: HDDS-938-HDDS-4.00.patch, HDDS-938-HDDS-4.01.patch
> Add Client and Server APIs to access the S3 Auth interface supported by Ozone Manager.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message