Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

2. Policy Lifecycle API CRUD Enhancements

Native policies can be supported by TOSCA policy type and policy. As for native Drools policy, since native DRL is packaged in JAR which has been deployed to nexus repo along with other dependency JARs, TOSCA policy for native DRL only needs to include the pointer for native JAR as well as necessary information being used by Drools PDP to instantiate a new controller instance with native DRL loaded into memory. Corresponding policy type should be defined and pre-loaded into policy framework so that TOSCA policy for native policy type can then be created off. As for native XACML policy, its contents are basically encoded in XML which is all XACML PDP needs to load into engine and run. Thus, TOSCA policy for native XACML only needs to include this XML content. An URL-encoded string can be created off composed XACML XML and is populated to a string property.

Below is the policy types defined to support native Drools and XACML policies.

Code Block
languageyml
titlePolicy Type for Native Drools Policy
linenumberstrue
collapsetrue


Code Block
languageyml
titlePolicy Type for Native XACML Policy
linenumberstrue
collapsetrue

Below is an example of TOSCA policy for native XACML rules

Code Block
languageyml
titleExample TOSCA Policy for Native XACML rules
linenumberstrue
collapsetrue

The native XACML rules for above TOSCA policy is:

Code Block
languageyml
titleNative XACML rules
linenumberstrue
collapsetrue

3. PAP Enhancements

PDP Engines must now register with PAP the new policy types for native policies they support in order for policies to be deployed by PAP to the PDP's. This will require an additional entry to be added into supported policy types list to indicate which native policy type each specific PDP engine can support.

...