impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sailesh Mukil (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IMPALA-5041) Allow AuthManager::Init() to be called more than once
Date Sat, 18 Mar 2017 00:25:41 GMT

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

Sailesh Mukil updated IMPALA-5041:
----------------------------------
    Summary: Allow AuthManager::Init() to be called more than once  (was: AuthManager::Init()
is not idempotent)

> Allow AuthManager::Init() to be called more than once
> -----------------------------------------------------
>
>                 Key: IMPALA-5041
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5041
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Security
>    Affects Versions: Impala 2.9.0
>            Reporter: Sailesh Mukil
>            Assignee: Sailesh Mukil
>              Labels: kerberos, security
>
> AuthManager::Init() is not idempotent. This generally isn't a problem since we call it
only once per daemon, however, if we want to test with different security configurations as
a part of the BE tests, this causes unnecessary failures.
> This is because we use a global variable to track the completion of the kerberos environment
setup which shouldn't be the case since we would want to re-setup the environment if we call
AuthManager::Init() with a different configuration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message