Custom Connector

(0) Share

Report

Posted on by bebeben10

Hi,

Can anyone point me to the right direction?

I am trying to create a custom connector using OAuth 2.0 as the authentication and Azure Active Directory as the Identity Provider.

I have successfully created a connection using client id, client secret and tenant id. However, I am getting 401 status code when I tried the operation.

What I have done so far:

- Used postman with the same details and successfully connected.

- Created a flow with http request action that requests the token and another http request action for the actual request.

Upon inspecting the difference using jwt.ms, the token generated by the custom connector has an audience of https://apihub.azure.com.

As per copilot, this is the architecture I need to follow:

Thanks in advance!

Categories:

Connector development

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

11manish 2,126 on at

Like (0)

Report
Copy link

Link copied!

The 401 error occurs because the custom connector is acquiring a token with the audience set to https://apihub.azure.com, which is not

accepted by your API.

This happens because Power Platform acts as an intermediary when using OAuth.

To fix this, you must configure your API in Azure AD with a proper Application ID URI, expose scopes, and update the custom connector to

request a token for your API (not API Hub). y

Alternatively, you can bypass the connector OAuth and manually acquire and pass the token using HTTP actions.

Was this reply helpful? Yes No
bebeben10 81 on at

Like (0)

Report
Copy link

Link copied!

Thanks for your reply @11manish.

Could you see anything that I am missing or doing anything wrong in terms of configuration of the API based on the screenshots below?

Also, if you could kindly expound further the alternative option? Bypassing the OAuth and manually acquiring the token.

Thanks!

Was this reply helpful? Yes No
11manish 2,126 on at

Like (0)

Report
Copy link

Link copied!

In first look, it is fine.

You can use Azure Function as alternative where every activites related to Auth should implement under the azure function.

You just need to consume it.

Was this reply helpful? Yes No