@Manu, first up, thanks for implementing this with such a short notice. Now that we've got this fully implemented, would you be able to drop a note to the thread explaining the config bits associated with enabling the required authorization levels for UI blocks?
Cheers, Prabath On Wed, Mar 25, 2015 at 5:49 PM, Prabath Abeysekera <praba...@wso2.com> wrote: > Hi Manu, Ruchira, > > Any possibility to get things rolling a little faster around this > implementation? > > Cheers, > Prabath > > On Sat, Mar 21, 2015 at 8:05 AM, Prabath Abeysekera <praba...@wso2.com> > wrote: > >> [Moving to architecture@ as this discussion belongs there] >> >> Cheers, >> Prabath >> >> On Fri, Mar 20, 2015 at 12:19 PM, Prabath Abeysekera <praba...@wso2.com> >> wrote: >> >>> >>> On Fri, Mar 20, 2015 at 9:39 AM, Manuranga Perera <m...@wso2.com> wrote: >>> >>>> +1 for ability for enable/disable visibly of a unit based on >>>> permissions. this feature is there in Carbon UI as well. will implement >>>> this. >>>> -1 for units automatically creating permissions. since in CDM, we are >>>> implementing business logic in Java, I think permission creation should >>>> also happen in Java code. ie. even if we remove the UI, app should be fully >>>> functional via the REST API. >>>> What do you think Prabath/Dulitha? >>>> >>> >>> Correct me if I'm wrong, my understanding about the "Unified UI >>> framework" is that, it's another UI framework which gives us the ability, >>> not only to organize the UI bits, but also to configure stuff like UI >>> permissions etc, just as how it's already done in "Carbon UI framework". In >>> other words, "Unified UI framework" itself should, IMO, take care of tasks >>> such as persisting/manipulating UI permissions etc and render the UIs >>> depending on the applicable authorization levels. We're all good as long as >>> we have that integrated into the framework. >>> >>> Cheers, >>> Prabath >>> >>> >>>> >>>> On Wed, Mar 18, 2015 at 9:38 PM, Dulitha Wijewantha <duli...@wso2.com> >>>> wrote: >>>> >>>>> Hi Manu, >>>>> In our current Units mechanism, we don't specify the permissions the >>>>> unit is consuming. The suggestion is to hold the permissions that a unit >>>>> is >>>>> consuming within the unit. Unified UI framework will push these >>>>> permissions >>>>> to the registry in application startup. >>>>> >>>>> We can also provide a helper form the unified UI to check if the >>>>> current user is permitted or not. WDYT? >>>>> >>>>> This is urgent for us as we are nearing, our product release. >>>>> >>>>> Cheers~ >>>>> >>>>> -- >>>>> Dulitha Wijewantha (Chan) >>>>> Software Engineer - Mobile Development >>>>> WSO2 Inc >>>>> Lean.Enterprise.Middleware >>>>> * ~Email duli...@wso2.com <duli...@wso2mobile.com>* >>>>> * ~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>* >>>>> >>>> >>>> >>>> >>>> -- >>>> With regards, >>>> *Manu*ranga Perera. >>>> >>>> phone : 071 7 70 20 50 >>>> mail : m...@wso2.com >>>> >>> >>> >>> >>> -- >>> Prabath Abeysekara >>> Associate Technical Lead, Data TG. >>> WSO2 Inc. >>> Email: praba...@wso2.com >>> Mobile: +94774171471 >>> >> >> >> >> -- >> Prabath Abeysekara >> Associate Technical Lead, Data TG. >> WSO2 Inc. >> Email: praba...@wso2.com >> Mobile: +94774171471 >> > > > > -- > Prabath Abeysekara > Associate Technical Lead, Data TG. > WSO2 Inc. > Email: praba...@wso2.com > Mobile: +94774171471 > -- Prabath Abeysekara Associate Technical Lead, Data TG. WSO2 Inc. Email: praba...@wso2.com Mobile: +94774171471
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
