cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
sdeverly
New Member

Are other flow than accessCode supported by OAuth2 custom connectors?

Hello,

I'm trying to use a custom connector to access a REST api. The REST api uses OAuth2 authentication, but it only supports password and application OAuth2 flows. I downloaded the swagger file for my connector, and tried to change  the flow to application or password but I get an error when I try to update my connector with the modified file:

Specified file does not match OpenAPI 2.0 specification: 'JSON is valid against no schemas from 'oneOf'. Path 'securityDefinitions.oauth2_auth'.'

It seems only accessCode is supported, which prevents me to connect to the REST api.

Any workaround for this problem?

Thanks.

5 REPLIES 5
v-bacao-msft
Community Support
Community Support

Hi @sdeverly,

 

Could you share the details and creation steps of your custom connector?

Please check and see if the following link would help:

https://docs.microsoft.com/en-us/connectors/custom-connectors/

https://docs.microsoft.com/en-us/connectors/custom-connectors/define-openapi-definition

 

Best Regards,

Barry

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
GabrielStJohn
Administrator
Administrator

Hey, @sdeverly!

Thank you for posting on the Flow Community Forum! It appears as though @v-bacao-msft would like some more information in order to further assist you properly with your issue. Please share any additional information that was requested in order to decrease the amount of time that it will take for you to be assisted!

Thank you for being an active member of the Flow Community!

-Gabriel
Flow Community Manager

- Gabriel
Community Manager
Power Automate | Power Virtual Agents
Super User Program Manager



sdeverly
New Member

Hello,

I was trying to build a connector for this API: https://developer.shotgunsoftware.com/rest-api/

Unfortunately it does not support the most standard accessCode OAuth2 workflow: https://developer.shotgunsoftware.com/rest-api/#authentication.

 

I managed to build a workaround by not using a connector, but having http nodes in my flow which:

  • Issue a client_credential request.
  • Retrieve the access token and set it in the headers for subsequent calls to the REST api.

It works, but a new access token is pulled out every time the Flow is evaluated.

Thanks

GabrielStJohn
Administrator
Administrator

Hello, @v-bacao-msft!

Thank you for posting a reply to a topic on the Microsoft Flow Community! It appears that the users who you have been engaging in this thread with are now awaiting your reply! Please follow-up on this thread ASAP.

Thank You!

-Gabriel

Microsoft Flow Community Manager

- Gabriel
Community Manager
Power Automate | Power Virtual Agents
Super User Program Manager



HI @sdeverly , could you please share the configuration of your HTTP nodes? I also similarly need to get an OAuth2 token with 'client_credential'. I have been trying to create a flow to do the same thing but have been getting errors.

Helpful resources

Announcements
MPA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MSFTBizAppsLaunchEvent

Experience what’s next for Power Virtual Agents

See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.

New Super Users

Meet the Power Automate Super Users!

Many congratulations to the Season 1 2021 Flownaut Crew!

Power Platform ISV STudio

Power Platform ISV Studio

ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.

Users online (76,293)