-
Story
-
Resolution: Done
-
Medium
-
None
-
None
The goal of this story is to make sure that DFC which talks to xNFs and internal ONAP components have internal and external certificates retrieved from AAF.
External certificates are planned to be retrieved from CMPv2 server and are called operator certificates. Internal certificate is the one which is used nowadays to connect to internal ONAP components (e.g. DMaaP).
Item discussed F2F with Vijay in Antwerp and following changes are foreseen (if extra flag will be needed on DCAE side to inform AAF that component would like to get also external certificates):
- Cloudify blueprint (Nokia)
- K8s plugin (Nokia)
- Blueprint generator (Nokia)
- TLS init container (Nokia)
- blocks
-
DCAEGEN2-2528 Add HTTPS as new protocol to collect files from xNFs
- Closed
- is blocked by
-
AAF-997 CertService, EJBCA and CMPv2 client integration
- Closed
-
DCAEGEN2-2459 Adjust BP-gen to correctly support DFC component spec - types
- Closed
-
DCAEGEN2-2460 Adjust BP-gen to correctly support DFC component spec - useExisting
- Closed
-
DCAEGEN2-2461 Adjust BP-gen to correctly support DFC component spec - streams
- Closed
-
DCAEGEN2-2489 BPGenerator yaml Fixes are different for yaml file and string
- Closed
- relates to
-
DCAEGEN2-1794 VES collector with certificate from CMPv2 server
- Closed
-
DCAEGEN2-1854 DataFileCollector uses wrong KeyManagerFactory
- Closed
-
DCAEGEN2-2195 HV-VES collector with certificate from CMPv2 server
- Closed
-
DCAEGEN2-2244 RestConf collector with certificate from CMPv2 server
- Closed