-1. This may cause unnecessary security issues if people do not want multitenancy & forget to remove this before production deployments. Now they have to remember to change the admin password. If we introduce a tenant, they have to remember to change that tenant admin's password & remove the tenant as well. A better approach is to create a tenant during integration tests, and then run tests against that tenant. If time permits today, I will try to implement something that shows how this can be done.
On Sat, Jun 2, 2012 at 9:15 AM, Supun Malinga <[email protected]> wrote: > Hi, > > How about $subject. This would ease development efforts and also users can > try out the stratos aspects OOTB. > WDYT? > > thanks, > -- > Supun Malinga, > > Software Engineer, > WSO2 Inc. > http://wso2.com > http://wso2.org > email - [email protected] <[email protected]> > mobile - 071 56 91 321 > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
