-
Notifications
You must be signed in to change notification settings - Fork 427
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
okta auth #37
Comments
In general snowflake provides the ability to use oauth tokens to authenticate when using command line tools or even connectors within programs. We should support the ability to provide an oauth token as a form of authentication. |
@mhaley-miovision at my company, we have a potential use case for oauth access tokens as well. I just put out a PR for this. It's limited in scope since it requires you to have a valid, non-expired access token, but might satisfy your command line tool use case |
<!-- Feel free to delete comments as you fill this in --> Adds OAuth access token support as requested [in this ticket](#37). Note this does not add logic around renewing the access token. If the access token is not valid, the user is presented with the Snowflake error. We at Flexport have a potential use case where we would like to generate short-lived OAuth tokens and distribute to an application or user for a brief period of time. <!-- summary of changes --> ## Test Plan <!-- detail ways in which this PR has been tested or needs to be tested --> * [x] Manual acceptance test: Generated valid oauth access token from Snowflake account with the correct roles, and verified that the roles are correct * [x] Manual acceptance test: Verified that when an empty access token is used, Snowflake reports "missing password" * [x] Unit test: DSN unit test corresponding to tests above ## References <!-- issues documentation links, etc --> * [Snowflake OAuth Flow for Custom Clients](https://docs.snowflake.com/en/user-guide/oauth-custom.html#configure-snowflake-oauth-for-custom-clients)
We are closing this issue as part of a cleanup described in announcement. If you believe that the issue is still valid in v0.89.0, please open a new ticket. |
No description provided.
The text was updated successfully, but these errors were encountered: