All actions done for a tenant, better be done the super tenant of that user. Clean ins't it?
On Wed, Jul 17, 2013 at 5:44 AM, Dimuthu Leelarathne <[email protected]>wrote: > Hi, > > AF has a magic user that exist in all tenants. This magic user is used in > following scenarios. > > - appmgt jaggery app use it to authorize/authenticate to Admin services > - Jenkins use it to run system builds > - Update rxts in registry > > With the introduction of multi tenancy concept it would make all sense to > remove this magic user due to following scenarios. > > - To utilize the platform level tenant lazy loading concepts > - To use our Admin services as it is and the best example > ApplicationMgtAdmin service > > In short to be MT truly this user has to go away. > > So we will manage the existing scenarios as follows. > - To trigger system driven auto builds we will use a user specific to > gitblit and Jenkins > - Updating rxts can be done as a super tenant then within that we will > start tenant flows when updating rxts > > WDYT? > > thanks, > dimuthu > > -- > Dimuthu Leelarathne > Architect & Product Lead of App Factory > > WSO2, Inc. (http://wso2.com) > email: [email protected] > Mobile : 0773661935 > > Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
