How OAuth 2.0 Configuration is different from In-bound policies settings in Azure API Management?

0
votes

I'm developing a serverless micro services application in Azure.

In-order to securing the APIs, I have registered both Service & Client Application with Azure AD and grand API access to client app.

So, In API Management instance I have updated the in-bound policies (to Verify JWT token) based on Azure AD configuration. Now its working as expected.

But my question is without adding any configuration in API Management console "OAuth 2.0" section, how its working?

How OAuth 2.0 configuration is different from In-bound policies settings in Azure API Management?

2
azureoauth-2.0azure-functionsmicroservicesazure-api-management

2 Answers

1
votes

The blade for OAuth 2.0 (and OpenID Connect) are to configure providers which powers the Developer Portal experience.

After defining the providers in these blades, APIs have to be assigned these providers for them to show up in the Developer Portal (in the Try It pages).

Support for OAuth in the new developer portal is not available yet. This issue tracks the feature.

0
votes

Got an answer. OAuth 2.0 Config required only for to use the oauth services in developer portal and consoles.Link