-
Story
-
Resolution: Done
-
Medium
-
None
-
None
Goal: Have E2E flow to get Cert from EJBCA
CoS:
- CMPv2 server details configurable
- Configuration stored outside container so made changes are persistent during container lifecycle management (LCM)
- Ability to configure more than one CMPv2 server provided (can be even the same but e.g. with different issuerDN)
- Finalize server implementation
- Validation of provided CMPv2 server details
- Selection of CMPv2 server details based on sent CA name
- CMPv2 client integrated with CertService
- CMPv2 client PR - https://gerrit.onap.org/r/c/aaf/authz/+/100016
- If needed CMPv2 client should be adjusted to new architecture (get rid of AAF CertMan's dependencies,e.g. CSRMeta
- blocks
-
DCAEGEN2-1794 VES collector with certificate from CMPv2 server
- Closed
-
DCAEGEN2-1795 DFC with certificate from CMPv2 server
- Closed
-
DCAEGEN2-2195 HV-VES collector with certificate from CMPv2 server
- Closed
-
DCAEGEN2-2244 RestConf collector with certificate from CMPv2 server
- Closed
- relates to
-
SDNC-926 Deploy NETCONF/TLS client certificate in ODL using AAF
- Closed