cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
BartVermeersch
Level: Powered On

Custom Connectors - troubleshoot Oauth 2.0 - Generic Oauth 2

I'm trying to create a custom connector based on oauth2 to a Saas solution (https://canvas.instructure.com/doc/api/file.oauth.html)

 

I'm able to create a connection to allow the connector to connect on my behalf and I have access to the API action I want to perform.

 

But when testing the custom connector, I receive a 401. In the test request I see a bearer token send to https://europe-001.azure-apim.net/apim/canvas.20flow.5fc4....

 

{
  "Authorization": "Bearer eyJ..."
}

 

The error message is:

{
  "errors": [
    {
      "message": "Invalid access token."
    }
  ]
}

 

Can I troubleshoot this further without having access to the Flow or SaaS backend?

1 ACCEPTED SOLUTION

Accepted Solutions
BartVermeersch
Level: Powered On

Re: Custom Connectors - troubleshoot Oauth 2.0 - Generic Oauth 2

Hi Mabel, thanks!

 

We found the solution. The base url was still referring to a test environment while all other url's were updated to production url's..

 

Bart

View solution in original post

2 REPLIES 2
Community Support Team
Community Support Team

Re: Custom Connectors - troubleshoot Oauth 2.0 - Generic Oauth 2

Hi @BartVermeersch,

 

Have you created the connection successfully?

The error message means that the access token you are using is invalid. Please try to verify access token and try again.

Please check the following doc for more details:

https://docs.apigee.com/api-platform/reference/policies/oauth-http-status-code-reference#verifyacces...

https://www.oauth.com/oauth2-servers/access-tokens/access-token-response/

 

Best regards,

Mabel

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
BartVermeersch
Level: Powered On

Re: Custom Connectors - troubleshoot Oauth 2.0 - Generic Oauth 2

Hi Mabel, thanks!

 

We found the solution. The base url was still referring to a test environment while all other url's were updated to production url's..

 

Bart

View solution in original post

Helpful resources

Announcements
firstImage

Microsoft Business Applications Virtual Launch Event

Watch the event on demand for an in-depth look at the new innovations across Dynamics 365 and the Microsoft Power Platform.

firstImage

Watch Sessions On Demand!

Continue your learning in our online communities.

Power Platform 2019 Release Wave 2 Plan

Power Platform 2019 Release Wave 2 Plan

Features releasing from October 2019 through March 2020.

thirdimage

Flow Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

fifthimage

Microsoft Learn

Learn how to build the business apps that you need.

sixthImage

Power Platform World Tour

Find out where you can attend!

seventhimage

Webinars & Video Gallery

Watch & learn from the Flow Community Video Gallery!

Users Online
Currently online: 80 members 2,950 guests
Please welcome our newest community members: