[
https://issues.apache.org/jira/browse/HADOOP-10057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoy Antony resolved HADOOP-10057.
-----------------------------------
Resolution: Won't Do
Cleaning up jiras which is not relevant anymore.
> Add ability in Hadoop servers (Namenode, JobTracker, Datanode ) to support
> multiple QOP (Authentication , Privacy) simultaneously
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-10057
> URL: https://issues.apache.org/jira/browse/HADOOP-10057
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 1.2.1
> Reporter: Benoy Antony
> Assignee: Benoy Antony
> Attachments: HADOOP-10057.pdf, hadoop-10057-branch-1.2.patch
>
>
> Add ability in Hadoop servers (Namenode, JobTracker Datanode ) to support
> multiple QOP (Authentication , Privacy) simlutaneously
> Hadoop Servers currently support only one QOP(quality of protection)for the
> whole cluster.
> We want Hadoop servers to support multiple QOP at the same time.
> The logic used to determine the QOP should be pluggable.
> This will enable hadoop servers to communicate with different types of
> clients with different QOP.
> A sample usecase:
> Let each Hadoop server support two QOP .
> 1. Authentication
> 2. Privacy (Privacy includes Authentication) .
> The Hadoop servers and internal clients require to do Authentication only
> without incurring cost of encryption. External clients use Privacy.
> An ip-whitelist logic to determine the QOP is provided and used as the
> default QOP resolution logic.
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
