hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2184) RPC Support for user permissions and authentication.
Date Wed, 14 Nov 2007 20:32:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542584
] 

Raghu Angadi commented on HADOOP-2184:
--------------------------------------

bq. In fact, this issue might ease HADOOP-1298 a bit, as it would not require a change to
the API: H-1298 currently adds a Ticket parameter to almost all methods of ClientProtocol.
This would not be necessary anymore if this issue provides the ticket directly through the
RPC layer.

That is true, but these changes to API are already done in HADOOP-1298. I didn't want to increase
the dependencies for 1298. I was planning to make the necessary changes if 1298 is already
committed. Lets see if by Friday if all the necessary code is ready.. we can reduce the changes
for 1298 after that.

> This might happen within the Eclipse plug-in.
Lets see how the current proposal goes in near term (2-3 weeks) and if required we could add
some more facilities (either in RPC or in another place) so that it is easy to separate identities.


> 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.


Mime
View raw message