Hi Dilshan, What we are going to do is stop implementation for a while and analyse all use cases and requirements. After that we will propose technical limitations, suggestions, improvements for existing user module.
On Mon, May 5, 2014 at 11:43 PM, Dilshan Edirisuriya <[email protected]>wrote: > Hi Chan, > > What are the EMM specific cases we need to handle? In that case does this > inherit behaviors of generic user module or will it be a different one > which only have the functions specific to EMM? > > Regards, > > Dilshan > > > On Mon, May 5, 2014 at 10:49 PM, Chan <[email protected]> wrote: > >> >> >> >> On Mon, May 5, 2014 at 8:34 AM, Ruchira Wageesha <[email protected]>wrote: >> >>> >>> >>> >>> On Sun, May 4, 2014 at 2:58 PM, Chan <[email protected]> wrote: >>> >>>> Hi folks, >>>> I am currently working on the $subject for EMM 1.1.0 release. EMM 1.0.0 >>>> used the default jaggery carbon module and internal user and group modules >>>> to solve the UM aspect. Below are some of the issues we have - >>>> >>>> - Coupling to the email >>>> - Roles creation is ambiguous (for example not write access to the >>>> User store) >>>> - User creation (no write access to User store) >>>> - Not supporting secondary User store >>>> - XACML usage >>>> >>>> The new UserModule aims to solve the above problems. There will be a >>>> config file that has configs whether to enable internal role and user >>>> creation. If enabled and write access is not provided - we create users and >>>> roles internally. If disabled we will remove those elements from UI and >>>> disable operations from the API. The new UserModule will always pass the >>>> carbon user object [1]. All the static operations that will be used will be >>>> under the UserModule. >>>> >>> Why you need to write a new module, instead of that, can't you improve >>> the existing one? >>> >> >> We are going to improve the existing module and we are going to have >> the module mentioned to handle certain cases specific to EMM. >> >> >>> >>>> >>>> The new UserModule will remove XACML for permission. Even though we >>>> used XACML for permissions on operations in the last version (1.0.0) we >>>> didn't see a real advantage of it for the features we had. For 1.1.0 we >>>> discussed to remove XACML and use a database table to handle permissions >>>> for roles. However -we'll be incorporating XACML in the future releases >>>> (1.2.0 perhaps) and will be giving the real advantage of it (eg:- time >>>> based permissions, write your own XACML in EMM UI). >>>> >>>> Cheers~ >>>> >>>> [1] - >>>> https://github.com/wso2/jaggery-extensions/blob/master/carbon/module/scripts/user/user.js >>>> >>>> >>>> -- >>>> Chan (Dulitha Wijewantha) >>>> Software Engineer - Mobile Development >>>> WSO2Mobile >>>> Lean.Enterprise.Mobileware >>>> * ~Email [email protected] <[email protected]>* >>>> * ~Mobile +94712112165 <%2B94712112165>* >>>> * ~Website dulitha.me <http://dulitha.me>* >>>> * ~Twitter @dulitharw <https://twitter.com/dulitharw>* >>>> *~Github @dulichan <https://github.com/dulichan>* >>>> *~SO @chan <http://stackoverflow.com/users/813471/chan>* >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> >>> *Ruchira Wageesha**Associate Technical Lead* >>> *WSO2 Inc. - lean . enterprise . middleware | wso2.com >>> <http://wso2.com>* >>> >>> *email: [email protected] <[email protected]>, blog: >>> ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>, >>> mobile: +94 77 5493444 <%2B94%2077%205493444>* >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Chan (Dulitha Wijewantha) >> Software Engineer - Mobile Development >> WSO2Mobile >> Lean.Enterprise.Mobileware >> * ~Email [email protected] <[email protected]>* >> * ~Mobile +94712112165 <%2B94712112165>* >> * ~Website dulitha.me <http://dulitha.me>* >> * ~Twitter @dulitharw <https://twitter.com/dulitharw>* >> *~Github @dulichan <https://github.com/dulichan>* >> *~SO @chan <http://stackoverflow.com/users/813471/chan>* >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Dilshan Edirisuriya > Senior Software Engineer - WSO2 > Mob: + 94 777878905 > http://wso2.com/ > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Gayan Gunawardana Software Engineer; WSO2 Inc.; http://wso2.com/ Email: [email protected] Mobile: +94 (71) 8020933 Blog: http://gayanj2ee.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
