When using a custom connector, does PowerApps OAuth2 implementation allow for the client/application flow?
I can use the accessCode flow just fine, but I cannot use the 'client' flow. Heres the relevant part of my swagger doc:
"description": "OAuth2 Application Flow",
"impersonate": "Fully impersonate"
When trying to create this connector, I get the follow error:
Manage your custom connectors | Microsoft Flow
So far, in PowerApps, authentication mechanism OAuth 2.0 is supported for specific services like Dropbox, Facebook, and SalesForce. I saw an idea submitted in the forum and you can vote there:
Thanks for your reply, but I think it is confusing, and even misleading; Generic OAuth2 is supported for Custom Connectors for use in connecting PowerApps/Flows to custom APIs. In fact, I have several custom connectors pointing to my custom API using OAuth2 right now.
But my question is more specific than this; of the OAuth2 flows, the accessCode flow works great, but I do not seem to be able to use the client/application flow.
Can anyone confirm if this is supported?
I am getting the same error if I use a FLOW other than IMPLISIT.
In both cases here what is common is that the FLOW is pointing to APPLICATION which is required when the Grant Type is Client Credentials.
I got Swagger validation elswhere!
The request failed with error: 'Parsing error(s): JSON is valid against more than one schema from 'oneOf'. No valid schemas. Path 'securityDefinitions.oauth_2_client_credentials_auth', line 51, position 41.'. The tracking Id is '29510f5e-bcc8-4d0b-a9d4-53e945928d58'.
Learn how to create your own user groups today!
Explore the latest tools,training sessions,technical expertise, networking and more.
Check out the new Power Platform Community Connections gallery!
Congratulations, the new Super User Season 2 for 2021 has started!
Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.