Currently Replicate only supports Snowflake native accounts for Authentication. We would like to have OAuth method to connect to Snowflake as an Endpoint. More tools are going towards OAuth method which is more secured than this native accounts.
Hi Shelly. Thank you so much. Preferebly OAuth as that is the way most of the other leading tools are going as this is more secured. As an example. A user originates from Microsoft Azure AD (Gives level 1 security that all users activity is monitored by SECOPS) and then adding OAuth on top of this adds level 2 security. We are currently using Talend for our ETL/ELT and Spark jobs where it uses OAuth way of Authenticating to Snowflake. We have already integrated Azure AD and enabled on OAuth on Snowflake. It would be just giving this option from Qlik to be able to use this.
Lately SECOPS teams across the companies are against using Native accounts as they are way easy to misuse if we know the password. Also, if we do use Native Accounts they suggest to use some kind of Key Authentication tools like Azure Key vault which is also not yet supported with Replicate. I have another idea on the KeyVault.
Great suggestion! We absolutely need OAuth 2.0 support for both Replicate and Compose - the only alternative is to use SF (non-federated) accounts. The Snowflake browser already integrates with Azure Active Directory (AAD), and other ETL tools use OAuth for programmatic access. In our case, we'd need Qlik to connect to AAD over Azure private link.
NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.