On Dec 6, 2016 3:19 AM, "Prabath Siriwardana" wrote:
On Thu, Dec 1, 2016 at 12:08 AM, Senthalan Kanagalingam
wrote:
> When moving XACML from C4 to C5, we have concerned following key aspect
> to change and improve.
>
> 1. Remove multi tenancy from
On Thu, Dec 1, 2016 at 12:08 AM, Senthalan Kanagalingam
wrote:
> When moving XACML from C4 to C5, we have concerned following key aspect
> to change and improve.
>
> 1. Remove multi tenancy from entitlement engine.
>
> In C4, we have tightly coupled with the multi tenancy.
Hi Sidath,
Thank you for your feedback. Yes, we can use cluster communication for
database.
But we are planned to use file based storage to store the polices. If all
the nodes in the cluster use one directory, then their will be no need for
notifying other nodes about the policy change. Because
When moving XACML from C4 to C5, we have concerned following key aspect to
change and improve.
1. Remove multi tenancy from entitlement engine.
In C4, we have tightly coupled with the multi tenancy. So in order to
remove that, we refactored the entitlement engine and caching level. But in