On Wed, 11 Mar 2026 18:15:36 GMT, Vishva N <[email protected]> wrote: > The fix proposed here doesn't look right. > > > While using Google Big Query JDBC Jar, If proxy username property is > > present in the connection url, the default authenticator is reset by a code > > piece in the jar without any checks for existing authenticator. > > This seems wrong and is the root of the issue, so I would suggest fixing the > behaviour of that jar instead.
Also, Giving control to the JVM owner should be the right way I think. This is significant in emergency production releases. ------------- PR Comment: https://git.openjdk.org/jdk/pull/30193#issuecomment-4041186735
