You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Andras Piros (JIRA)" <ji...@apache.org> on 2017/07/31 09:25:00 UTC
[jira] [Updated] (OOZIE-3018) Use Hadoop's CredentialProvider for
passwords in SchemaCheckerService
[ https://issues.apache.org/jira/browse/OOZIE-3018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andras Piros updated OOZIE-3018:
--------------------------------
Description: In the [*previous JIRA*|OOZIE-2272] almost all the cases where {{ConfigurationService.get(SOME_PASSWORD_KEY)}} was used, were modified to use Hadoop's {{CredentialProvider}} class. Only one place [*was left*|https://issues.apache.org/jira/browse/OOZIE-2272?focusedCommentId=16104281&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16104281], within {{SchemaCheckerService.init()}}. Addressing this issue. (was: In the [*previous JIRA*|OOZIE-2272] almost all the cases where {{ConfigurationService.get(SOME_PASSWORD_KEY)}} was used, were modified to use Hadoop's {{Credentials}} class. Only one place has been left, within {{SchemaCheckerService.init()}}. Addressing this issue.)
> Use Hadoop's CredentialProvider for passwords in SchemaCheckerService
> ---------------------------------------------------------------------
>
> Key: OOZIE-3018
> URL: https://issues.apache.org/jira/browse/OOZIE-3018
> Project: Oozie
> Issue Type: Bug
> Reporter: Andras Piros
> Assignee: Andras Piros
>
> In the [*previous JIRA*|OOZIE-2272] almost all the cases where {{ConfigurationService.get(SOME_PASSWORD_KEY)}} was used, were modified to use Hadoop's {{CredentialProvider}} class. Only one place [*was left*|https://issues.apache.org/jira/browse/OOZIE-2272?focusedCommentId=16104281&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16104281], within {{SchemaCheckerService.init()}}. Addressing this issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)