[
https://issues.apache.org/jira/browse/AMBARI-23589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-23589:
---------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Enable Security and ACLs in History Server
> ------------------------------------------
>
> Key: AMBARI-23589
> URL: https://issues.apache.org/jira/browse/AMBARI-23589
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Priority: Critical
> Fix For: 2.7.0
>
> Attachments: AMBARI-23589.patch
>
>
> *Usecase*
> The Spark History Server should have authentication enabled out of the box.
> By default only authenticated Ambari Admin user should have access to SHS UI.
> Ambari Admin should be able to see history of all jobs. For others, the job
> submitter should see history of their own jobs and not anyone else's.
> *TestCase*
> * Verify that SHS enables Authentication OOB
> * Enable Kerberos in the Cluster with Ambari, verify that SHS is still
> enabled for authentication
> * Verify that Admin can see history of all jobs
> * Verify a job submitter only sees history or their own jobs
> Current Spark's Web UI only has SSL encryption, doesn't have mutual
> authentication. From my understanding it is necessary and valuable to add
> this support, both for live UI and history UI.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
