Certificates (From AAF)

DCAE service components will use common certifcates generated from AAF/test instance and made available during deployment of DCAE TLS init container.

DCAE has a generalized process of certificate distribution as documented here - https://docs.onap.org/en/latest/submodules/dcaegen2.git/docs/sections/tls_enablement.html

The updated certificates are located in https://git.onap.org/dcaegen2/deployments/tree/tls-init-container/tls

Certificates (Manual configuration of self-signed certifcates)

Configuration of Certificates in test environment(For FTP over TLS):

DFC supports two protocols: FTPES and SFTP. For FTPES, it is mutual authentication with certificates. In our test environment, we use vsftpd to simulate xNF, and we generate self-signed keys & certificates on both vsftpd server and DFC.

1. Generate key/certificate with openssl for DFC:

openssl genrsa -out dfc.key 2048
openssl req -new -out dfc.csr -key dfc.key
openssl x509 -req -days 365 -in dfc.csr -signkey dfc.key -out dfc.crt

2. Generate key & certificate with openssl for vsftpd:

openssl genrsa -out ftp.key 2048
openssl req -new -out ftp.csr -key ftp.key
openssl x509 -req -days 365 -in ftp.csr -signkey ftp.key -out ftp.crt

3. Configure java keystore in DFC:

We have two keystore files, one for TrustManager, one for KeyManager.

For TrustManager:

  1. First, convert your certificate in a DER format :
openssl x509 -outform der -in ftp.crt -out ftp.der
  1. And after, import it in the keystore :
keytool -import -alias ftp -keystore ftp.jks -file ftp.der

For KeyManager:

  1. First, create a jks keystore:
keytool -keystore dfc.jks -genkey -alias dfc
  1. Second, import dfc.crt and dfc.key to dfc.jks. This is a bit troublesome.

1). Step one: Convert x509 Cert and Key to a pkcs12 file

openssl pkcs12 -export -in dfc.crt -inkey dfc.key -out dfc.p12 -name [some-alias]

Note: Make sure you put a password on the p12 file - otherwise you’ll get a null reference exception when you try to import it.

Note 2: You might want to add the -chainoption to preserve the full certificate chain.

2). Step two: Convert the pkcs12 file to a java keystore:

keytool -importkeystore -deststorepass [changeit] -destkeypass [changeit] -destkeystore dfc.jks -srckeystore dfc.p12 -srcstoretype PKCS12 -srcstorepass [some-password] -alias [some-alias]

4. Update existing jks.b64 files

Copy the existing jks from the DFC container to a local environment.

docker cp <DFC container>:/opt/app/datafile/config/ftp.jks .
docker cp <DFC container>:/opt/app/datafile/config/dfc.jks .
openssl base64 -in ftp.jks -out ftp.jks.b64
openssl base64 -in dfc.jks -out dfc.jks.b64
chmod 755 ftp.jks.b64
chmod 755 dfc.jks.b64

Copy the new jks.64 files from local environment to the DFC container.

docker cp ftp.jks.b64 <DFC container>:/opt/app/datafile/config/
docker cp dfc.jks.b64 <DFC container>:/opt/app/datafile/config/


docker restart <DFC container>

5. Configure vsftpd:

update /etc/vsftpd/vsftpd.conf:




6. Configure config/datafile_endpoints.json:

Update the file accordingly:
"ftpesConfiguration": {
    "keyCert": "/config/dfc.jks",
    "keyPassword": "[yourpassword]",
    "trustedCA": "/config/ftp.jks",
    "trustedCAPassword": "[yourpassword]"

7. Other conditions

This has been tested with vsftpd and dfc, with self-signed certificates. In real deployment, we should use ONAP-CA signed certificate for DFC, and vendor-CA signed certificate for xNF