On Wed, 11 Mar 2026 14:38:00 GMT, Daniel Fuchs <[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. This fix is to give control to owner of a big java project. This is not the only jar that I am gonna use. With this fix, there is no need to wait for update from the jar. Instead I can just skip the setDefault() call with this fix. Setting default authenticator is necessary in case where central proxy control is needed or Authentication is managed centrally. ------------- PR Comment: https://git.openjdk.org/jdk/pull/30193#issuecomment-4041174660
