[ https://issues.apache.org/jira/browse/SPARK-12312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17178282#comment-17178282 ]
John Lonergan commented on SPARK-12312: --------------------------------------- I think we fixed this in oracle along the lines of this post... https://stackoverflow.com/questions/52662249/javakerberos-authentication-to-sql-server-on-spark-framework See the references to datamountaineer and also the git repo mentioned gives good ideas... https://github.com/nabacg/krb5sqljdb You should be able to get it working for oracle as I have. We followed pretty much the same approach as ... https://github.com/nabacg/krb5sqljdb/blob/master/src/main/scala/net/cabworks/jdbc/Krb5SqlServer.scala .... but we used java and oracle rather than scala and mssql It was fairly straightforward. On Sat, 15 Aug 2020, 3:58 pm Ravi Tummalapenta (Jira), <j...@apache.org> > 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-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org