cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
devdoc
Regular Visitor

custom connector secure using Azure Active Directory and OAuth2

I have a custom connector that needs to use Azure active directory to do oauth2 to secure it. Is there any documentation or examples I can use to set the API up correctly in Azure and what the connector's security tab page also needs?  I have not found any good examples to try to duplicate.  I need to secure the custom rest api.

1 ACCEPTED SOLUTION

Accepted Solutions
yashag2255
Dual Super User II
Dual Super User II

Hi @devdoc 

 

Yes you can create the connector by following the below article:
 
Based on this article, you can create both backend and client application registrations, once this is configured, create a custom connector from blank and update your security settings as:
 
Authentication type: OAuth 2.0
Identity Provider: Azure Active Directory
Client ID: Client ID for Client App Registration
Client Secret: Client Secret for Client App Registration
Resource URL: Client ID fot Backend App Registration.
 
Lastly, update the rediect url created in your custom connector, into your client Application registration, remove the existing value and add this newly created one, this is same for all connectors and it is: https://global.consent.azure-apim.net/redirect
 
Hope this Helps!
 
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

View solution in original post

2 REPLIES 2
yashag2255
Dual Super User II
Dual Super User II

Hi @devdoc 

 

Yes you can create the connector by following the below article:
 
Based on this article, you can create both backend and client application registrations, once this is configured, create a custom connector from blank and update your security settings as:
 
Authentication type: OAuth 2.0
Identity Provider: Azure Active Directory
Client ID: Client ID for Client App Registration
Client Secret: Client Secret for Client App Registration
Resource URL: Client ID fot Backend App Registration.
 
Lastly, update the rediect url created in your custom connector, into your client Application registration, remove the existing value and add this newly created one, this is same for all connectors and it is: https://global.consent.azure-apim.net/redirect
 
Hope this Helps!
 
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

View solution in original post

KyleH
Frequent Visitor

Can you clarify your post more? I'm attempting to match your list with the documentation.


Client ID - Is this the 'Secret ID' or 'Application (Client) ID'?
Client Secret - Is this the 'Secret Value' or 'Secret ID'?

KyleH_0-1632345753565.png


Resource URL - Is this the application (client) ID?

 

KyleH_1-1632345801618.png

 

Thank you!

 

Helpful resources

Announcements
User Group Leader Meeting January 768x460.png

Calling all User Group Leaders!

Don't miss the User Group Leader meetings on January, 24th & 25th, 2022.

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

Top Solution Authors
Top Kudoed Authors
Users online (1,189)