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,
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
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
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
>
> 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
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
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
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
[+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
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
10 matches
Mail list logo