article Qlik Cloud: Qlik Snowflakes Connector using OAuth authentication in Official Support Articles

Qlik Cloud: Qlik Snowflakes Connector using OAuth authentication

Ayaka_Hanazono — Thu, 15 Feb 2024 09:56:18 GMT

You can use an OAuth authentication for the Qlik Snowflake connector. Snowflakes allow configuring External Auth to integrate your OAuth server. Find more details on External OAuth

This instruction describes configuring Azure AD as an External OAuth Authorization Server and creating a Snowflake connection to Qlik Sense SaaS. (O Auth is only available in the SaaS edition)

Qlik Help: Create a Snowflake connection

This is only applicable to Qlik Sense SaaS (Qlik Cloud). See Create a Snowflake connection | Authentication.

OAuth configuration for Snowflake in Azure AD
1. Create Snowflake OAuth Resource and Client: HOW TO: CREATE EXTERNAL OAUTH TOKEN USING AZURE AD ON BEHALF OF THE USER
2. Step # 4 for both resource and client, do not forget to add "Redirect URL."https://connector.qlik.com/auth/oauth/v2.htm
3. This is required for the Qlik Snowflake connection.
4. Generate a token for verification
5. cURL Follow the instructions on the same page HOW TO: CREATE EXTERNAL OAUTH TOKEN USING AZURE AD ON BEHALF OF THE USER
6. Python connector HOW TO: TEST AZURE OAUTH CONNECTION TO SNOWFLAKE END TO END USING PYTHON (USER CREDENTIALS FLOW)
7. Avoid using an AD that enables another IDP, which could cause an authentication failure
Configuration in Snowflake
1. Create an OAuth Authorization Server in Snowflake.
2. Create a security integration: Step 4: Create an OAuth Authorization Server in Snowflake
3. Use the command under Create an OAuth Authorization Server with Audiences
Create a Snowflake connection: Create a Snowflake connection

For Azure AD, the property, Scope is required. Insert a scope configured under Expose an API of the Snowflake OAuth Resource.
It's also possible to create a connection via an ODBC driver provided by Snowflake: ODBC Driver
1. Install and Configure the ODBC Driver for Windows: Installing and Configuring the ODBC Driver for Windows
2. Add a parameter to enble OAuth. Add a new parameter, token to the registry, along with a generated token.
3. Verify a connection using Qlik Sense Desktop. For SaaS, QlikData Transfer will load data via the ODBC drivers.

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Re: Qlik Sense SaaS: Qlik Snowflakes Connector using OAuth authentication

ArockiyaM — Fri, 11 Aug 2023 08:03:49 GMT

Hi @Ayaka_Hanazono ,

Can you please elaborate why we need to redirect to "https://connector.qlik.com/auth/oauth/v2.htm"?

What kind of operation will happen on this endpoint?

Is there any alternative method available instead of this URL?

Regards,

Arockiya.

Re: Qlik Sense SaaS: Qlik Snowflakes Connector using OAuth authentication

qlikster — Tue, 13 Feb 2024 13:55:46 GMT

Hi,

is this also possible with Qlik Sense Client-Managed ?

Re: Qlik Sense SaaS: Qlik Snowflakes Connector using OAuth authentication

Sonja_Bauernfeind — Thu, 15 Feb 2024 09:50:56 GMT

Hello @qlikster

OAuth is only available for Qlik Sense SaaS. See Snowflake Connection | Availability.

All the best,
Sonja

Re: Qlik Cloud: Qlik Snowflakes Connector using OAuth authentication

wayne-a — Fri, 27 Jun 2025 14:53:35 GMT

I didn't see any reply to the question above: Can you please elaborate why we need to redirect to "https://connector.qlik.com/auth/oauth/v2.htm"?

I don't understand this either. Where do we do this redirect?

I'm trying to set up OAUTH through Entra IDP to Snowflake but cannot get this to work (case 00388241) and this document isn't easy to follow, for me anyway. I've successfully used this Entra IDP with other products and they work as expected.

On Qlik Cloud, when I set it up and try to authenticate, a separate browser tab opens with this message "AADSTS900971: No reply address provided" which seems to correlate to the redirect mentioned. It's almost like it is trying to authenticate with my personal credentials instead of the application level credentials we set up in Entra.

Re: Qlik Cloud: Qlik Snowflakes Connector using OAuth authentication

Sonja_Bauernfeind — Mon, 30 Jun 2025 06:27:59 GMT

Hello @wayne-a

"https://connector.qlik.com/auth/oauth/v2.htm" is the URL used for all Qlik Connector for Oauth authentication. There is no alternative.

Your assigned support agent is still reviewing your request, and we will be in touch.

All the best,
Sonja

Re: Qlik Cloud: Qlik Snowflakes Connector using OAuth authentication

wayne-a — Mon, 30 Jun 2025 14:44:57 GMT

Hi Sonja, thank you for the reply. I understand we have to use the redirect, but the instructions aren't clear where to set that up.

Step 1 above outlines setting up Azure AD (Entra).

In 1.b. it says "Step # 4 for both resource and client, do not forget to add "Redirect URL."".

But Step 4 in the linked Snowflake document( https://community.snowflake.com/s/article/Create-External-OAuth-Token-Using-Azure-AD-For-The-OAuth-Client-Itself), is "Create an External OAuth Security Integration in Snowflake". So I'm confused if I'm adding the redirect in the Entra Application and Client Application setup or in Snowflake.

I've used the Snowflake document to set up an existing Entra IDP with multiple client apps for other products that don't have this requirement so I'm trying to understand where this extra setup goes.

Thank you for your help.