Custom Connector and end user credentials

[asitjena]

Hello there,

I have a very fundamental question here. Let me start with the situation:

1. I have developed a custom connector and a connection using oAuth 2.0

2. Shared the connector and connection

3. Suppressed the consent pop-up using powershell method as described in the documentation

4. Used the connection in simple powerapps app.

4. All this is done with an admin account.

Now I am switching to a normal user account. Trying to use the app. App is working fine, but behind the screen what is see, it is using the admin credentials to call my backend API. That is a compliance issue, as we would like to know who is the use that called the api.

Is there a way to pass the current user credentials all through the interaction, end-to-end. This means, I would like to suppress the consent pop-up, but would like current user credential be used for calling the API. 

Thank you!

[SamratGavale]

If you want your API to be invoked using individual user's credentials, you should not suppress the consent popup. That way when users will have to sign in using oAuth when they open the app for 1st time and a separate connection will be created for each user. 

[Syndicate_Admin]

I am clear on that flow. But that is not a good user experience and business user may not have idea of what this connector and connection is all about. On top of it, if we have more connections, then it just adds up more inconvenience. So, we need some innovative idea/solution here, which can solve the problem with proper user experience. Power platform has to come give "right" focus to user experience. 

[asitjena]

Microsoft Team, Please let me know if you have any solution here. I would refrain from making an app with bad UX and same time using author's credentials under the hood. If you don't have any solution, unfortunately we have to drop powerapps from our road map for the strategic initiative.