[HADOOP-6907] Rpc client doesn't use the per-connection conf to figure out server's Kerberos principal

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.20.203.0, 0.22.0
• Component/s: ipc, security
• Hadoop Flags: Reviewed
• Assignee: Kan Zhang
• Reporter: Kan Zhang
• Created: 09/Aug/10 21:36
• Updated: 02/May/13 02:29
• Resolved: 02/Sep/10 00:37

Description

Currently, RPC client caches the conf that was passed in to its constructor and uses that same conf (or values obtained from it) for every connection it sets up. This is not sufficient for security since each connection needs to figure out server's Kerberos principal on a per-connection basis. It's not reasonable to expect the first conf used by a user to contain all the Kerberos principals that her future connections will ever need. Or worse, if her first conf contains an incorrect principal name, it will prevent the user from connecting to the server even if she later on passes in a correct conf on retry (by calling RPC.getProxy()).

Issue Links

• is depended upon by: HADOOP-6889 Make RPC to have an option to timeout
• relates to: HADOOP-6938 ConnectionId.getRemotePrincipal() should check if security is enabled