-
Notifications
You must be signed in to change notification settings - Fork 29
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
Feature Request: Snowflake: SSO Single Sign On (Microsoft) #859
Comments
Unfortunately it’s very unlikely I will be able to add SSO for snowflake. I asked the snowflake team about this back in 2020 and they said it was backlogged with no plans to add support. I’ve reached out to them again ( Sorry for the bad news! |
I appreciate your checking with them. I'm trying to consider alternative methods to secure our Snowflake instance better. Do you have any way to support MFA (including the word multi-factor authentication for searchability) with Snowflake? |
Snowflake support in SQLPro currently only provides username and password authentication and this will mostly likely not change in 2013. There is a possibility MFA would work if you specify your password in the format of <password_string><passcode_string> (similar to how the snowflake documentation suggests for an ODBC connection) but it's not something I'm currently supporting. |
Closing as a copy of #661. |
Is your feature request related to a problem? Please describe.
Our organization is switching our Snowflake authentication to SSO via Microsoft. Because of this, we'll no longer be able to use SQLPro Studio unless we are able to authenticate via SSO in SQLPro Studio.
Describe the solution you'd like
I'd like SSO sign-in via Microsoft to be implemented in SQLPro Studio.
Describe alternatives you've considered
The only alternative really available to us would be to use a different SQL client.
Additional context
We have a hard cutoff of February 10 by which we have to switch and will no longer be able to use SQLPro Studio without this feature enabled. If possible, it'd be great to have this implemented by then so our whole team can continue to use.
The text was updated successfully, but these errors were encountered: