[
https://issues.apache.org/jira/browse/HDFS-13532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549714#comment-16549714
]
CR Hota commented on HDFS-13532:
--------------------------------
[~elgoiri] [~xiaochen] The assumption is that renewals will also go through the
router, router issuing DTs and clients bypassing router and directly talking to
namenodes for renewal/cancellation anyways won't work. As far as renewals are
concerned, from clients perspective it will be one single call, which will
either succeed or fail based on how renewals went through for all downstream
name nodes. These details will be covered in the design document of router
delegation token in
[HDFS-13358|https://issues.apache.org/jira/browse/HDFS-13358].
> RBF: Adding security
> --------------------
>
> Key: HDFS-13532
> URL: https://issues.apache.org/jira/browse/HDFS-13532
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: Íñigo Goiri
> Assignee: Sherwood Zheng
> Priority: Major
> Attachments: RBF _ Security delegation token thoughts.pdf,
> Security_for_Router-based Federation_design_doc.pdf
>
>
> HDFS Router based federation should support security. This includes
> authentication and delegation tokens.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
