Re: [Architecture] Dashboard Component Permission Model

2017-01-19 Thread Thanuja Jayasinghe
Hi Johann/Napagoda, KasunG is currently working on removing user.core components from the carbon-security repo. So we will have carbon-security m3 release before the IS 6.0.0 m1 release. Thanks, Thanuja On Fri, Jan 20, 2017 at 9:58 AM, Johann Nallathamby wrote: > > > On Mon,

Re: [Architecture] Dashboard Component Permission Model

2017-01-19 Thread Johann Nallathamby
On Mon, Jan 9, 2017 at 2:21 PM, Thanuja Jayasinghe wrote: > > > On Mon, Jan 9, 2017 at 1:34 PM, SajithAR Ariyarathna > wrote: > >> Currently, we are in the process of refactoring the carbon-security >>> source and hope to release a 1.0.0-m3 soon. With this

Re: [Architecture] Dashboard Component Permission Model

2017-01-19 Thread Chandana Napagoda
HI Thanuja, When are you guys expecting to release carbon-security 1.0.0-m3? Regards, Chandana On Mon, Jan 9, 2017 at 2:21 PM, Thanuja Jayasinghe wrote: > > > On Mon, Jan 9, 2017 at 1:34 PM, SajithAR Ariyarathna > wrote: > >> Currently, we are in the

Re: [Architecture] Dashboard Component Permission Model

2017-01-09 Thread Thanuja Jayasinghe
On Mon, Jan 9, 2017 at 1:34 PM, SajithAR Ariyarathna wrote: > Currently, we are in the process of refactoring the carbon-security source >> and hope to release a 1.0.0-m3 soon. With this release, CAAS User >> implementation will only provide authorization functionalities. In

Re: [Architecture] Dashboard Component Permission Model

2017-01-09 Thread SajithAR Ariyarathna
> > Currently, we are in the process of refactoring the carbon-security source > and hope to release a 1.0.0-m3 soon. With this release, CAAS User > implementation will only provide authorization functionalities. In order to > consume identity store related functionalities, you need to use the

Re: [Architecture] Dashboard Component Permission Model

2017-01-08 Thread Thanuja Jayasinghe
Hi Sajith, Currently, we are in the process of refactoring the carbon-security source and hope to release a 1.0.0-m3 soon. With this release, CAAS User implementation will only provide authorization functionalities. In order to consume identity store related functionalities, you need to use the

Re: [Architecture] Dashboard Component Permission Model

2017-01-08 Thread SajithAR Ariyarathna
Hi Johann, Once you login using CAAS (carbon authentication and authorization service) > components you will get a CAAS User object [1]. This User object is a proxy > object which can be used to call all the underlying identity store and > authorization store methods. Ideally you will store this

Re: [Architecture] Dashboard Component Permission Model

2017-01-04 Thread Dilan Udara Ariyaratne
Hi Tania, Are we going to keep one dashboard permission or multiple ? The reason that I am asking this is if we can allow multiple, we can separate out access for critical functions like dashboard view, edit and manage via those permissions. Also, have you looked into the scenario of restricting

Re: [Architecture] Dashboard Component Permission Model

2017-01-03 Thread Nipuna Chandradasa
[+adding Sajith] Please find the my questions and suggestions in line > >>> Based on the above model we have following questions. >>> 1. How can we call the isAuthorized method from dashboard component ? >>> >> Isn't this isAuthorized method should be exposed through UUF as dashboard

[Architecture] Dashboard Component Permission Model

2017-01-03 Thread Tanya Madurapperuma
Hi IS Team and all, Purpose of this mail is to discuss about $ Subject. There are two main artifact types associated with the dashboard component; Dashboards and Widgets. *Widgets* According to the current implementation a widget can be an UUF fragment or an UUF component. So the plan is to