You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by GitBox <gi...@apache.org> on 2020/07/17 14:21:56 UTC

[GitHub] [hadoop] steveloughran commented on pull request #2083: HADOOP-17077. S3A delegation token binding to support secondary binding list

steveloughran commented on pull request #2083:
URL: https://github.com/apache/hadoop/pull/2083#issuecomment-660134142


   Related to this, we want different DT bindings to be able to return different auth chains for different usages. e.g Dt 1 provides auth for s3, but DT 2 does dynamoDB
   
   Proposed: we extend the auth chain logic so that
   
   * S3ADelegationTokens stores map of client-role -> auth chain
   
   On demand, token providers are asked for the auth chain for a specific role -they can choose whether to return one or none at all. The default chain is the one built up during init


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



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