...
Input Table for CMPV2 client:
Input Values | Input Type | Description | Usage |
|---|---|---|---|
| csrMeta | object | csrMeta object from aaf, would contain values needed for certificate request. any needed values that should be stored in the csrMeta will be mentioned below. | stores all pertinent values for certificate request - these will be detailed below, and should be set before being passed to the cmpv2 client. |
| csrMeta:IssuerDn | distinguished name of the CA we're receiving certificate from. Cannot be null | used in the creation of the cert on EJBCA server | |
| csrMeta: SubjectDn | Distinguished name of the Entity the certificate is being issued to/ Certificate Requesting Entity. Cannot be null. | used in the creation of the cert on EJBCA server | |
| csrMeta: KeyPair | KeyPair associated with the entity the certificate is being issued to. Cannot be null | used to create proof of possession for request to EJBCA server | |
| csrMeta: Password | secret password value shared by EJBCA server. Cannot be null | used to authenticate ourselves to the EJBCA serve | |
csrMeta: CA Details | Certification Authority Details ( Http address, Port number and Path (which includes alias if used)). Cannot be null | used to Post Http request to External CA. | |
.cer file | .cer (CSR) generated by Cert-man using Key-pair. Cannot be null. | used to validate response (.crt)/ certificate send from EJBCA server | |
| beforeDate | date object representing the date a certificate is not valid before | used to add a valid date period for the cert. | |
| afterDate | date object representing the date a certificate is not valid after | used to add a valid date period for the cert. | |
| caName | the name and general description of the external CA | used for debugging purposes | |
| caMode | string noting whether the server we are contacting will be operating in either client or RA mode | used for debugging purposes |
...