cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

PowerApps ask for enpoint key to end users

Hi Team, 

 

I integrated PowerApps with a QnAmaker, creating a custom connection. 

When I share my Powerapps with end users, it request them to authorized using the QNAMaker end point key. 

 

This is not the ideal scnerio as I cannot share the key with endusers.

Is there a setting I can change to make users use my APP without asking any endpoint key.

 

Thanks in advance !

 

1 ACCEPTED SOLUTION

Accepted Solutions
Super User
Super User

Re: PowerApps ask for enpoint key to end users

Hi,

 

I don't think this exists as it would defeat the point of having licenses per active user as you could then potentially run an entire organisation via one license -  Any connector will initially try use the user's credentials when trying to authenticate, so it will ask them for the key if their user credentials are not sufficient enough to set up the connector.

So if the connector only requires your O365 credentials, then the user will see an 'allow access' screen (unless you set to bypass consent using powershell), however even if you bypasssed consent in this case, I think you would still have the issue of the connector needing the key and prompting the user for it.

 

You might be able to get your App to trigger a flow to run another flow (that's run under your account), but I haven't tested this to confirm if this would work, and I feel like it wouldn't as it would be trying to circumvent licensing again.

 

Regards,

@iAm_ManCat




Don't forget to 'Mark as Solution' and 'Thumbs Up' those who deserve it!
1 REPLY 1
Super User
Super User

Re: PowerApps ask for enpoint key to end users

Hi,

 

I don't think this exists as it would defeat the point of having licenses per active user as you could then potentially run an entire organisation via one license -  Any connector will initially try use the user's credentials when trying to authenticate, so it will ask them for the key if their user credentials are not sufficient enough to set up the connector.

So if the connector only requires your O365 credentials, then the user will see an 'allow access' screen (unless you set to bypass consent using powershell), however even if you bypasssed consent in this case, I think you would still have the issue of the connector needing the key and prompting the user for it.

 

You might be able to get your App to trigger a flow to run another flow (that's run under your account), but I haven't tested this to confirm if this would work, and I feel like it wouldn't as it would be trying to circumvent licensing again.

 

Regards,

@iAm_ManCat




Don't forget to 'Mark as Solution' and 'Thumbs Up' those who deserve it!

Helpful resources

Announcements
firstImage

Watch Sessions On Demand!

Continue your learning in our online communities.

SecondImage

Follow PowerApps on Twitter

Stay Up-to-Date by following PowerApps on Twitter

Top Community Contributors for July 2019

Top Community Contributors for July 2019

Let's thank our top community contributors

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

FirstImage

Power Platform World Tour

Coming to a city near you

thirdimage

PowerApps Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

FourthImage

Join PowerApps User Group!!

Connect, share, and learn with your peers year-round

FifthImage

Dynamics 365 and Power Platform April 2019 Release notes

Features releasing from April 2019 through September 2019!

Top Kudoed Authors
Users Online
Currently online: 45 members 4,152 guests
Please welcome our newest community members: