microsoft / microsoft/PowerPlatformConnectors

Snowflake Connector Instant Flow Fails after app share

Open
#2,809 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
1.3k
Forks
1.5k
Avg merge
5d 15h
Merged PRs (30d)
11

Description

Type of Connector

Certified Connector

Name of Connector

Snowflake

Describe the bug

When creating an instant flow within a canvas app. The flow can be used to access the snowflake data with no issues by the flow creator. When the application is shared with others the users are prompted to login to Snowflake with SSO. After login and upon launching the PowerApp the instant flow will load until timeout and never return data unless the user has defined a Default Role in their Snowflake profile. The user can still query via the Snowflake UI and Power BI with no issues even without a Default Role.

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 1 - Connector is broken or there's a very serious issue

To Reproduce

Create a canvas app
Add an instant flow that returns data using the Snowflake Connector
Share the application and flow with another user
Ask user to try and load data into the application
Data will never load and timeout

Expected behavior

This should work exactly like the SQL server connector that allows implicit access to the data via the flow creators account. App Users should not have to login to Snowflake after the app has already been shared with them the app should retrieve data using the flow creators account.

Environment summary

Powerapps canvas app
Power automate instant flow
Snowflake Connector

Additional context

This is preventing effective use of the Snowflake functionality. Apps that are created to use the instant flow to retrieve data are only usable by the app creator and cannot be shared.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Snowflake Connector authentication path for an instant flow used by a shared canvas app, comparing it with the SQL server connector behavior described in the report. Reproduce the timeout with a user who has no Snowflake Default Role, then verify that shared app users can retrieve data without an unnecessary Snowflake login.

Written by the indexing model from the issue text.

Assessment

Domain
api, authentication, backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.