Skip to content

SNOW-1791788: Browser authentication timeout timer not cleared on successful authentication #953

Closed as not planned
@adriancooney

Description

@adriancooney

If you need urgent assistance then file a case with Snowflake Support.
Otherwise continue here.

Please answer these questions before submitting your issue.
In order to accurately debug the issue this information is required. Thanks!

  1. What version of NodeJS driver are you using?

1.14.0

  1. What operating system and processor architecture are you using?

Operating System: Darwin (macOS)
Kernel Version: 23.6.0
Processor Architecture: ARM64

  1. What version of NodeJS are you using?
    (node --version and npm --version)
$ node -v
v22.5.1
$ pnpm -v
9.5.0
  1. What are the component versions in the environment (npm list)?

  2. What did you do?

  3. Create a connection using createConnection with the authenticator set to EXTERNALBROWSER.

  4. Call connectAsync which opens up browser tab.

  5. Complete authentication flow successfully.

  6. Execute simple query (< 3 seconds).

  7. Close the connection.

  8. Expect program to exit - it does not.

  9. What did you expect to see?

Expect program to exit - it does not.

There is an open timer, created here, preventing the program from exiting. The timer is essentially a timeout for the browser authentication. It should be cleared if the authentication was successful.

  1. Can you collect debug logs?
[WTF Node?] open handles:
- File descriptors: (note: stdio always exists)
  - fd 1 (tty) (stdio)
  - fd 2 (tty) (stdio)
- Timers:
  - (120000 ~ 2 min) (anonymous) @ ./node_modules/.pnpm/[email protected][email protected][email protected][email protected]/node_modules/snowflake-sdk/lib/authentication/auth_web.js:181

⚠️ Before sharing any data, please be sure to review the log and remove any sensitive
information.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugSomething isn't workingduplicateThis issue or pull request already existsstatus-triage_doneInitial triage done, will be further handled by the driver team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions