[ 
https://issues.apache.org/jira/browse/AMBARI-18071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keta Patel updated AMBARI-18071:
--------------------------------
    Attachment: AMABRI-18071.patch

> Ambari Files View needs to have ability to load security configurations
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-18071
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18071
>             Project: Ambari
>          Issue Type: Improvement
>          Components: contrib
>    Affects Versions: trunk
>            Reporter: Keta Patel
>            Assignee: Keta Patel
>         Attachments: AMABRI-18071.patch
>
>
> When HDFS is configured with Encryption Zones, Files View to browser files 
> will give "No KeyProvider" error.
> Steps to reproduce this issue:
> 1. Configure an encrypted zone in HDFS (Transparent Data Encryption) 
> following the link 
> https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.3.0/bk_hdfs_admin_tools/content/ch_configuring_hdfs_encryption.html
> 2. Create a Files View instance and provide a user/group the privilege to use 
> the instance.
> 3. Log into the Ambari console as the user with the Files View permission.
> 4. Open the Files View instance.
> 5. Go to the folder which is configured as an encrypted zone.
> 6. Try to open an existing file in this folder.
> 7. This throws an error - java.io.IOException: No KeyProvider is configured, 
> cannot access an encrypted file. 
> 8. When trying through the shell, opening this file works.
> This happens because Files View doesn't have enough configuration set to 
> browse secured zone. Files view doesn't even provide an option to add these 
> configurations.This is why we see errors "No KeyProvider is configured, 
> cannot access an encrypted file", to work around this, you could download 
> client configuration from HDFS service tab, and copy the core-site.xml and 
> hdfs-site.xml files to /etc/ambari-server/conf, then restart ambari-server. 
> After this, the user is able to open the file in the encrypted zone.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to