Hi Chathura,
The approach you mentioned can be broken for two incidents mentioned below.
1. Remove a role from a user
2. Remove a role from an application
If I explained first case,
Let's suppose *application1* has restricted to *role1* and *user1* has
*role1*. User will be able to see the
On Fri, Mar 4, 2016 at 11:38 AM, Pirinthapan Mahendran wrote:
> Hi Imesh and Lakmal,
>
> Thanks for the replies. Since the generated hash value is sufficient, we
> are going with that solution.
>
+1 It might be better to add labels to the services including their
metadata
Hi Imesh and Lakmal,
Thanks for the replies. Since the generated hash value is sufficient, we
are going with that solution.
Thanks,
Pirinthapan.
Mahendran Pirinthapan
Software Engineer | WSO2 Inc.
Mobile +94772378732.
On Fri, Mar 4, 2016 at 11:13 AM, Lakmal Warusawithana
On Fri, Mar 4, 2016 at 9:33 AM, Lakmal Warusawithana
wrote:
>
>
> On Thu, Mar 3, 2016 at 9:42 PM, Pirinthapan Mahendran <
> pirintha...@wso2.com> wrote:
>
>> Hi all,
>>
>> In AppCloud, when deploying application in Kubernetes we are using the
>> following pattern as the service
On Thu, Mar 3, 2016 at 9:42 PM, Pirinthapan Mahendran
wrote:
> Hi all,
>
> In AppCloud, when deploying application in Kubernetes we are using the
> following pattern as the service name.
>
> *--*
>
> We are using the above pattern because a particular Application can be
>
Hi,
Are we using the same handler we publish data to DAS (AFAIU the events go
through CEP before publishing to DAS)?
If so I have a small doubt if we can cover the following scenario as the
synapse response handlers are executed before the outSequence of the API.
1. Backend returns an invalid
+1 for API Availability Dashboard.
On Thu, Mar 3, 2016 at 10:03 PM, Janaka Ranabahu wrote:
> Hi Maheshakya,
>
> On Thu, Mar 3, 2016 at 4:30 PM, Maheshakya Wijewardena <
> mahesha...@wso2.com> wrote:
>
>> Hi,
>>
>> Due to the potential security issues and complexity issues arose
Hi Pirinthapan,
We had the same problem in Stratos when creating K8S services. The way we
resolved that is using a sequence number and a prefix [1]:
*"service-"*
[1]
Hi Maheshakya,
On Thu, Mar 3, 2016 at 4:30 PM, Maheshakya Wijewardena
wrote:
> Hi,
>
> Due to the potential security issues and complexity issues arose in the
> discussions among APIM analytics team members, we have decided to get rid
> of the separate Java client for API
Hi all,
In AppCloud, when deploying application in Kubernetes we are using the
following pattern as the service name.
*--*
We are using the above pattern because a particular Application can be
identified by Application Name and Version within a tenant.
But Kubernetes limits the number of
Can we profile and check why there is a drop in performance in high
concurrency?
On Wed, Mar 2, 2016 at 2:51 PM, Nathasha Naranpanawa
wrote:
> Hi,
>
> As initially planned, the feature was implemented to collect web
> application statistics and publish them to DAS.
>
> Given
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20160303T103000Z
DTEND:20160303T113000Z
DTSTAMP:20160303T091900Z
ORGANIZER;CN=Nadeeshani Pathirennehelage:mailto:nadeesha...@wso2.com
Hi Sameera,
I came across a the topic of exception handling in functional interfaces
when going through the book 'Java 8 for the Really Impatient - Cay S.
Horstmann' which was recommended by my mentor Azeez.
The book however says that what is suggested is a solution but not a
complete fix.
The
13 matches
Mail list logo