Note: In General, AAF is the END Source of Information... Thus, clients can talk to AAF, but it does not talk to other ONAP clients.
| Projects Name | OOM | Heat | Notes |
|---|---|---|---|
| Health Check | Pass | Pass | |
AAF ↔ APPC | Has workaround (Non-block) | Pass | When we tried to validate in OOM, but discovered we needed to copy our configuration files (aaa-app-config.xml and cadi -https://gerrit.onap.org/r/#/c/50409/) into OOM, but this was rejected due to the lateness in the cycle. We are working to document a manual workaround until we have it merged into the Casablanca release. (From Randa Maher) |
| AAF ← CLAMP | Passed | Pass | CLAMP code changes have not been merged yet for AAF OOM Integration |
| AAF ← Policy | N/A | N/A | Policy is using a server certificate issued by AAF. No runtime interactions between these two Projects. |
| AAF ← SDNC | Passed | Passed | SDNC is using the AAF provided trust store, and have tested with A&AI using that. Completed test using AAF to authenticate logins. |
| AAF -→ A&AI | N/A | N/A | A&AI is using a server certificate issued by AAF. No runtime interactions between these two Projects. |