[ADAP-1049] [Bug] Snowflake SSO Token expiration not surfaced in logs

[colin-rogers-dbt]

Is this a new bug in dbt-snowflake?

• I believe this is a new bug in dbt-snowflake
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

SSO auth is silently failing after token expiration. This is due to the exception handling assuming that none is the only failure signal so when we go to return the access token (i.e. return result_json["access_token"]) it fails as the "access_token" isn't in the result_json.

Section of code:

dbt-snowflake/dbt/adapters/snowflake/connections.py

Line 237 in 62f7594

if result_json is None:

Expected Behavior

If the access_token is not in result_json we return an auth failure exception with the exception message from snowflake.

Steps To Reproduce

See: https://dbtlabs.atlassian.net/browse/CC-860
On Version 1.5.9 ->
Token expired for Snowflake SSO ->
Run ‘dbt run’ command in the IDE

Relevant log output

No response

Environment

- OS:
- Python:
- dbt-core:
- dbt-snowflake:

Additional Context

No response

[jtcohen6]

I think this could be a relatively simple addition within our exception_handler. An illustrative example: 382a890

To test this, I'd hope that we could extend TestSnowflakeOauth but with an invalid refresh token.

[colin-rogers-dbt]

Use unit tests instead of functional test