-
Sub-task
-
Resolution: Won't Do
-
Medium
-
None
-
None
-
Policy Casablanca - 4, Policy Casablanca - 6
- console, pdp-x, pdp-d, and consul machine users must be pre-provisioned in AAF. These users, and appropriate roles, and permissions, should be added to the org.onap.policy.pap namespace. AAF must be pre-configured with these permissions for demo automated installation purposes.
- Policy components: console, pdp-x, and pdp-d should use client certificate authentication preferably (no consul).
- console, pdp-x, pdp-d, and consul processes should use the existing HTTP Basic Authentication mechanisms when talking to the pap component. When using client certificates, the authentication credentials will be used for authorization requests to AAF.
- When AAF is not available in a lab deployment, console,pdp-x, and pdp-d should default to use existing authentication mechanisms.
- pap should use the AAF CADI Framework client libraries to interact with AAF.
- pap should talk to AAF using HTTPS Client Certificates based authentication to perform. The pap client certificate must be stored in the pap keystore to present it to AAF.