Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/33#discussion_r10140602
--- Diff: core/src/main/scala/org/apache/spark/SecurityManager.scala ---
@@ -0,0 +1,259 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.spark
+
+import java.net.{Authenticator, PasswordAuthentication}
+import org.apache.hadoop.io.Text
+import org.apache.hadoop.security.Credentials
+import org.apache.hadoop.security.UserGroupInformation
+import org.apache.spark.deploy.SparkHadoopUtil
+
+import scala.collection.mutable.ArrayBuffer
+
+/**
+ * Spark class responsible for security.
+ *
+ * In general this class should be instantiated by the SparkEnv and most
components
+ * should access it from that. There are some cases where the SparkEnv
hasn't been
+ * initialized yet and this class must be instantiated directly.
+ *
+ * Spark currently supports authentication via a shared secret.
+ * Authentication can be configured to be on via the 'spark.authenticate'
configuration
+ * parameter. This parameter controls whether the Spark communication
protocols do
+ * authentication using the shared secret. This authentication is a basic
handshake to
+ * make sure both sides have the same shared secret and are allowed to
communicate.
+ * If the shared secret is not identical they will not be allowed to
communicate.
+ *
+ * The Spark UI can also be secured by using javax servlet filters. A user
may want to
+ * secure the UI if it has data that other users should not be allowed to
see. The javax
+ * servlet filter specified by the user can authenticate the user and then
once the user
+ * is logged in, Spark can compare that user versus the view acls to make
sure they are
+ * authorized to view the UI. The configs 'spark.ui.acls.enable' and
'spark.ui.view.acls'
+ * control the behavior of the acls. Note that the person who started the
application
+ * always has view access to the UI.
+ *
+ * Spark does not currently support encryption after authentication.
+ *
+ * At this point spark has multiple communication protocols that need to
be secured and
+ * different underlying mechisms are used depending on the protocol:
--- End diff --
mechanisms
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
