Hi, Anyone kindly review the problem and solution please. On Thu, Mar 12, 2026 at 4:07 PM Vishva N <[email protected]> wrote:
> Hi Everyone, > I am facing an issue where the default authenticator set by the Java > project owner is getting overridden by third party jars used. > https://bugs.java/bugdatabase/JDK-8379776 > > The solution might be asking the jar author to fix the faulty code. but it > is a production critical case and needs to be fixed soon but also don't > want to remove the jar. > > So I came up with an idea to provide access control for > Autheticator modification to the Java Project owner. Java owner can either > throw error or just skip the setDefault call according to the Authenticator > class provided. > > *PR for the Proposed solution*: https://github.com/openjdk/jdk/pull/30193 > > I have attached a program with this mail. Kindly download google big query > jdbc jar and place all the jars inside the zip in the classpath. > > JDBC Jar: > https://storage.googleapis.com/simba-bq-release/jdbc/SimbaJDBCDriverforGoogleBigQuery42_1.6.5.1002.zip > > *Example Scenario:* > 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. >
