Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/4106#issuecomment-75861282
The model I had in mind for this patch was to support dedicated
clusters/appliances based on Spark where the Spark cluster itself is fully
trusted and not multi-tenant. @harishreedharan - trying to have secured key
distribution in the standalone mode is a very large undertaking, this is
intentionally designed to avoid that to support a more limited security model.
Trying to support arbitrary user code that you don't trust (within the cluster)
is also not the intention - there aren't arbitrary users, it's a single
embedded application. We've had several requests for some simpler security
mechanism in Standalone mode over the users.
The main concerns I see here are that the KDC can't handle frequent
authentication requests of the same principle from multiple hosts. That might
render this approach untenable. It would be worth testing and understanding the
limitations in that regard.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
