Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-13443

KMS should check the type of underlying keyprovider of KeyProviderExtension before falling back to default

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 2.6.0
    • 2.9.0, 3.0.0-alpha1
    • kms
    • None
    • Reviewed

    Description

      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.

      Attachments

        1. HADOOP-13443.03.patch
          11 kB
          Anthony Young-Garner
        2. HADOOP-13443.patch
          11 kB
          Anthony Young-Garner
        3. HADOOP-13443.patch
          8 kB
          Anthony Young-Garner

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            anthony.young-garner@cloudera.com Anthony Young-Garner
            anthony.young-garner@cloudera.com Anthony Young-Garner
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment