[HADOOP-17536] ABFS: Suport for customer provided encryption key

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.3.1
• Component/s: fs/azure
• Labels: pull-request-available
• Target Version/s: 3.4.0
• Assignee: Bilahari T H
• Reporter: Bilahari T H
• Created: 19/Feb/21 04:34
• Updated: 27/Apr/21 12:17
• Resolved: 27/Apr/21 12:17

Description

The data for a particular customer needs to be encrypted on account level. At server side the APIs will start accepting the encryption key as part of request headers. The data will be encrypted/decrypted with the given key at the server. 

Since the ABFS FileSystem APIs are implementations for Hadoop FileSystem APIs there is no direct way with which customer can pass the key to ABFS driver. In this case driver should have the following capabilities so that it can accept and pass the encryption key as one of the request headers. 

1. There should be a way to configure the encryption key for different accounts.
2. If there is a key specified for a particular account, the same needs to be sent along with the request headers. 

Config changes 

They key for an account can be specified in the core-site as follows. 

fs.azure.account.client-provided-encryption-key.

{account name}

.dfs.core.windows.net 

Issue Links

• links to: GitHub Pull Request #2707