[SPARK-12312] Support JDBC Kerberos w/ keytab

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.5.2, 2.4.2
• Fix Version/s: 3.1.0
• Component/s: SQL
• Assignee: Gabor Somogyi
• Reporter: nabacg
• Created: 13/Dec/15 16:56
• Updated: 19/Jun/21 18:09
• Resolved: 10/Feb/21 07:34

Description

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.

Issue Links

• links to: GitHub Pull Request #24421

Sub-Tasks

• Support Postgres Kerberos login in JDBC connector: Resolved
• Support MySQL Kerberos login in JDBC connector: Resolved
• Support MariaDB Kerberos login in JDBC connector: Resolved
• Support DB2 Kerberos login in JDBC connector: Resolved
• Enable DB2IntegrationSuite test and upgrade the DB2 docker inside: Resolved
• Synchronise global JVM security configuration modification: Resolved
• Support MS Sql Kerberos login in JDBC connector: Resolved
• Upgrade to Oracle JDBC Driver 8: Resolved
• Support Oracle Kerberos login in JDBC connector: Resolved
• Pin mariadb-plugin-gssapi-server version to fix MariaDBKrbIntegrationSuite: Resolved
• Create Kerberos authentication provider API in JDBC connector: Resolved
• Add provider disable possibility just like in delegation token provider: Resolved
• Application entry parsing fails because DriverWrapper registered instead of the normal driver: Resolved
• Create high level description about JDBC connection providers for users/developers: Resolved
• Support Hive Kerberos login in JDBC connector: Closed
• Support Azure SQLDB Kerberos login in JDBC connector: Closed
• Support MongoDB Kerberos login in JDBC connector: Closed