,
Chamod.
--
*Chamod Samarajeewa*
Software Engineer - WSO2
Email - cha...@wso2.com
Mobile - +94710397382
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
b.com/wso2/product-apim/issues/6804
Best Regards.
--
Chamod Samarajeewa | Software Engineer | WSO2 Inc.
(m) +94710397382 | Email: cha...@wso2.com
GET INTEGRATION AGILE
Integration Agility for Digitally Driven Business
___
Architecture mailing list
Archite
che entry.
On Fri, Jun 28, 2019 at 11:54 AM Fazlan Nazeem wrote:
> Hi Chamod,
>
> On Fri, Jun 28, 2019 at 10:48 AM Chamod Samarajeewa
> wrote:
>
>> Hi Harsha,
>>
>> @Chamod Samarajeewa Are we also going to implement the
>>> revocation support as
Hi Harsha,
@Chamod Samarajeewa Are we also going to implement the
> revocation support as well as we already have the backend implementation?
Yes, we will.
Best regards.
On Fri, Jun 28, 2019 at 10:44 AM Harsha Kumara wrote:
> @Chamod Samarajeewa Are we also going to imp
lue and the key will be the "jti" value
(Unique identifier of the token) of the token.
The swagger stored in the gateway as a local entry will be used to
- retrieve the missing information in the payload of JWT token such as
"API tier"
- retrieve scopes bound to
om header containing the
client id which requires a lesser logical change at their code level. Even
this option will arise the need for dynamic headers to support
multi-tenants as well which is a considerable change.
Best regards,
Chamod.
On Fri, Mar 8, 2019 at 2:33 PM Chamod Samarajeewa wrote:
> Ar
>
> Are we caching the decision?
>
Yes. We are hoping to use a caching mechanism.
On Fri, Mar 8, 2019 at 2:29 PM Harsha Kumara wrote:
>
>
> On Fri, Mar 8, 2019 at 3:56 AM Chamod Samarajeewa wrote:
>
>> Hi Harsha,
>>
>> In the current implementation,
wrote:
> @Chamod Samarajeewa can you share current
> implementation details? Is you basic authentication handler, I assume you
> calling token endpoint with hard coded consumer key and password. We should
> be able to support Johann's suggestion with Option 1.
>
> On Fri, Mar
-- Forwarded message -
From: Chamod Samarajeewa
Date: Tue, Mar 5, 2019 at 4:35 PM
Subject: Re: Basic Authentication for APIM Gateway
To: Nadeesha Gamage
Cc: Harsha Kumara , , Nuwan Dias <
nuw...@wso2.com>, APIM Team
Hi Nadeesha,
How will this impact stat
ethod and resource path both in order to
> uniquely identify the resource.
>
> On Tue, Feb 26, 2019 at 11:13 AM Chathura Ekanayake
> wrote:
>
>> @Chamod Samarajeewa if we send username, password and
>> resource to the KM, can't we get the required result from a single
without calling the Key Manager.
I would really appreciate any feedback. Thank you.
Best regards,
Chamod.
On Sat, Feb 16, 2019 at 9:10 PM Chamod Samarajeewa wrote:
> Hi Harsha,
>
> Yes, the user can expose API either OAuth, Basic auth or even both with
> this implementation. Thank y
chanism for this.
>
> Since we do have mutual authentication as a security scheme, check the
> best way of providing the basic authentication
>
> Thanks,
> Harsha
>
> On Fri, Feb 15, 2019 at 9:07 PM Chamod Samarajeewa
> wrote:
>
>> Adding architecture@wso2
> best way of providing the basic authentication
>
> Thanks,
> Harsha
>
> On Fri, Feb 15, 2019 at 4:59 PM Chamod Samarajeewa
> wrote:
>
>> Adding architect...@wso2.com.
>>
>>
>> -- Forwarded message -
>> From: Nuwan Dias
>> Date: Fri
13 matches
Mail list logo
