[
https://issues.apache.org/jira/browse/SPARK-32001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142937#comment-17142937
]
Gabor Somogyi commented on SPARK-32001:
---------------------------------------
Here is the DT provider API:
https://github.com/apache/spark/blob/e00f43cb86a6c76720b45176e9f9a7fba1dc3a35/core/src/main/scala/org/apache/spark/security/HadoopDelegationTokenProvider.scala#L31
META-INF.services:
https://github.com/apache/spark/blob/master/core/src/main/resources/META-INF/services/org.apache.spark.security.HadoopDelegationTokenProvider
> Create Kerberos authentication provider API in JDBC connector
> -------------------------------------------------------------
>
> Key: SPARK-32001
> URL: https://issues.apache.org/jira/browse/SPARK-32001
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Affects Versions: 3.1.0
> Reporter: Gabor Somogyi
> Priority: Major
>
> Adding embedded provider to all the possible databases would generate high
> maintenance cost on Spark side.
> Instead an API can be introduced which would allow to implement further
> providers independently.
> One important requirement what I suggest is: JDBC connection providers must
> be loaded independently just like delegation token providers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
