Support client credentials grant type

Type of Connector

Custom Connector

Name of Connector

Custom OAuth

Is your feature request related to a problem? Please describe.

I have a few 3rd party apps that use the client credentials grant type. Because of this, I am unable to successfully add them as a custom connector. The workaround is to just call them directly with the HTTP action in the flow itself but it is extremely inefficient. I am happy to provide more information or examples if it would help.

Describe the solution you'd like

I would like to be able to leverage the client credentials grant type when creating a custom connector that uses Oauth2.0. Ideally, I would be able to put in my own custom request types to accommodate more 3rd party applications for custom connectors. i.e. In one application, they use 'audience' as a token request.

Describe alternatives you've considered

Today I use the http trigger/action in the flow itself to call the api and just do not create the custom connector at all.

Additional context

N/a

Start with the custom connector OAuth2.0 configuration and the token request handling described in the issue. Review how the HTTP action currently serves as the workaround, then define what support for the client credentials grant and custom token request fields such as audience would require; done means the listed third-party apps can be configured without direct HTTP actions.