[
https://issues.apache.org/jira/browse/HADOOP-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542607
]
Raghu Angadi commented on HADOOP-2184:
--------------------------------------
Looking at the RPC client code, the connections are established on demand based
on remote address. Is it enough if we make client create connections based on
<remoteaddress, ticket>, here ticket is somehow obtained (this is part of
another jira) inside getProxy() (i.e. while new RPC proxy is created).
I think this handles many of our cases: a client like DFSClient needs to make
sure it has proper ticket set up only when the RPC client is created. After
that, all the calls on that proxy use the ticket.
So when client invokes an RPC call, current RPC client internally does
'{{getConnection(remoteaddress)}}', this will instead be
'{{getConnection(remoteaddress, ticket)}}'.
Btw, currently version is not checked for each reconnect, strictly it should.
Ticket management requires that each reconnect will have an extra RPC along
with socket connect.
> RPC Support for user permissions and authentication.
> ----------------------------------------------------
>
> Key: HADOOP-2184
> URL: https://issues.apache.org/jira/browse/HADOOP-2184
> Project: Hadoop
> Issue Type: New Feature
> Components: ipc
> Affects Versions: 0.15.0
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Raghu Angadi
> Fix For: 0.16.0
>
>
> Update 11/13/2007: What is proposed for 0.16.0 :
> The client can set a user ticket (as defined in HADOOP-1701) for each
> connection and that ticket is made available to RPC calls at the server. The
> client can replace the ticket at any time. The main advantage is that rest of
> the the client RPCs don't need to be aware of the user tickets.
> What RPC would ideally support in future :
> In the current version of RPC, there is no authentication or data protection.
> We propose to change the RPC framework, so that secure communication is
> possible.
> The new RPC should:
> - Compatible with current RPC
> - Allow a pluggable security implementations (see HADOOP-1701)
> - Support both secure and non-secure modes.
> Here is a rough idea:
> - Store security information (e.g. username, keys) in a ticket
> - Use the ticket to establish a RPC connection
> - Create secure sockets by the (subclass of) SocketFactory corresponding to
> the selected security implementations
> - Send the data and RPC parameters with the secure sockets
> When authentication is supported, the RPC callee should also initialize
> caller information during RPC setup and execute the RPC on the caller's
> behalf.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
