![Reggy van young tin lizzy](https://loka.nahovitsyn.com/142.jpg)
![private cache access private cache access](https://www.maptown.com/v/vspfiles/photos/MD164-2T.jpg)
These goals are described by the following diagram. The same Azure AD tenant, users, groups, managed identities, service principals, roles and RBAC can stay intact. In case any of the backend (vendor) systems is replaced, what needs to be changed is limited to API Management policy, instead of Azure application code. Shielding an Azure application and its security from backend (vendor specific) security schemes.An Azure application can use any of the OAuth2 grant flows with a single Azure-native Identity Provider: Azure AD and its token issuer to access the backend services. Replacing multiple different backend identity providers/token issuers by a single one: Azure AD, to protect the list of backend REST API services.If backend is one or multiple different vendors’ services protected by different Identity Providers and token issuers, we can use API Management as a gateway to achieve the following goals: In addition, we assume the backend service is not necessarily protected by Azure AD. Here we present an API Management policy which can not only acquire access token, but also cache and renew upon its expiration.
#PRIVATE CACHE ACCESS HOW TO#
This document shows how to acquire access token from Azure AD thru client credentials flow. Dan Balma, Maarten Van De Bospoort, Vishnu Naga Praveen Deepthimahanthi, Nick Drouin, Kreig DuBose, David Giard, Michael Green, Binay Kumar, Hao Luo, Shubhaangi Mahajan, Maggie Marxen, Andres Robinet, Jatin Sharma, Taru Sinha, David Triana, Jeremy Woo-Sam, Franco ZuccarelliĪPI Management can acquire access tokens from backend before forwarding calls with the access token to the backend.
![Reggy van young tin lizzy](https://loka.nahovitsyn.com/142.jpg)