From 44da5ab2dea6dcf1e13d624784741141883870bb Mon Sep 17 00:00:00 2001 From: Thomas Graves Date: Thu, 24 Apr 2014 18:38:10 -0700 Subject: Spark 1489 Fix the HistoryServer view acls This allows the view acls set by the user to be enforced by the history server. It also fixes filters being applied properly. Author: Thomas Graves Closes #509 from tgravescs/SPARK-1489 and squashes the following commits: 869c186 [Thomas Graves] change to either acls enabled or disabled 0d8333c [Thomas Graves] Add history ui policy to allow acls to either use application set, history server force acls on, or off 65148b5 [Thomas Graves] SPARK-1489 Fix the HistoryServer view acls --- docs/monitoring.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'docs/monitoring.md') diff --git a/docs/monitoring.md b/docs/monitoring.md index 347a9b1f1a..6f35fc37c4 100644 --- a/docs/monitoring.md +++ b/docs/monitoring.md @@ -115,6 +115,19 @@ represents an application's event logs. This creates a web interface at Location of the kerberos keytab file for the History Server. + + spark.history.ui.acls.enable + false + + Specifies whether acls should be checked to authorize users viewing the applications. + If enabled, access control checks are made regardless of what the individual application had + set for spark.ui.acls.enable when the application was run. The application owner + will always have authorization to view their own application and any users specified via + spark.ui.view.acls when the application was run will also have authorization + to view that application. + If disabled, no access control checks are made. + + Note that in all of these UIs, the tables are sortable by clicking their headers, -- cgit v1.2.3