Re: [Architecture] OAS 3 as default API definition

On Mon, Aug 12, 2019 at 10:53 AM Rukshan Premathunga wrote: > Hi All, > > ATM generated API definition is in swagger 2. Can we make it OAS 3 for the > new APIs? > Yes, we can change the default version of a newly created API to OAS 3.0.0. However, the API creator is allowed to pick the OAS

[Architecture] OAS 3 as default API definition

Hi All, ATM generated API definition is in swagger 2. Can we make it OAS 3 for the new APIs? When new API is created from an OAS 2 or 3, we can create from the same imported version. Existing API also can be kept as an existing version. Thanks and Regards -- Rukshan C. Premathunga | Associate

Re: [Architecture] OAS 3 as default API definition

On Mon, Aug 12, 2019 at 10:53 AM Rukshan Premathunga wrote: > Hi All, > > ATM generated API definition is in swagger 2. Can we make it OAS 3 for the > new APIs? > +1 to go with v3 as we are releasing a major version for APIM. > Thank you! -- *Pubudu Gunatilaka* | Associate Technical Lead |

Re: [Architecture] OAS 3 as default API definition

On Mon, Aug 12, 2019 at 11:16 AM Thilini Shanika wrote: > > > On Mon, Aug 12, 2019 at 10:53 AM Rukshan Premathunga > wrote: > >> Hi All, >> >> ATM generated API definition is in swagger 2. Can we make it OAS 3 for >> the new APIs? >> > Yes, we can change the default version of a newly created

Re: [Architecture] Force Retry Mechanism per Step in Adaptive Authentication

Thanks for the clarification Vihanga. So this is a kind of "force" authentication where the forcing happens within the context of the same authentication request rather than across different authentication requests in the same session. I also can see that It is a valid requirement. As well as it