Re: [Architecture] Introduce API Product concept for WSO2 API Manager

+1 to allowing subscriptions to API products only, I dont see an advantage in supporting both subscriptions to APIs and API products(it only complicates things). This will also eliminate confusion for subscribers. Yes there will be a migration effort in doing this but its worth it IMO for the

Re: [Architecture] Dynamic Detection of Broker Nodes in Cluster and Load Balancing

Hi Chamila, I'm planing to use some thing similar to DNS round robian algorithm and I can you disruptor to handle this. On Fri, Aug 26, 2016 at 9:37 PM, Chamila De Alwis wrote: > +1 to this approach, since IMO this is a great feature for the > andes-client itself to have,

Re: [Architecture] [AppM] Best practice to re-use domain objects in the gateway handlers

On Tuesday, August 23, 2016, Chathura Ekanayake wrote: > Hi Rushmin, > > Can't we maintain a cache of domain objects, may be in a data holder > instance? > Yes, using a cache with a data holder instance would be appropriate for this problem. Do we know how frequently these

Re: [Architecture] [APIM] Modifying test cases to use new REST APIs instead of old Jaggery REST APIs

Hi Praminda How was the "authorizationUrl/tokenUrl" set to the security definitions was it hardcoded or does it dynamically resolve the URL based on the setup. Let say if we want to test a distributed deployment does it pick tokenUrl may be from configs. Thanks Jo On Mon, Aug 22, 2016 at 10:34

Re: [Architecture] OpenID Connect Based SSO valve for WSO2 AS 6.0.0

Hi Abilashini, The valve approach might not be able to cater all webapp developer requirements. Especially there are certain parameters in the OIDC request which can be dynamic, changes from request to request, e.g. claims, scopes, etc. During the meeting we had we decided to provide them as