Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SNOW-1292069: Failed to connect with v1.10.0 using externalbrowser authentication #812

Closed
duclet opened this issue Apr 1, 2024 · 3 comments
Assignees
Labels
bug Something isn't working status-fixed_awaiting_release The issue has been fixed, its PR merged, and now awaiting the next release cycle of the connector. status-triage_done Initial triage done, will be further handled by the driver team

Comments

@duclet
Copy link

duclet commented Apr 1, 2024

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?
    v1.10.0

  2. What operating system and processor architecture are you using?
    Manjaro Linux

  3. What version of NodeJS are you using?
    (node --version and npm --version)
    Node v20.9.0

  4. What are the component versions in the environment (npm list)?

5.Server version:* E.g. 1.90.1
You may get the server version by running a query:

SELECT CURRENT_VERSION();
  1. What did you do?

    Upgraded from version v1.9.3 to the new version. I'm not now able to connect anymore using the EXTERNALBROWSER authentication model. It gets the error: Failed to connect: SAML response is invalid or matching user is not found. Contact your local system administrator and provide the error code - .

  2. What did you expect to see?

    Connection successfully.

  3. Can you set logging to DEBUG and collect the logs?

{"level":"INFO","message":"[12:47:18.374 PM]: Trying to initialize Easy Logging"}
{"level":"INFO","message":"[12:47:18.382 PM]: No client config file found in default directories"}
{"level":"INFO","message":"[12:47:18.383 PM]: Easy Logging is disabled as no config has been found"}
{"level":"DEBUG","message":"[12:47:18.384 PM]: 300"}
{"level":"DEBUG","message":"[12:47:18.385 PM]: Contacting SF: /session/v1/login-request?*****&warehouse=****&roleName=*****, (0/7)"}
{"level":"TRACE","message":"[12:47:18.386 PM]: Create and add to cache new agent https://*****.snowflakecomputing.com-keepAlive"}
{"level":"DEBUG","message":"[12:47:18.387 PM]: Proxy settings used in requests: none."}
{"level":"TRACE","message":"[12:47:18.387 PM]: CALL POST with timeout 90000: https://*****.snowflakecomputing.com/session/v1/login-request?*****&warehouse=****&roleName=*****"}
{"level":"DEBUG","message":"[12:47:18.387 PM]: Issuing heartbeat call"}
{"level":"DEBUG","message":"[12:47:18.441 PM]: OCSP validation disabled for *****.snowflakecomputing.com"}
{"level":"DEBUG","message":"[12:47:19.483 PM]: Encountered an error when sending the request. Details: {\"name\":\"OperationFailedError\",\"code\":\"390133\",\"message\":\"SAML response is invalid or matching user is not found. Contact your local system administrator and provide the error code - . The administrator can obtain troubleshooting information at https://docs.snowflake.com/en/user-guide/errors-saml#saml-error-codes.\",\"data\":{\"nextAction\":\"RETRY_LOGIN\",\"authnMethod\":\"FEDERATED\"}}"}
{"level":"DEBUG","message":"[12:47:20.939 PM]: Contacting SF: /session/v1/login-request?requestId=*****&warehouse=****&roleName=*****, (1/7)"}
{"level":"TRACE","message":"[12:47:20.940 PM]: Get agent with id: https://*****.snowflakecomputing.com-keepAlive from cache"}
{"level":"TRACE","message":"[12:47:20.940 PM]: CALL POST with timeout 90000: https://*****.snowflakecomputing.com/session/v1/login-request?requestId=*****&warehouse=****&roleName=*****"}
{"level":"DEBUG","message":"[12:47:21.535 PM]: Encountered an error when sending the request. Details: {\"name\":\"OperationFailedError\",\"code\":\"390133\",\"message\":\"SAML response is invalid or matching user is not found. Contact your local system administrator and provide the error code - . The administrator can obtain troubleshooting information at https://docs.snowflake.com/en/user-guide/errors-saml#saml-error-codes.\",\"data\":{\"nextAction\":\"RETRY_LOGIN\",\"authnMethod\":\"FEDERATED\"}}"}
{"level":"DEBUG","message":"[12:47:25.737 PM]: Contacting SF: /session/v1/login-request?requestId=******&warehouse=****&roleName=*****, (2/7)"}
{"level":"TRACE","message":"[12:47:25.738 PM]: Get agent with id: https://*****.snowflakecomputing.com-keepAlive from cache"}
{"level":"TRACE","message":"[12:47:25.738 PM]: CALL POST with timeout 90000: https://*****.snowflakecomputing.com/session/v1/login-request?requestId=******&warehouse=****&roleName=*****"}

  1. What is your Snowflake account identifier, if any? (Optional)
@duclet duclet added the bug Something isn't working label Apr 1, 2024
@github-actions github-actions bot changed the title Failed to connect with v1.10.0 SNOW-1292069: Failed to connect with v1.10.0 Apr 1, 2024
@sfc-gh-dszmolka sfc-gh-dszmolka self-assigned this Apr 2, 2024
@sfc-gh-dszmolka sfc-gh-dszmolka changed the title SNOW-1292069: Failed to connect with v1.10.0 SNOW-1292069: Failed to connect with v1.10.0 using externalbrowser authentication Apr 2, 2024
@sfc-gh-dszmolka sfc-gh-dszmolka added status-fixed_awaiting_release The issue has been fixed, its PR merged, and now awaiting the next release cycle of the connector. status-triage_done Initial triage done, will be further handled by the driver team labels Apr 2, 2024
@sfc-gh-dszmolka
Copy link
Collaborator

sfc-gh-dszmolka commented Apr 2, 2024

hi and thank you for raising this with us. indeed we're aware of a regression introduced with 1.10.0 affecting externalbrowser auth, and it's fixed in #804

if you can , you can test the fix by installing the connector from main branch, otherwise it will be released with the next upcoming driver version (should be imminent, I see 2024 March release is still pending)

@sfc-gh-dszmolka
Copy link
Collaborator

fix released with 2024 March release cycle in v1.10.1

@duclet
Copy link
Author

duclet commented Apr 9, 2024

Just to confirm that the fix worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working status-fixed_awaiting_release The issue has been fixed, its PR merged, and now awaiting the next release cycle of the connector. status-triage_done Initial triage done, will be further handled by the driver team
Projects
None yet
Development

No branches or pull requests

2 participants