Re: [Architecture] New feature to be included in the category xml of composite repository

Hello Viraj, This feature is to enable cloud connectivity from developer studio. This code was initially in the APIM product tool. Since it could be required by other plugins in future we moved it to a separate feature so that other product plugins can access it from kernel without having to

Re: [Architecture] New feature to be included in the category xml of composite repository

Hi Awanthika, Noted. But why does the feature id contain "cloud" name in it for registry bundles. Thanks, Viraj. On Thu, Apr 28, 2016 at 8:05 AM, Awanthika Senarath wrote: > Hi, > > Please note $subject as a requirement for registry bundle to be resolved. > I

[Architecture] WSO2 API Manager 2.0.0-ALPHA Released!

*WSO2 API Manager 2.0.0-ALPHA Released!* WSO2 API Manager team is pleased to announce WSO2 API Manager 2.0.0-ALPHA release. Download distribution here . This release comes with following new features, bug fixes and

[Architecture] [C5] [Hamming] JNDI Support in WSO2 Carbon 5.0.0

Hi All, We've recently released the *alpha* version of the Carbon JNDI implementation [1]. This module provides following features to C5 based products. - In-memory JNDI Context implementation which supports "java:" URL scheme. - This implementation is based on the Apache Tomcat's JNDI

[Architecture] New feature to be included in the category xml of composite repository

Hi, Please note $subject as a requirement for registry bundle to be resolved. I have added this and committed to the master branch of ESB tooling. Add this to any other release branches you already have created. [commit id : 0b3b5438e831eb1c54e8fdf2bd81cbae4745e3e7] Regards, Awanthika

[Architecture] Implementing proper security model for dashboard server

*Requirement:* *When dashboard retrieving data from some REST APIs which are secured, we do require proper security model in place in order to identify who can access this dashboard and at which level should it be done. In addition,how can dashboard be going to communicate with respective REST API

[Architecture] WSO2 Carbon JNDI 1.0.0-Alpha Released

WSO2 Carbon JNDI 1.0.0-Alpha Released ​ The Carbon team is pleased to announce the release of Carbon JNDI 1.0.0-Alpha. Listed below are the features introduced with this release. New Features - - OSGi URL scheme support that allows JNDI based applications to access services in the

Re: [Architecture] RESTFul API for App Manager - Design discussion

Sanjeewa (or Prabath) may have guidance on this... Best regards, Frank 2016-04-27 11:11 GMT+02:00 Thilini Shanika : > + Frank > > On Wed, Apr 27, 2016 at 2:36 PM, Thilini Shanika > wrote: > >> Hi, >> >> We have a little concern regarding the permission

Re: [Architecture] RESTFul API for App Manager - Design discussion

+ Frank On Wed, Apr 27, 2016 at 2:36 PM, Thilini Shanika wrote: > Hi, > > We have a little concern regarding the permission check in OAuth secured > APIs in APPM. > > Currently, all the available APIs are attached with relevant OAuth 2 > scopes, but there are some cases where

Re: [Architecture] RESTFul API for App Manager - Design discussion

Hi, We have a little concern regarding the permission check in OAuth secured APIs in APPM. Currently, all the available APIs are attached with relevant OAuth 2 scopes, but there are some cases where we cannot manage permissions using scopes only. For example, in application lifecycle change

Re: [Architecture] [DS]Embeddable gadgets feature for Dashboard Server

Hi, Thanks for your suggestion. I will look into it. Thanks. Regards, Megala On Wed, Apr 27, 2016 at 12:16 PM, Sriskandarajah Suhothayan wrote: > Hi Megala > > I think its not necessary to communicate to DS if we are to do gadget to > gadget communication, but we have to

Re: [Architecture] API Manager Artifact Synchronization on Containerized Platforms

On Wed, Apr 27, 2016 at 12:09 PM, Imesh Gunaratne wrote: > Hi Srinath, > > On Wed, Apr 27, 2016 at 11:52 AM, Srinath Perera wrote: > >> Hi Imesh, >> >> Publishing to both gateways is not good because things fall apart when a >> one publication failed. Then a

Re: [Architecture] API Manager Artifact Synchronization on Containerized Platforms

Just to add another option we evaluated: *Rolling Updates on Kubernetes* - Again this is only available on Kubernetes at the moment and not supported on Mesos. - The idea in this is to build a new gateway Docker image on each API change and execute a rollout via Kubernetes. - This process

Re: [Architecture] [DS]Embeddable gadgets feature for Dashboard Server

Hi Megala I think its not necessary to communicate to DS if we are to do gadget to gadget communication, but we have to provide a js library that the web page developer need to embed in order to get the pub-sub working. Via this library we can do the pub-sub locally within that page, and who can

Re: [Architecture] API Manager Artifact Synchronization on Containerized Platforms

Hi Srinath, On Wed, Apr 27, 2016 at 11:52 AM, Srinath Perera wrote: > Hi Imesh, > > Publishing to both gateways is not good because things fall apart when a > one publication failed. Then a one node will be out of sync and will > continue to be out of sync. > Indeed, that's

Re: [Architecture] API Manager Artifact Synchronization on Containerized Platforms

Hi Imesh, Publishing to both gateways is not good because things fall apart when a one publication failed. Then a one node will be out of sync and will continue to be out of sync. Also in C5, we are dropping depsync, and ask users to use rsync ( or some other method like NSF). Can't we use

Re: [Architecture] Best way to generate client id and client secret

Hi Dilshan, Thanks for the info. I will try to follow the same way which EMM does in clustered setup. On Wed, Apr 27, 2016 at 11:40 AM, Dilshan Edirisuriya wrote: > "If we know DCR endpoint on DS side we can create an application and > generate client id and secret

Re: [Architecture] Best way to generate client id and client secret

"If we know DCR endpoint on DS side we can create an application and generate client id and secret against created application. " Which means it needs to hit IOT nodes deployed rather than invoking IS only for this particular scenario. What needs to happen is this DCR part needs to moved into