Major Description
Some of the built-in JDBC connection providers are changing the JVM security context to do the authentication which is fine. The problematic part is that executors can be reused by another query. The following situation leads to incorrect behaviour:
- Query1 opens JDBC connection and changes JVM security context in Executor1
- Query2 tries to open JDBC connection but it realizes there is already an entry for that DB type in Executor1
- Query2 is not changing JVM security context and uses Query1 keytab and principal
- Query2 fails with authentication error
