microsoft / microsoft/PowerPlatformConnectors
[FEATURE REQUEST] Custom Connectors with client credentials OAuth
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 1.5k
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 11
Description
Type of Connector
Custom Connector
Name of Connector
Custom Connectors
Is your feature request related to a problem? Please describe.
As a follow up to #225.
Currently it is impossible to use client_credentials in the OAuth definition for Custom Connectors. This issue has been around a while see the Power Automate Idea from 5 years ago.
It would be great if we could integrate PowerAutomate into our system using a "Service Connection", one authorized connection all Flows can share without any User logging in, as I understand it, that is what the client_credentials is for. In the Swagger editor we can see the different flows available:
- implicit
- password
- application
- accessCode
It seems impossible to change this and save the Custom Connection, in addition client_credentials is missing from this list.
Describe the solution you'd like
An additional dropdown in the OAuth section of the Custom Connector Security tab, where we can accurately update the information for each one of the flows available as well as adding the client_credentials flow
Describe alternatives you've considered
- Users logging in for each flow doesn't really work for us at the moment
- We are considering a "simple" API key solution for now, but we are not a fan
Additional context
N/a
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or code entry points are identified in the issue. Start by reviewing follow-up issue #225 and the Custom Connector Security tab behavior described here; done means supporting client_credentials and allowing the listed OAuth flows to be configured and saved.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100