SNOW-1566207: ExternalBrowser authentication hangs if user closes browser prior to authentication

[hchenatsafe]

1. What version of JDBC driver are you using?
3.16.1

2. What operating system and processor architecture are you using?
Ubuntu 22.04, Intel x64

3. What version of Java are you using?
OpenJDK 17.0.11+9
OpenJ9 0.44.0

4. What did you do?
Our application allows users to pass the connection property authenticator=externalbrowser when we connect to the driver via connect().

This works fine if the user logs in successfully, but if the user decides to close the browser without logging in, the request simply hangs and does not return any exceptions or timeouts.

5. What did you expect to see?

A similar browser-based authentication method exists for the Microsoft JDBC Driver for SQL Server. When the user closes the browser without logging in, the driver returns an exception after a short amount of time:

Worker 3430810 > com.microsoft.sqlserver.jdbc.SQLServerException: Failed to authenticate the user test@test.com in Active Directory (Authentication=ActiveDirectoryInteractive). No Authorization code was returned from the server
Worker 3430810 > at com.microsoft.sqlserver.jdbc.SQLServerMSAL4JUtils.getCorrectedException(SQLServerMSAL4JUtils.java:449)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.SQLServerMSAL4JUtils.getSqlFedAuthTokenInteractive(SQLServerMSAL4JUtils.java:403)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.SQLServerConnection.getFedAuthToken(SQLServerConnection.java:6157)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.SQLServerConnection.onFedAuthInfo(SQLServerConnection.java:5989)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.SQLServerConnection.processFedAuthInfo(SQLServerConnection.java:5823)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onFedAuthInfo(tdsparser.java:322)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:130)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:42)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:6881)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:5428)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$300(SQLServerConnection.java:94)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:5360)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7748)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:4410)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:3847)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:3372)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:3197)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1971)
Worker 3430810 > at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:1263)

[sfc-gh-wfateem]

Hi @hchenatsafe,
Thanks for reaching out. PR #1824 addresses this issue and has already been merged. We'll update the issue once it's released.

[hchenatsafe]

Oh that's awesome, thank you!

[sfc-gh-dszmolka]

Released with JDBC v3.19.0 in August 2024 release cycle