Versions Compared

Key

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

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 NameHEATOOMNotes
Health CheckPASSPASSAAF Refactored OOM is working well.
 AAF ← A&AIPASSPASSA&AI Pair Wise Testing for Casablanca Release, AAI also uses new BasicAuthConvert code to support old ID formats

AAF APPC

PASSPASSAPPC (Takamune) validated Authentication and API calls (10/22)
AAF ← CLAMPPASSPASSWaiting for Clamp PTL to report AAF usage (10/22)
However, Integration-SB4 (Plantania) reports:
  1. CLAMP -> AAF: When the user wants to run operations in CLAMP, CLAMP accesses AAF to get user permissions. Status: SUCCESS
 
 AAF ← PortalPASSPASSAll tickets closed by Sunder (10/22)

AAF ← Policy

PASSPASS(*)

AAF ← Portal ← Policy OK

AAF ← Policy (Heartbeat) OK

AAF ← Policy (PDP-D) OK

(*) AAF ← Policy (PDP-X) retest POLICY-1217.

 AAF ← Portal ← VIDPASSPASS

VID contacts AAF indirectly through Portal (10/22)

AAF ← SDNC
 AAF A&AI
PASSPASS

SDNC wants to utilize BasicAuthConvert code (like AAI), instructions sent