c# - How many applications should be defined in Azure B2C for a micro-service based infrastructure? -


in preview azure ad b2c can define applications. each application given name, client id, app key , few settings define whether include web app / web api , whether allow implicit flow. in 'old' world of azure ad had greater control interaction between applications such "this application can access graph api", or "this application can talk service" whereas in new world order doesn't appear possible (at least portal ui perspective). question is: given lack of apparent control in azure ad b2c infrastructure has growing number of microservices, make sense create 'application' per service in azure ad b2c (and indeed per environment)? or should whole system share same application (and therefore client id?).

(i comment on current score not allow me that)

what do: have client ids each web , api app (container micro services). when initializing authentication api apps put client ids allowed talk api in validaudiences:

    public static string clientids = configurationmanager.appsettings["validclientids"];      public void configureauth(iappbuilder app)     {         tokenvalidationparameters tvps = new tokenvalidationparameters         {             // specify api accepts tokens own clients             validaudiences = clientids.split(',')         };          app.useoauthbearerauthentication(new oauthbearerauthenticationoptions         {             // securitytokenprovider fetches azure ad b2c metadata , signing keys openid connect metadata endpoint             accesstokenformat = new jwtformat(tvps, new openidconnectcachingsecuritytokenprovider(string.format(aadinstance, tenant, globals.odicendpointversion, globals.oidcmetadatasuffix, commonpolicy)))         });     } 

Comments

Popular posts from this blog

java - Suppress Jboss version details from HTTP error response -

gridview - Yii2 DataPorivider $totalSum for a column -

Sass watch command compiles .scss files before full sftp upload -