x509 certificate package used to test the fetching of missing certificates in the chain.
Authority Information Access HTTP/FTP
- caIssuers
- end entity or CA certificates (excluding root)
- single DER encoded certificate
.cerapplication/pkix-cert
- CMS "certs-only" message
.p7capplication/pkcs7-mime
- single DER encoded certificate
- end entity or CA certificates (excluding root)
Subject Information Access HTTP/FTP
- caRepository
- CA certificates
- single DER encoded certificate
.cerapplication/pkix-cert
- CMS "certs-only" message
.p7capplication/pkcs7-mime
- single DER encoded certificate
- CA certificates
- edit
Daedalus_hierarchy.shscript and change the address of your local server:website_ca="http://localhost:1180/${test_directory}" - run the script:
./daedalus_hierarchy.sh - 2 folders will be created:
p7c_tests_xxxxx- copy to the root directory of the local serverIMPORT_THIS_xxxxx- contains files for testing the download of missing certificates via http.
In Windows, when you open IMPORT_THIS_xxxxx/cert_G1.der.cer file, the system retrieves the missing certificates and displays the following chain:
(“A” root CA certificate intentionally missing)
There are 3 generated packages on this page:
daedalus_462d7.tar.gzdaedalus_4341c.tar.gzdaedalus_04297.tar.gz
The extension included in the certificate is used to download missing certificates and build the chain up (forward direction). We start with the USER “G” and end with the “trusted” root certificate “A”.
(arrows should be drawn in reverse)
G1←F1←E1←D2←C2←B1
G2←
G3←
G4←F3←E2
G5←F4←
G6←F5←E3←
G7←F6←E4←D3←C3←B2←A
The extension included in the certificate is used to retrieve missing certificates and build the chain down (in reverse). We start with the “trusted” root certificate A and go all the way to the final USER G.
