[
https://issues.apache.org/jira/browse/GIRAPH-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Avery Ching updated GIRAPH-211:
-------------------------------
Attachment: GIRAPH-211.2.patch
Here is an attached patch with the following changes from GIRAPH-211.patch:
Addressed the -2 worker id by adding the task id to ChannelRotater.
SaslComplete -> SaslCompleteRequest
SASL_TOKEN_MESSAGE -> SASL_TOKEN_MESSAGE_REQUEST
Fixed all minor things (javadoc, functions, added authenticate()).
mvn -Phadoop=facebook compile fixed
Tested with
mvn -Phadoop_non_secure clean verify
- passed
mvn -Phadoop_1.0 clean verify
= passed
mvn -Phadoop_2.0.0 clean verify
- passed
mvn -Phadoop_2.0.1 clean verify
- passed
mvn -Phadoop=facebook compile
- passed
Note that hadoop-2.0.2 wasn't tested (I don't have the artifacts), but should
work.
I know that we should add more testing, but I think this is good to go for now.
It seems to work and it's already very huge. Great work [~ekoontz]! Please
let me know if the changes I made are acceptable, I'm fine with the current
version. We should commit soon.
> Add secure authentication to Netty IPC
> --------------------------------------
>
> Key: GIRAPH-211
> URL: https://issues.apache.org/jira/browse/GIRAPH-211
> Project: Giraph
> Issue Type: Improvement
> Reporter: Eugene Koontz
> Assignee: Eugene Koontz
> Fix For: 0.2.0
>
> Attachments: GIRAPH-211.2.patch, GIRAPH-211.patch, GIRAPH-211.patch,
> GIRAPH-211.patch, GIRAPH-211.patch, GIRAPH-211.patch, GIRAPH-211.patch,
> GIRAPH-211.patch, GIRAPH-211.patch, GIRAPH-211.patch, GIRAPH-211-proposal.txt
>
>
> Gianmarco De Francisci Morales asked on the user list:
> bq. I am getting the exception in the subject when running my giraph program
> bq. on a cluster with Kerberos authentication.
> This leads to the idea of having Kerberos authentication supported within
> GIRAPH. Hopefully it would use our fast GIRAPH-37 IPC, but could also
> interoperate with Hadoop security.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
