cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
aabrin
Advocate II
Advocate II

MAJOR Connections security hole - PowerApp shares any related Connections with all users to be able to create their OWN PowerApps

If I create a PowerApp with a Connection to a SQL Server database, any user that I grant permission to use my PowerApp is then given "Can Use" permissions on the connection, and can then subsequently go create their OWN PowerApp using MY Connection.

 

This is not made clear ANYWHERE in the process, and I can guarantee there are tons of users who don't understand or expect this to be the case.  It means that ANY in-app data access management is right out the window if any user has the ability to make their own applications in the environment.  If UserA is only meant to have access to RoleA data in my app, they can simply go create a new application, use the Connection from my application, and have it feed in ANY data from the connection they want.

 

This is really heinous, and needs to be addressed in some way ASAP.  This is undercutting the basic expectations of your users about how data permissions will pass through these applications.

1 ACCEPTED SOLUTION

Accepted Solutions
timl
Super User
Super User

Hi @aabrin 

I agree that many users will not be aware of this, so thanks for highlighting this issue to those that may not appreciate the workings of a shared SQL connector.

I know you will have seen these posts already, but I would suggest that anyone affected by this vote on these ideas. I think this would be the most effective route towards progressing a fix for this issue.

 

https://powerusers.microsoft.com/t5/PowerApps-Ideas/Making-SQL-Connector-Secure/idi-p/112599

 

https://powerusers.microsoft.com/t5/PowerApps-Ideas/Removing-user-ability-to-access-data-source-with...

View solution in original post

4 REPLIES 4
v-yuxima-msft
Community Support
Community Support

Hi @aabrin ,

 

Thanks for your post.

Please reference this case:

https://powerusers.microsoft.com/t5/General-Discussion/Role-based-Security-implementation-in-PowerAp...

 

Hope this could be helpful.

 

Best Regards.

Yumia

 

timl
Super User
Super User

Hi @aabrin 

I agree that many users will not be aware of this, so thanks for highlighting this issue to those that may not appreciate the workings of a shared SQL connector.

I know you will have seen these posts already, but I would suggest that anyone affected by this vote on these ideas. I think this would be the most effective route towards progressing a fix for this issue.

 

https://powerusers.microsoft.com/t5/PowerApps-Ideas/Making-SQL-Connector-Secure/idi-p/112599

 

https://powerusers.microsoft.com/t5/PowerApps-Ideas/Removing-user-ability-to-access-data-source-with...

View solution in original post

v-yuxima-msft
Community Support
Community Support

Hi @aabrin  @timl ,

 

Thanks for your posts.

 

Best Regards.

Yumia

That is very helpful for setting up role based security in a single application, which is genuinely something I need to do, so thank you for that.

 

Unfortunately I also think it might only exaserbate the fact that if a user is also a Maker in a given environment, this gives the *impression* of role level security for the data connection backing the application, but actually they can go take that connection and create their *own* application which would then let them see any and all data available.

Helpful resources

Announcements
UG GA Amplification 768x460.png

Launching new user group features

Learn how to create your own user groups today!

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

M365 768x460.jpg

Microsoft 365 Collaboration Conference | December 7–9, 2021

Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.

Top Solution Authors
Top Kudoed Authors
Users online (1,151)