Re: [Architecture] [Greg]Optimal VM heap size for Greg 5.2 performance testing

Hi Kasun, As you mentioned, the 2GB heap gives a better throughput than 1GB heap and therefore it's good to do performance tests with 2GB heap. Since there is about 96% throughput, we may not need to do additional GC tuning. However let's enable GC logs during the performance tests and then we ca

Re: [Architecture] [Analytics][APIM] - Implement Geo location graph in Analytics

Hi All, We have come across following ways to do the above task after the Initial POC. 1. Using File type database which given by max-mind (.mmdb) and use there database readers. >From this approach we got lesser value to get the location from the above using JAX-RS service which is used to wrap

[Architecture] WSO2 App Cloud 2.0.0 Pre-Alpha Released!

WSO2 App Cloud 2.0.0 Pre-Alpha Release WSO2 App Cloud team is pleased to announce the release of version 2.0.0 Pre-Alpha of the WSO2 App Cloud. WSO2 App Cloud is a multi-tenant, elastic and self-service enterprise platform that enables hosting applications written in multiple languages on multipl

[Architecture] WSO2 Identity Server 5.2.0 Milestone 1 Released!

WSO2 Identity Server 5.2.0 Milestone 1 Released!Date: 8th March 2016The WSO2 Identity Server team is pleased to announce the 1st Milestone of WSO2 Identity Server 5.2.0. You can download this distribution from https://github.com/wso2/product-is/releases/tag/v5.2.0-m1 Following list [1] contains al

[Architecture] Fwd: OATH Authenticators for IS

+1 for separating common modules. However IMO these needs to go as two different authenticators since it provides two distinct methods to authenticate. +architecture -- Forwarded message -- From: Rajj ​common mod​ az Mohammed Date: Tue, Mar 8, 2016 at 6:56 PM Subject: OATH Authe

[Architecture] [PET] Office 365 Connector

Hi All, I have planned to develop office 365 connector using REST API[1] with the following Methods for initial version. The Office 365 APIs are REST services that provide access to high-value data from Office 365 services : Mail, calendars, contacts, people, notifications, photos, etc. Office 3

[Architecture] [AS 6.0.0] HTTP Monitoring dashboard - Why are we parsing the User-Agent header in the event builder?

Hi App Server team, According to the code in [1], the user-agent string is parsed and some of the information are extracted from the user-agent at event publishing time. Could you guys please clarify why you guys haven't published the whole user-agent string to DAS and use a UDF to extract the cor

Re: [Architecture] Have we looked at supporting "Kiosk" mode as part of the proposed "COPE" implementation?

One of the things that we need to specifically focus on is how we're going to let administrators configure this particular mode in EMM. I believe, "Kiosk" can be thought of as an extension of "Locked-down mode", in which one/limited number of applications are allowed to be enforced on the device. S

Re: [Architecture] [AS 6.0.0] HTTP Monitoring dashboard - Why are we parsing the User-Agent header in the event builder?

Hi all, The user-agent information were extracted at event publishing time mainly considering that data analyzing using scripts will be made easier at the Dashboard Server. We are going to change the current implementation by publishing the whole user-agent string considering all the performance

Re: [Architecture] [AS 6.0.0] HTTP Monitoring dashboard - Why are we parsing the User-Agent header in the event builder?

I too think its a valid concern. +1 to publish the complete header as it is. @Lochana, Please note this during HTTP Monitoring Dashboard task when you are extracting the information. Regards, Manoj *Manoj Kumara* WSO2 Inc. *| **lean. enterprise. middleware.* *Mobile:* +94 713 448188 On Wed, Mar

Re: [Architecture] Have we looked at supporting "Kiosk" mode as part of the proposed "COPE" implementation?

Cool, let's also look at the options that Shan's suggested and go for the most appropriate one!. Cheers, Prabath On Wed, Mar 9, 2016 at 9:56 AM, Inosh Perera wrote: > Hi Prabath, > > Yes, I was thinking the same. Since we are already under research for a > complete lock-down mode in Android, I

Re: [Architecture] Fwd: OATH Authenticators for IS

+1 for common module for TOTP and HOTP algorithms. IMO can we rename TOTP authenticator to Google Authenticator. SMS OTP, Email OTP and Google Authenticator can have the options TOTP and HOTP. Thanks, Kahees On Tue, Mar 8, 2016 at 7:51 PM, Malaka Silva wrote: > +1 for separating common module

Re: [Architecture] Fwd: OATH Authenticators for IS

> IMO can we rename TOTP authenticator to Google Authenticator. SMS OTP, > Email OTP and Google Authenticator can have the options TOTP and HOTP. > > +1 with kathees, these are the 3 ways to user to get token( can use yubikey also ). so we can create 3 authenticators and each authenticator have th

Re: [Architecture] Fwd: OATH Authenticators for IS

+1 for Kathees's idea. On Wed, Mar 9, 2016 at 11:54 AM, Kathees Rajendram wrote: > +1 for common module for TOTP and HOTP algorithms. > > IMO can we rename TOTP authenticator to Google Authenticator. SMS OTP, > Email OTP and Google Authenticator can have the options TOTP and HOTP. > > Thanks, >

[Architecture] Session Affinity Alternatives

We are currently using sessions and session affinity in our apps. But going forward, especially in Micro Services/Docker model does it make scene? Eg: If we bring up a new container due to high load, requests will still route to old continents due to the session. If we kill a container that is ass