[HDFS-14006] Refactor name node to allow different token verification implementations

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.3.0, 3.1.4, 3.2.2
• Assignee: CR Hota
• Reporter: CR Hota
• Created: 18/Oct/18 20:20
• Updated: 26/Mar/20 00:20
• Resolved: 14/Dec/18 19:13

Description

Router currently uses Namenode web resources to read and verify delegation tokens. This model doesn't work when router will be deployed in secured mode. This change will introduce router's own UserProvider resource and dependencies.

In the current deployment one can see this exception.

{"RemoteException":{"exception":"ClassCastException","javaClassName":"java.lang.ClassCastException","message":"org.apache.hadoop.hdfs.server.federation.router.Router cannot be cast to org.apache.hadoop.hdfs.server.namenode.NameNode"}}

In the proposed change, router will maintain its own web resource, that will be similar to current namenode, but modified to get back a router instance instead of namenode.

 

 

Issue Links

• blocks: HDFS-13972 RBF: Support for Delegation Token (WebHDFS)
• relates to: HDFS-13972 RBF: Support for Delegation Token (WebHDFS)