You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Alejandro Abdelnur (Updated) (JIRA)" <ji...@apache.org> on 2011/11/24 00:34:40 UTC
[jira] [Updated] (OOZIE-77) Oozie should support Kerberos
authentication on its HTTP REST API
[ https://issues.apache.org/jira/browse/OOZIE-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur updated OOZIE-77:
------------------------------------
Description:
Original Issue: GH-35
The correct way of doing this would be using an SPNEGO filter on the server side.
Ideally authentication should be plugglable, allowing support for cookie based auth, certs, etc.
was:
The correct way of doing this would be using an SPNEGO filter on the server side.
Ideally authentication should be plugglable, allowing support for cookie based auth, certs, etc.
Summary: Oozie should support Kerberos authentication on its HTTP REST API (was: GH-35: Oozie should support Kerberos authentication on its HTTP REST API)
> Oozie should support Kerberos authentication on its HTTP REST API
> -----------------------------------------------------------------
>
> Key: OOZIE-77
> URL: https://issues.apache.org/jira/browse/OOZIE-77
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
> Assignee: Roman Shaposhnik
>
> Original Issue: GH-35
> The correct way of doing this would be using an SPNEGO filter on the server side.
> Ideally authentication should be plugglable, allowing support for cookie based auth, certs, etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira