The relevant CAs can be downloaded from section Download CAs. Whether you actually need a chain of certificates or how you would chain the certificates is out of scope for the migration process, you would need to ask the vendor of your implementation regarding what the expected format of the certificate is to be used in your particular use case. Some implementations might require you to chain this private key pair with the OpenPEPPOL Intermediate CA and Root CA.
For Internet Explorer users Enrollment with Internet ExplorerĪfter the enrollment process is complete you will end up with a private key pair.For Firefox users Enrollment with Firefox (version 56).The certificate generation is done by the OpenPeppol member using a web browser, please follow the detailed instructions with regards to which web browser is used Once you have obtained the enrollment email containing your assigned 'Service Provider ID' and an SMS with the enrollment code, you are ready to issue the certificate. The issuing process begins with the OpenPeppol member requesting a PKI v3 certificate through the Jira service desk.Īfter the request has been approved by PEPPOL Operations and the responsible PEPPOL Authority an enrollment email and SMS will be sent to the OpenPeppol member. The new CAs allow improved security (SHA-256) and some minor adjustments have been made to the naming conventions to ease the maintainability of the certificates. The new PKI infrastructure does not differ much in comparison with the old infrastructure, the biggest change has been removal of one intermediate CA (for issuing STS certificates) and changing all other CAs to new ones. On OpenPeppol will adopt a new PKI infrastructure and at the same time start the migration process.
0 kommentar(er)
