[ 
https://issues.apache.org/jira/browse/HDFS-13532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516050#comment-16516050
 ] 

Íñigo Goiri edited comment on HDFS-13532 at 6/18/18 5:36 PM:
-------------------------------------------------------------

Thanks [~zhengxg3] for the document.
Could you add more details on how the Router does the mapping between the DT 
from the Router (e.g., step 8) to the federated token?
>From what we saw in the prototypes, we were getting a DT with a different 
>signature and we had to do guesses to map it to the DT stored.
Can you give more details on how the federated token is created and managed?
For example, how do we propagate the federated tokens across Routers, etc.

In addition, can you add pointers to the particular JIRAs in the design doc?


was (Author: elgoiri):
Thanks [~zhengxg3] for the document.
Could you add more details on how the Router does the mapping between the DT 
from the Router (e.g., step 8) to the federated token?
>From what we saw in the prototypes, we were getting a DT with a different 
>signature and we had to do guesses to map it to the DT stored.
Can you give more details on how the federated token is created and managed?
For example, how do we propagate the federated tokens across Routers, etc.


> 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: 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]

Reply via email to