Re: [Architecture] [APIM 3.0.0] Publisher REST APIs for mediation policies

2019-08-15 Thread Ishara Cooray
For viewing, shall we use a single scope: apim:mediation_policy_view But, it make sense to have the apim:api_view scope to view mediation policies of an api IMO If not, a user with apim:api_view scope can see the api but unable to see the mediation policies due to missing

Re: [Architecture] [APIM 3.0.0] Publisher REST APIs for mediation policies

2019-08-15 Thread Malintha Amarasinghe
Hi Ishara, +1 for the overall approach. For viewing, shall we use a single scope: apim:mediation_policy_view Also for the tag: shall we simplify as "Mediation Policies" Thanks! On Tue, Aug 13, 2019 at 1:18 PM Ishara Cooray wrote: > Hi, > I have started working on the $Subject and below is

[Architecture] [APIM 3.0.0] Publisher REST APIs for mediation policies

2019-08-13 Thread Ishara Cooray
Hi, I have started working on the $Subject and below is the rest api definitions. - To avoid string manipulations, Mediation policy post is done as a file upload. Hence we can provide the sequence file(xml content) as an input in the form of multipart/form-data ex: curl -X POST