Jira:
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
Related Jiras: Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key POLICY-2112 Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key POLICY-3170 Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key POLICY-3187 Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key POLICY-3188
Background: Support Policy Updates between PAP and the PDPs
Description: As part of the work in POLICY-2112 - it was decided that PAP would be enhanced to send two additional lists of delta policies (policesToBeDeployed & policiesToBeUndeployed) to the PDPs. Sending these lists of delta policies, eliminates the need for the PDPs to filter through a full list of policies sent from PAP in order to determine what policies need to be deployed or undeployed. The PAP component now does this work for the PDPs. This means that the PDPs need to be modified to handle these delta policy lists to remove the need to filter through the entire list.
...
XACML-PDP has yet to be modified to handle the delta policies.
Info |
---|
Maybe below we can add some proposed solutions to this below. |
...
1. Add an additional check in PAP to check that the delta policies are a subset of the full list of policies.
2.
3.