Hi Sajeewa, Thanks for the feedback , yes we too have the visibility current domain only , but this is controlled by role. That means if role is "internal/everyone" ,then visibility is for current domain (users who can log in to that domain) .
Restricted by roles -> internal/everyone(current domain only) Thanks On Tue, Nov 24, 2015 at 7:57 AM, Sanjeewa Malalgoda <[email protected]> wrote: > @Jena, > Please refer comment inline. > > On Mon, Nov 23, 2015 at 10:18 PM, Jenananthan Yogendran < > [email protected]> wrote: > >> Hi All, >> >> We have started to working on the following feature as in api >> manager[1] >> >> - *Public and tenant stores* >> >> In multitenant deployment access to http://<ip>:9443/store will >> take the user to public store. In the public store (store of stores) user >> can find the links to all available tenant stores. >> >> - *Managing subscriptions among multiple tenants* >> >> Web app creator can control on who can subscribe to the webapp based >> on following options. >> >> * i) Available to current tenant only:* Web apps can be >> subscribed by users in the current tenant domain only (tenant domain of >> wepapp creator creator) >> * ii)Available to all the tenants:* The webapp can be >> subscribed by all the tenants in the deployment >> * iii)Available to specific tenants:* The webapp can be >> subscribed to by specific tenants who are mentioned(while creating the >> webapp) and the current tenant. >> >> Creator can select above options when app is created. Above three >> subscription options have relationship with webapp visibility as follow. >> >> a. if web app is created with 'allow anonymous access" option >> then no subscription needed. in that case all subscription options are >> hidden to creator. >> b. if web app visibility is restricted to role , then only >> subscription option "available to current tenant only' will be available. >> c. if weapp visibility is public , then all 3 subscription >> options will be available to choose while create the webapp >> > Other visibility option would be current domain only. Then subscription > also should available for current tenant only > > I think visibility should come first and then based on visibility we > should be able to select subscription availability. > Please refer following relationship and check that is how mapping works. > In APIM also we use similar pattern but here only change would be having > anonymous access. > > > > Thanks, > sanjeewa. > >> >> >> >> - *Publishing APIs to multiple tenant stores* >> >> Publisher will be allowed to publish the webapp to external >> stores(other tenant stores) as advertised app . when user in the external >> store clicks the advertised webapp it will redirect the user to >> original store where webapp is created. User can then >> subscribe to that app in the original store. >> >> In order to push to external stores, external store details >> should be configured in registry. Each tenant will have >> *external-app-stores.xml*( >> /_system/governance/apimgt/externalstores/external-api-stores.xml ) >> where external store details will be configured. Once >> webapp is published to publisher's tenant store, in the overview >> section of webapp , all configured external stores will be displayed. >> From there Publisher can >> select the external stores and publish to them. >> >> Please share your thoughts. >> >> >> [1] >> http://wso2.com/library/articles/2015/10/article-multitenant-api-management-with-wso2-api-manager/ >> >> >> >> -- >> Jenananthan Yogendran >> *Software Engineer,* >> *WSO2 inc., http://wso2.com <http://wso2.com>* >> >> > > > -- > > *Sanjeewa Malalgoda* > WSO2 Inc. > Mobile : +94713068779 > > <http://sanjeewamalalgoda.blogspot.com/>blog > :http://sanjeewamalalgoda.blogspot.com/ > <http://sanjeewamalalgoda.blogspot.com/> > > > -- Jenananthan Yogendran *Software Engineer,* *WSO2 inc., http://wso2.com <http://wso2.com>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
