tgravescs commented on a change in pull request #23348: [SPARK-25857][core] Add 
developer documentation regarding delegation tokens.
URL: https://github.com/apache/spark/pull/23348#discussion_r245684798
 
 

 ##########
 File path: core/src/main/scala/org/apache/spark/deploy/security/README.md
 ##########
 @@ -0,0 +1,238 @@
+# Delegation Token Handling In Spark
+
+This document aims to explain and demystify delegation tokens as they are used 
by Spark, since
+this topic is generally a huge source of confusion.
+
+
+## What are delegation tokens?
+
+Delegation tokens (DTs from now on) are authentication tokens used by some 
services to replace
+Kerberos service tokens. Many services in the Hadoop ecosystem have support 
for DTs, since they
+have two very desirable advantages over Kerberos tokens:
+
+* No need to distribute Kerberos credentials
+
+In a distributed application, distributing Kerberos credentials is tricky. Not 
all users have
+keytabs, and when they do, it's generally frowned upon to distribute them over 
the network as
+part of application data.
 
 Review comment:
   We seem to be mixing the section of what is a delegation token with what the 
benefits are, the definition of what also seems to be in  the next section with 
the lifecycle, perhaps we need to reorganize this a bit to have more of a 
section on what is DT, within there you can go into the benefits or why
   
   Might mention here that with tokens you can't acquire more tokens vs with 
tgts or keytab you can get more tokens so its more secure to use tokens.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to