You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oozie.apache.org by "Janos Makai (Jira)" <ji...@apache.org> on 2022/12/08 16:20:00 UTC

[jira] [Created] (OOZIE-3687) 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)

Janos Makai created OOZIE-3687:
----------------------------------

             Summary: 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


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)