hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bharat Viswanadham (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-1043) Enable token based authentication for S3 api
Date Mon, 25 Feb 2019 20:22:00 GMT

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

Bharat Viswanadham commented on HDDS-1043:

I feel, we have already AuthorizationHeaderV4.java, we can use that to parse AuthorizationHeader,
and for remaining to compute stringtoSign and other we can add those to the existing class.


As if it is not according to AWS authHeader V4 spec we throw out errors. But we have not parsed
credential value, to check it has all the correct entries. We can incorporate [~anu] comments

> Enable token based authentication for S3 api
> --------------------------------------------
>                 Key: HDDS-1043
>                 URL: https://issues.apache.org/jira/browse/HDDS-1043
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Ajay Kumar
>            Assignee: Ajay Kumar
>            Priority: Major
>              Labels: security
>             Fix For: 0.4.0
>         Attachments: HDDS-1043.00.patch, HDDS-1043.01.patch, HDDS-1043.02.patch, HDDS-1043.03.patch
> Ozone has a  S3 api and mechanism to create S3 like secrets for user. This jira proposes
hadoop compatible token based authentication for S3 api which utilizes S3 secret stored in

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