Re: [Architecture] [Dev][Vote] Release of WSO2 API Microgateway 3.2.0 RC2

2020-08-25 Thread Amali Matharaarachchi
Hi all, Tested the following scenarios: - Multiple JWT issuers - Mutual SSL authentication - API Key STS - Auth combinations - Analytics file writing and file uploading/publishing No blockers found. [+] Stable - Go ahead and release Thanks On Tue, Aug 25, 2020 at 8:15 PM Shehani

Re: [Architecture] [Dev] [Vote] Release of WSO2 API Microgateway 3.1.0 RC2

2020-03-25 Thread Amali Matharaarachchi
Hi all, I tested the following. - Binary Quick start guide - API Key STS - API Key authentication - Multiple JWT issuers - Default security schemes No issues found. *[+] Stable - Go ahead and release* On Wed, Mar 25, 2020 at 2:22 PM Rajith Roshan wrote: > Hi all, > Tested the

[Architecture] API Key support for WSO2 API Microgateway

2020-01-28 Thread Amali Matharaarachchi
Hi all, The WSO2 API Microgateway is now supporting API Key authentication. It also provides an STS for issuing API Keys. API Key authentication in WSO2 API Microgateway is a simple HTTP authentication scheme that accepts a valid self-contained token issued for accessing APIs [1]. You can find

Re: [Architecture] [Microgateway] JWT Issuer feature

2020-01-08 Thread Amali Matharaarachchi
[apikey.issuer.apis.1] name="Swagger Petstore New" basepath="pizzashack" versions="1.0.0, v1, v2" [apikey.issuer.apis.2] name="MyAPI" basepath="myapi" versions="*" Please let me know any suggestions or concerns. Thanks. On Fri, Jan 3, 2020 at 5

Re: [Architecture] [Microgateway] JWT Issuer feature

2020-01-03 Thread Amali Matharaarachchi
basic authorization. API Keys with subscribed API list will be issued for the above APIs. Please let me know any suggestions or concerns regarding the above configuration. Thanks, Amali On Mon, Dec 16, 2019 at 3:36 PM Amali Matharaarachchi wrote: > Nuwan, Rajith and I had an internal discussion on

Re: [Architecture] [Microgateway] JWT Issuer feature

2019-12-16 Thread Amali Matharaarachchi
https://localhost:9095/apikey - Provide a new config file to configure users and apis for STS. 5. User authentication is not needed for api invocation with the API key. We appreciate your thoughts on this. Thanks. On Mon, Dec 16, 2019 at 10:16 AM Amali Matharaarachchi wrote: > API Key w

Re: [Architecture] [Microgateway] JWT Issuer feature

2019-12-15 Thread Amali Matharaarachchi
Fri, Dec 13, 2019 at 11:34 AM Amali Matharaarachchi > wrote: > >> Hi all, >> >> I have several concerns regarding the current approach. I highly >> appreciate your suggestions. @Rajith Roshan Please >> add if I have missed out anything. >> >> 1. How

Re: [Architecture] [Microgateway] JWT Issuer feature

2019-12-12 Thread Amali Matharaarachchi
validating the user with its own user configurations. Hence ideally, the user configurations should be identical in gateways. Kindly let me know your thoughts. Thank you. On Mon, Dec 9, 2019 at 5:06 PM Amali Matharaarachchi wrote: > Hi, > If someone used this API Key in authorizati

Re: [Architecture] [Microgateway] JWT Issuer feature

2019-12-09 Thread Amali Matharaarachchi
ot;Invalid JWT token" or similar error as expected. >> >> On Mon, Dec 9, 2019 at 4:34 PM Fazlan Nazeem wrote: >> >>> We should be identifying both separately already in the synapse gateway. >>> Have you checked how it has been done and stick to the same if

Re: [Architecture] [Microgateway] JWT Issuer feature

2019-12-09 Thread Amali Matharaarachchi
the token, it will be recognized as an API Key. I highly appreciate if you have any suggestions regarding this. Thanks. On Fri, Dec 6, 2019 at 3:54 PM Amali Matharaarachchi wrote: > Hi Harsha, > > Will the token endpoint is default one and provide an option to point to >> the key manager

Re: [Architecture] [Microgateway] JWT Issuer feature

2019-12-06 Thread Amali Matharaarachchi
s://github.com/wso2/product-microgateway/issues/897#issuecomment-561996404 [2] https://github.com/wso2/product-microgateway/issues/897#issuecomment-562422055 On Fri, Dec 6, 2019 at 3:03 PM Amali Matharaarachchi wrote: > Hi all, > There is a Slack Discussion[1] in #microgateway channel as well. &g

[Architecture] Fwd: [Microgateway] JWT Issuer feature

2019-12-06 Thread Amali Matharaarachchi
+architecture -- Forwarded message - From: Harsha Kumara Date: Fri, Dec 6, 2019 at 3:06 PM Subject: Re: [Microgateway] JWT Issuer feature To: Amali Matharaarachchi Cc: APIM Team , Rajith Roshan , Nuwan Dias , Praminda Jayawardana , Hasunie Adikari , Viraj Gamage Also please

Re: [Architecture] Decoupling API Manager and API Microgateway

2019-03-13 Thread Amali Matharaarachchi
43/client-registration/%7Bversion%7D/register>" >> >> +1 for this. This will minimise most of the redo work in each new > microgateway release, due to updating the mappings in the code level. > Rather than keeping two configs for the APIM version and the REST API &g

Re: [Architecture] Decoupling API Manager and API Microgateway

2019-02-28 Thread Amali Matharaarachchi
rogateway with an >> APIM version that was released after the microgateway was released. This is >> the only use case where we will not know how to derive the Rest API version >> from the respective APIM version. >> >> On Fri, Mar 1, 2019 at 10:08 AM Amali Mathara

Re: [Architecture] Decoupling API Manager and API Microgateway

2019-02-28 Thread Amali Matharaarachchi
sing to objects in the Microgateway side. Thank you On Fri, Feb 22, 2019 at 3:49 PM Amali Matharaarachchi wrote: > Adding architecture@wso2.org > > On Fri, Feb 22, 2019 at 11:08 AM Amali Matharaarachchi > wrote: > > >> Hi all, >> >> I am working o

[Architecture] Fwd: Decoupling API Manager and API Microgateway

2019-02-22 Thread Amali Matharaarachchi
Adding architecture@wso2.org On Fri, Feb 22, 2019 at 11:08 AM Amali Matharaarachchi wrote: > Hi all, > > I am working on reducing coupling between APIM and Microgateway[1]. > > > *Problem*: > > Microgateway requires the same version of the API Manager to be exec