Hi With the new proposal the previous "super tenant store" will be a store of "stores". If we take an example lets assume there are two tenants WSO2 and Foo, the super tenant store will just show URLs of WSO2 store and Foo Store, where users can navigate to.
When an anonymous user goes to one of these store, (s)he will only see the public APIs of that tenant. Subsequently the older super store will be replaced by a simple OOTB store, where any tenant can push APIs. its like a public store hosted somewhere, which anybody can push APIs. Regards, /Nuwan On Tue, Jul 30, 2013 at 1:08 PM, Nuwan Dias <[email protected]> wrote: > On Tue, Jul 30, 2013 at 12:45 PM, Sumedha Rubasinghe <[email protected]>wrote: > >> This discussion happened as part of *Enterprise Store* discussion. >> Participants: Nuwan, Azeez, Sanjiva, Srinath, NuwanD, Lalaji, Sanjeewa, >> Sumedha >> >> *Current Functionality:* >> 1. At the point of publishing an API, publisher can select the visibility >> scope (one of Globally visible, selected tenants, tenant only >> [private/public]). >> 2. Based on selected scope, APIs will be created with correct set of >> permission indicators in WSO2 Governance Registry >> 3. @ the point of populating a store, based on the store type APIs will >> be fetched from tenant registries >> >> *Limitations in this approach:* >> 1. Assumption of single registry for all tenants (fetching, publishing >> criteria fails with tenant partitioning) >> 2. High computational cost for populating global tenant store (also known >> as super tenant store) >> 3. API publishing is only supported for WSO2 API Store type >> 4. Tight coupling with WSO2 API Store semantics for API publishing & >> fetching >> >> *New Approach:* >> 1. At the point of publishing an API, it can also be published to >> multiple (external) stores >> 2. These stores will be defined through configuration (run time >> registration can be considered for future work, limited by lack of standard >> API for publishing API) >> >> 3. APIs will published to external stores through their APIs. This has >> several design considerations: >> - Any API store can be integrated to WSO2 API Publisher through this >> approach >> - WSO2 API Store will also be treated as an external one >> - Concept of Super Tenant Store will no longer be applicable *** >> - If an API is shared with another tenant store, it will be stored in >> that tenant's storage (if sharing is removed, relevant removal should >> follow) >> >> 4. *** When navigated to http://<IP/Domain>/store (formally known as >> Super tenant's store), it will show a list of tenant store URLs only >> > > Right now we do not allow a tenant user (when logged in) to view other > tenant stores. You can view other tenant stores if you are a super tenant > user or when you are in anonymous mode (not logged in). If this behavior is > to remain as it is, what is the purpose of displaying other tenant's store > URLs on the /store? > > 5. This concept should be supported in WSO2 Generic Store as well >> > >> Feedback welcome. >> > > Thanks, > NuwanD. > >> >> -- >> /sumedha >> b : bit.ly/sumedha >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Nuwan Dias > > Senior Software Engineer - WSO2, Inc. http://wso2.com > email : [email protected] > Phone : +94 777 775 729 > -- *Thanks & Regards, Nuwan Bandara Technical Lead; **WSO2 Inc. * *lean . enterprise . middleware | http://wso2.com * *blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 9629 * <http://www.nuwanbando.com/>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
