[HADOOP-10141] Create an API to separate encryption key storage from applications

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.6.0
• Component/s: security
• Assignee: Owen O'Malley
• Reporter: Owen O'Malley
• Created: 03/Dec/13 00:11
• Updated: 01/Dec/14 03:10
• Resolved: 20/Dec/13 00:27

Description

As with the filesystem API, we need to provide a generic mechanism to support multiple key storage mechanisms that are potentially from third parties.

An additional requirement for long term data lakes is to keep multiple versions of each key so that keys can be rolled periodically without requiring the entire data set to be re-written. Rolling keys provides containment in the event of keys being leaked.

Toward that end, I propose an API that is configured using a list of URLs of KeyProviders. The implementation will look for implementations using the ServiceLoader interface and thus support third party libraries.

Two providers will be included in this patch. One using the credentials cache in MapReduce jobs and the other using Java KeyStores from either HDFS or local file system.

Issue Links

• is duplicated by: HADOOP-10528 A TokenKeyProvider for a Centralized Key Manager Server (BEE: bee-key-manager)
• is duplicated by: HADOOP-9825 Key Provider for TokenAuth
• is related to: HADOOP-9534 Credential Management Framework (CMF)
• is related to: HADOOP-10607 Create an API to Separate Credentials/Password Storage from Applications
• is related to: HDFS-6134 Transparent data at rest encryption