EXTERNALBROWSER based authentication not working, getting "Cannot read properties of null (reading 'proofKey')" error.

[rajeshmuraleedharan]

EXTERNALBROWSER based authentication not working, getting "Cannot read properties of null (reading 'proofKey')" error.

Here is the error log details
[1691774054735] INFO (ext): EXECUTING COMMAND => sqltools.selectConnection
[1691774054736] INFO (ext): EXECUTING COMMAND => sqltools.getConnections
[1691774054736] INFO (ls): REQUEST RECEIVED => connection/GetConnectionsRequest
[1691774054737] INFO (ext): EXECUTING COMMAND => sqltools.getConnections
[1691774054738] INFO (ls): REQUEST RECEIVED => connection/GetConnectionsRequest
[1691774054738] INFO (ls): REQUEST RECEIVED => connection/ConnectRequest
[1691774054738] INFO (ls): Connection instance created for aaaabbbb.east-us-2.azure.
ns: "conn-manager"
[1691774055015] ERROR (ls): TypeError: Cannot read properties of null (reading 'proofKey')
at /Users/uesrname/.vscode/extensions/koszti.snowflake-driver-for-sqltools-0.5.0/node_modules/snowflake-sdk/lib/authentication/auth_web.js:174:24
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
at async auth_web.authenticate (/Users/rajeshmuraleedharan/.vscode/extensions/koszti.snowflake-driver-for-sqltools-0.5.0/node_modules/snowflake-sdk/lib/authentication/auth_web.js:75:18)
at async Connection.connectAsync (/Users/rajeshmuraleedharan/.vscode/extensions/koszti.snowflake-driver-for-sqltools-0.5.0/node_modules/snowflake-sdk/lib/connection/connection.js:262:7)

[archiewood]

Also getting this

[jrudman25]

Issue still exists. I'm using Snowflake v1.21.0, SQLTools v0.28.5, and Snowflake Driver for SQLTools v0.5.0. I managed to bypass the check and successfully connect to Snowflake by running ALTER USER [user] SET MINS_TO_BYPASS_MFA = [mins]; in a Snowflake worksheet in the browser. Then, you can just connect using User & Password for Authenticator type and it will connect without checking for MFA. Definitely a temporary solution, but better than nothing. In order to minimize risk with this fix, make sure to set [mins] as low as possible to allow you just enough time to sign in. This way MFA bypass isn't active for longer than it needs to be.