Skip to content

Latest commit

 

History

History
76 lines (53 loc) · 3.6 KB

OnboardingChecklist.md

File metadata and controls

76 lines (53 loc) · 3.6 KB

Onboarding Checklist

Common Hints

Registration Process: Process

It is highly recommended:

  • to use certificates issued from a public CA which follows the CAB Forum Rules
  • not to reuse any certificates across the different staging environments

Links to the Environments

Test Environment

For a successfull connection to the gateway there are several steps to prepare:

  1. Certificates must be prepared for Test Environment (self signed allowed)
    • Authentication: NBTLS
    • Upload: NBUP
    • CSCA(s): NBCSCA
  2. Send the Public Keys in PEM Format to the contact of the Test Operator (functional mailbox)
  3. After Onboarding in the Test Environment, check the connectivity with the following command:
    curl -vvv -H "Accept: */*" --resolve ****.ec.europa.eu:443 --cert "auth_de.pem" --key "key.pem" https://****.ec.europa.eu/trustList
    You should see a output like:
    TrustListOutput
  4. Test the other Truslist Routes in the same style (e.g. with DSC/CSCA/Upload/Authentication...)
  5. Create an Document Signer Certificate and sign it by the CSCA
  6. Create an CMS Package with the following Command:
    openssl x509 -outform der -in cert.pem -out cert.der
    openssl cms -sign -nodetach -in cert.der -signer signing.crt -inkey signing.key -out signed.der -outform DER -binary
    openssl base64 -in signed.der -out cms.b64 -e -A 

Note: cert.der is your DSC, signing.crt ist the Uploader Certificate)

  1. Upload the CMS Package to the Gateway
    curl -v -X POST -H "Content-Type: application/cms" --cert auth_de.pem --key key.pem --data @cms.b64 https://****.ec.europa.eu/signerCertificate
  2. Download the Trustlist again, and check if your DSC is available.

Note: Some versions of curl don't attach the client certificates automatically. This can be checked via curl --version Ensure that the used version is linked to OpenSSL. Especially under Windows (https://curl.se/windows/):

OpenSSL Test Example (working)

Working Setup

WinSSL Test Example (Not working)

Non Working Setup

Acceptance Environment

  1. Order/Generate your certificates according the defined requirements in Certificate Governance:
  2. Transfer the certificates via circABC to the Secretariat
  3. After the certificate whitelisting, test the functionality again with your backend (E2E)

Production Environment

  1. Push the certificates together with your application for going live over circABC to the secretariat (TBD)
  2. Connect your production setup