[ 
https://issues.apache.org/jira/browse/OOZIE-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Janos Makai updated OOZIE-3687:
-------------------------------
    Attachment: OOZIE-3687-002.patch

> Fix Oozie client always using the current system username instead the one 
> specified by the user (e.g.: via kerberos or via explicit basic 
> authentication)
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-3687
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3687
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: 5.2.1
>            Reporter: Janos Makai
>            Assignee: Janos Makai
>            Priority: Major
>         Attachments: OOZIE-3687-001.patch, OOZIE-3687-002.patch
>
>
> Oozie client relies on user.name system property now which is not secure in a 
> kerberised environment. This has to be changed.
> A bug in Oozie CLI causes the Workflow to be launched in the name of the 
> current Unix user even if Kerberos authentication is used with a ticket for a 
> different user.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to