Hello Everyone, Thank you for all the reviews. I actually solved Bigquery issue as Eirik mentioned.
I thought about this proposal because I had issues with couple another jars And I accept Alan bateman and Jaikirans solutions. I’ll try out the agent introduction. On Sun, 15 Mar 2026 at 4:58 PM, Eirik Bjørsnøs <[email protected]> wrote: > Vishva, > > I agree with others here that this issue should be addressed to the > developers of the Simba JDBC driver library. > > In terms of workarounds, have you considered the following: > > 1) Leave out ProxyUid and ProxyPwd properties from the connection URL. It > seems this will prevent Authenticator.setDefault from being called. > 2) Use Google's JDBC driver instead (in preview) which seems to not call > Authenticator.setDefault. > > Cheers, > Eirik. > > On Sun, Mar 15, 2026 at 8:42 AM Alan Bateman <[email protected]> > wrote: > >> >> >> On 15/03/2026 02:08, Jaikiran Pai wrote: >> > >> > : >> > >> > I think introducing a change in the JDK implementation of >> > java.net.Authenticator.setDefault() to run arbitrary application code >> > isn't the way to solve this. Especially not when the change is >> > motivated due to: >> > >> Right, the proposed API in the PR doesn't make sense. We could >> potentially provide better guidance in the Authenticator class >> description to make it clearer that this method for the application to >> set the system-wide Authenticator, it's not something that libraries >> should be using. >> >> As Jai notes, and I also noted in the PR, the example agent in JEP 486 >> may provide some inspiration for a workaround that modifies the use >> sites in the libraries until they are fixed to not set the system wide >> Authenticator. >> >> -Alan. >> >
