You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Prakash Rajendran (Jira)" <ji...@apache.org> on 2020/09/23 21:16:00 UTC
[jira] [Commented] (SPARK-12312) JDBC connection to Kerberos
secured databases fails on remote executors
[ https://issues.apache.org/jira/browse/SPARK-12312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17201101#comment-17201101 ]
Prakash Rajendran commented on SPARK-12312:
-------------------------------------------
[~johnlon] the above references use keytab and principal to establish kerberos authentication to Oracle. IN my scenario, I donot have control over keytab file, as there will be a sidecar which takes care of detting up the kerb5cache file to my pod. So the executor has to use only the krb5cache file. Is this scenario also works?
> JDBC connection to Kerberos secured databases fails on remote executors
> -----------------------------------------------------------------------
>
> Key: SPARK-12312
> URL: https://issues.apache.org/jira/browse/SPARK-12312
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.5.2, 2.4.2
> Reporter: nabacg
> Assignee: Gabor Somogyi
> Priority: Minor
>
> When loading DataFrames from JDBC datasource with Kerberos authentication, remote executors (yarn-client/cluster etc. modes) fail to establish a connection due to lack of Kerberos ticket or ability to generate it.
> This is a real issue when trying to ingest data from kerberized data sources (SQL Server, Oracle) in enterprise environment where exposing simple authentication access is not an option due to IT policy issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org