Hi Kishanthan,
On Thu, Nov 7, 2013 at 11:09 AM, Kishanthan Thangarajah <[email protected] > wrote: > > > > On Wed, Nov 6, 2013 at 6:11 PM, Supun Malinga <[email protected]> wrote: > >> Hi All, >> >> We (Sagara, me) came up with a holistic view on the SaaS support from AS. >> As you may know there are several ways to get some SaaS features >> implemented within the platform. >> >> *Ways to enable login to SaaS applications * >> >> 1. SaaS parameter defining in web.xml with basic/form auth >> >> This is the simplest method to achieve the authentication. Can be done >> with a zero java coding. But only limited to basic/form auth. >> >> 2. Manually authenticating with tenants' user stores >> >> Here user can implement any authentication mechanism in the application >> and talk to the internal user-mgt APIs. >> >> 3. Login with API manager (/token api invocation) >> >> In this approach we can call the /token api in API Manager and get the >> oauth token in return. If we get a valid token user can be considered valid >> and the token can be used to talk to other APIs within the application. >> > > Is this something that the user has to handle him self or are planning to > provide an API for this? which does the calling of token api and return the > access token. So that the user does not have to worry about those details. > We can definitely facilitate this internally and as API everywhere integration is going on it will be more easier. But I don't feel it will be useful since users will most probably implement in their code along with the rest of the logic in the application.. thanks, > > > >> *SaaS Application supported Features * >> >> - users, roles and permissions mgt >> - authentication and authorization >> - caching >> - logging >> - resource sharing >> - configuration sharing >> >> Also we Identified two modes of providing above features within a SaaS >> application. >> *Mode 1* >> Tenant's data, configs will be kept within each tenant. >> For eg: tenant logo. Here we can store each tenant's logo in each >> tenant's registry. >> >> *Mode 2* >> Application hosting tenant can logically define seperation and keep >> configs within tenant itself. >> eg: Store all tenants' logos within hosting tenant's registry. >> >> I'm planning to properly test each of these and sample and document each >> area. >> Please let me know if I have missed any aspect/point. Looking forward to >> discuss and refine this. >> >> thanks, >> -- >> Supun Malinga, >> >> Senior Software Engineer, >> WSO2 Inc. >> http://wso2.com >> email: [email protected] <[email protected]> >> mobile: +94 (0)71 56 91 321 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Kishanthan Thangarajah* > Senior Software Engineer, > Platform Technologies Team, > WSO2, Inc. > lean.enterprise.middleware > > Mobile - +94773426635 > Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>* > Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>* > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: [email protected] <[email protected]> mobile: +94 (0)71 56 91 321
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
