-
Story
-
Resolution: Done
-
Highest
-
None
-
None
-
None
-
Policy Casablanca - 4, Policy Casablanca - 6
These are the intended goals for policy components in Casablanca.
- Add AAF interfaces (using AAF provided CADI library) to all policy components: pdp-d, brmsgw, pdp-x, pap, and console.
- HTTPS Client certificates should be used to authenticate against AAF. Communication must be encrypted.
- Every Policy component must define its own namespace with corresponding authorization permissions in AAF.
- All existing authorization decisions must be delegated to AAF
Assumptions:
- AAF Root certificate is configured for all components (completed in
POLICY-781) - Interfaces between Policy and external components use HTTPS (completed in
POLICY-781) - HTTPS client certificate based authentication among Policy components are used internally (completed in
POLICY-781)
1.
|
Console CADI (AAF) Integration | Closed | mmokry | |
2.
|
PAP CADI (AAF) Integration | Closed | mmokry | |
3.
|
PDP CADI (AAF) Integration | Closed | mmokry | |
4.
|
BRMSGW CADI (AAF) Integration | Closed | mmokry | |
5.
|
Make AAF Configurable | Closed | mmokry | |
6.
|
Perform Unit Testing for each Component (Console, PAP, PDP-X, BRMSGW) | Closed | mmokry | |
7.
|
Upgrade Portal SDK to 2.4.0 | Closed | rb7147 |