[ https://issues.apache.org/jira/browse/HDFS-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560962#comment-13560962 ]
Daryn Sharp commented on HDFS-4362: ----------------------------------- I just want to make sure I understand the issue correctly. In order for a secure client to talk to an insecure NN, a server that does not issue tokens must return null. The reason is the insecure NN will kick the secure client into SIMPLE auth. However, the secure client will always request tokens anyway so the insecure server must return null. This patch appears to allow protobuf token requests to return null, correct? > GetDelegationTokenResponseProto does not handle null token > ---------------------------------------------------------- > > Key: HDFS-4362 > URL: https://issues.apache.org/jira/browse/HDFS-4362 > Project: Hadoop HDFS > Issue Type: Bug > Affects Versions: 2.0.2-alpha > Reporter: Suresh Srinivas > Assignee: Suresh Srinivas > Priority: Critical > Fix For: 2.0.3-alpha > > Attachments: HDFS-4362.patch > > > While working on HADOOP-9173, I notice that the > GetDelegationTokenResponseProto declares the token field as required. However > return of null token is to be expected both as defined in > FileSystem#getDelegationToken() and also based on HDFS implementation. This > jira intends to make the field as optional. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira