You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Xiao Chen (JIRA)" <ji...@apache.org> on 2016/08/04 07:54:20 UTC
[jira] [Updated] (HADOOP-13443) KMS should check the underlying
keyprovider of KeyProviderExtension before falling back to
DefaultCryptoProvider
[ https://issues.apache.org/jira/browse/HADOOP-13443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiao Chen updated HADOOP-13443:
-------------------------------
Summary: KMS should check the underlying keyprovider of KeyProviderExtension before falling back to DefaultCryptoProvider (was: KMS uses DefaultCryptoProvider when active keyprovider implements KeyProviderCryptoExtension)
> KMS should check the underlying keyprovider of KeyProviderExtension before falling back to DefaultCryptoProvider
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-13443
> URL: https://issues.apache.org/jira/browse/HADOOP-13443
> Project: Hadoop Common
> Issue Type: Bug
> Components: kms
> Affects Versions: 2.6.0
> Reporter: Anthony Young-Garner
> Assignee: Anthony Young-Garner
> Priority: Minor
> Attachments: HADOOP-13443.03.patch, HADOOP-13443.patch, HADOOP-13443.patch
>
>
> By default, the KMS wraps the active key provider in a CachingKeyProvider at runtime. This prevents the KeyProviderCryptoExtension.createKeyProviderCryptoExtension method from ever detecting whether the active key provider implements theKeyProviderCryptoExtension interface. Therefore, the DefaultCryptoExtension is always used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org