On Tue, Aug 13, 2019 at 7:39 PM Rajith Roshan wrote:
>
>
> On Tue, Aug 13, 2019 at 2:48 PM Thilini Shanika wrote:
>
>> Even though OAS 2.0 support is deprecated, we should carefully handle the
>> use cases of OAS 2.0 supported APIs which have been migrated from previous
>> versions. In that
Hi all,
After we decided to go ahead with the import-export approach, we decided to
move the existing api-import-export APIs to Admin REST APIs (similar to
current application-import-export APIs). So the Admin REST API will have
the following two new resources.
*GET
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
On Wed, Aug 7, 2019 at 2:23 PM Tharindu Bandara wrote:
> Hi all,
>
> Find the best approach to maintain the archetypes (in a single repo or
>> inside the feature repo).
>
>
I didn't understand what do we meant by feature repo here. Still it is
going to be single repo right?
When we created the
Even though OAS 2.0 support is deprecated, we should carefully handle the
use cases of OAS 2.0 supported APIs which have been migrated from previous
versions. In that case, still, we have to maintain the current
implementation(Both in UI and backend) to handle functionalities of two
versions.
On Tue, Aug 13, 2019 at 6:06 PM Thilini Shanika wrote:
> Shouldn't we add error handling for unauthorized/forbidden API(Role
> restricted) comment retrievals/deletions
>
+1
Also please find a couple of inline comments:
>
> On Tue, Aug 13, 2019 at 5:10 PM Kavishka Fernando
> wrote:
>
>> Hi
On Tue, Aug 13, 2019 at 2:48 PM Thilini Shanika wrote:
> Even though OAS 2.0 support is deprecated, we should carefully handle the
> use cases of OAS 2.0 supported APIs which have been migrated from previous
> versions. In that case, still, we have to maintain the current
> implementation(Both
Shouldn't we add error handling for unauthorized/forbidden API(Role
restricted) comment retrievals/deletions
On Tue, Aug 13, 2019 at 5:10 PM Kavishka Fernando wrote:
> Hi all,
>
> We are planning on creating the comments feature for the Store in APIM 3.0
> similar to the comments feature and
Hi All,
I’m currently working on the “SAML Federated IdP Initiated Logout” feature.
In the Identity server implementation, we have the support for SAML2 SP
initiated logout for federated IdPs and with this feature, we will have the
capability to handle federated IdP initiated logout requests as
