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

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
Super User
Super User

Re: custom connector secure using Azure Active Directory and OAuth2

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!
1 REPLY 1
Super User
Super User

Re: custom connector secure using Azure Active Directory and OAuth2

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!

Helpful resources

Announcements
firstImage

Watch Sessions On Demand!

Continue your learning in our online communities.

SecondImage

PowerApps Monthly Community Call

Next Wednesday, September 18th at 8am PDT

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

FirstImage

Power Platform World Tour

Coming to a city near you

thirdimage

PowerApps Community User Group Member Badge

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

FourthImage

Join PowerApps User Group!!

Connect, share, and learn with your peers year-round

SecondImage

Power Platform Summit North America

Register by September 5 to save $200

Top Kudoed Authors
Users Online
Currently online: 58 members 4,389 guests
Please welcome our newest community members: