Hi All,
Please find below, Notes from yesterday's meeting.
Publisher
- Users need to be able to create an application, publish to public
store.
- This concept is there in AM, but is not exactly the same as the
requirement, there is the concept of "public store" in a tenant domain
perspective. Said public store has all the public APIs for that
particular
tenant domain. What is required here is that we come up with a certain
super store that holds all public APIs from all tenant domains.
- Visibility and Subscribability model will also need to be revised
to accommodate this requirement.
- Role Mapping between multiple user stores. (E.g. Administrative user
of Organization A, has the same level of access to resources in App
Manager, as users having the admin role in Organization B)
- *IS already has this feature, with its latest release (5.0.0). We
need to adopt same in App Manager*
Store
- Make APIs visible/subscribable to users having a certain role.
- *Role based filtering for assets need to be implemented in
Enterprise Store front.*
- *We can use the Federated Identity feature in IS, to allow
subscriptions to APIs not owned by a particular user*
GW
- According to the current implementation, how the Gateway keeps track
of IDP authenticated users is via, a cached Cookie. This model needs to be
restructured so that Multi-Tenancy is supported.
Miscellaneous
- Tenant aware workflows
- The workflow configuration, as of now is picked off the
app-manager.xml, this needs to be changed so that each tenant
can maintain
a separate configuration file for its activities in the registry. *The
necessary changes have already been done with the latest release of API
Manager (1.7.0), changes needs to be ported to App Manager.*
- M/T enabled Workflow configuration UI
- *The UI changes done in API Manager 1.7.0 to handle tenant workflow
configurations needs to be ported to App Manager.*
Apart from above, the possibility of applications published in APP Manager
having APIs within them that needs to be governed by API Manager was also
discussed. In order to handle such scenarios, API Manager and App Manager
will need to be merged as one product.
Thanks and Regards,
Ruwan Yatawara
Software Engineer,
WSO2 Inc.
lean . enterprise . middleware
email : [email protected]
mobile : +94 77 9110413
blog : http://thoughts.ruwan-ace.com/
www: :http://wso2.com
On Thu, Apr 10, 2014 at 6:39 AM, Dinusha Senanayaka <[email protected]>wrote:
>
>
>
> On Thu, Apr 10, 2014 at 6:24 AM, Sumedha Rubasinghe <[email protected]>wrote:
>
>> Dinusha,
>> Let's schedule a discussion today with Azeez, Shankar & Prabath.
>>
> sent a calender invitation @2-3pm.
>
>>
>>
>> On Thu, Apr 10, 2014 at 6:18 AM, Dinusha Senanayaka <[email protected]>wrote:
>>
>>> Hi,
>>>
>>> We have identified following ares to be cover with $subject.
>>> Additionally we need to define features that could be useful for users,
>>> like assets sharing across tenants etc. Thoughts ?
>>>
>>>
>>>
>>> Data Isolation
>>>
>>> Execution Isolation
>>>
>>> Publisher
>>>
>>> -
>>>
>>> Assets need to saved in to correct tenant space.
>>> -
>>>
>>> Save into tenant registry (Comes with ES)
>>> -
>>>
>>> Save into AppM DB (Need to check whether artifacts get saved with
>>> tenant ID)
>>> -
>>>
>>> Need to check resources associated with asset get saved in correct
>>> tenant registry space (Resources like Documents)
>>>
>>>
>>>
>>> -
>>>
>>> When publishing, synapse config need to deploy in correct tenant
>>> space.
>>> -
>>>
>>> Application publish workflow extension handling for tenant.
>>>
>>> Store
>>>
>>> -
>>>
>>> Logged in user should see only the assets published by his tenant
>>> domain (Comes with ES)
>>> -
>>>
>>> Need to check associated resource loading (Documents)
>>> -
>>>
>>> Recently added assets, tags
>>> -
>>>
>>> Subscription handling
>>>
>>>
>>>
>>> Gateway
>>>
>>>
>>> -
>>>
>>> Tenant aware invocations.
>>> -
>>>
>>> SSO handling (currently cookie saved in cache)
>>>
>>>
>>>
>>>
>>> Regards,
>>> Dinusha.
>>>
>>> --
>>> Dinusha Dilrukshi
>>> Senior Software Engineer
>>> WSO2 Inc.: http://wso2.com/
>>> Mobile: +94725255071
>>> Blog: http://dinushasblog.blogspot.com/
>>>
>>
>>
>>
>> --
>> /sumedha
>> b : bit.ly/sumedha
>>
>
>
>
> --
> Dinusha Dilrukshi
> Senior Software Engineer
> WSO2 Inc.: http://wso2.com/
> Mobile: +94725255071
> Blog: http://dinushasblog.blogspot.com/
>
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
