[
https://issues.apache.org/jira/browse/HADOOP-13443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407413#comment-15407413
]
Hudson commented on HADOOP-13443:
---------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #10211 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/10211/])
HADOOP-13443. KMS should check the type of underlying keyprovider of (xiao: rev
05db64913d8c620cf481f74219bac9b72cb142af)
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/crypto/key/KeyProviderCryptoExtension.java
*
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/crypto/key/TestKeyProviderCryptoExtension.java
> KMS should check the type of underlying keyprovider of KeyProviderExtension
> before falling back to default
> ----------------------------------------------------------------------------------------------------------
>
> 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
> Fix For: 2.9.0, 3.0.0-alpha2
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
