2. EL 7
  3. strongimcv
  4. strongimcv_pki---issue(1)

Scroll to navigation

PKI --ISSUE(1) strongSwan PKI --ISSUE(1)

NAME

pki --issue - Issue a certificate using a CA certificate and key

SYNOPSIS

pki --issue [--in file] [--type type] --cakey file|--cakeyid hex --cacert file [--dn subject-dn] [--san subjectAltName] [--lifetime days] [--not-before datetime] [--not-after datetime] [--serial hex] [--flag flag] [--digest digest] [--ca] [--crl uri [--crlissuer issuer]] [--ocsp uri] [--pathlen len] [--nc-permitted name] [--nc-excluded name] [--policy-mapping mapping] [--policy-explicit len] [--policy-inhibit len] [--policy-any len] [--cert-policy oid [--cps-uri uri] [--user-notice text]] [--outform encoding] [--debug level]
pki --issue --options file
pki --issue -h | --help

DESCRIPTION

This sub-command of pki(1) is used to issue a certificate using a CA certificate and private key.

OPTIONS

Print usage information with a summary of the available options.
Set debug level, default: 1.
-+, --options file
Read command line options from file.
Public key or PKCS#10 certificate request file to issue. If not given the key/request is read from STDIN.
Type of the input. Either pub for a public key, or pkcs10 for a PKCS#10 certificate request, defaults to pub.
CA private key file. Either this or --cakeyid is required.
Key ID of a CA private key on a smartcard. Either this or --cakey is required.
CA certificate file. Required.
Subject distinguished name (DN) of the issued certificate.
subjectAltName extension to include in certificate. Can be used multiple times.
Days the certificate is valid, default: 1095. Ignored if both an absolute start and end time are given.
Absolute time when the validity of the certificate begins. The datetime format is defined by the --dateform option.
Absolute time when the validity of the certificate ends. The datetime format is defined by the --dateform option.
strptime(3) format for the --not-before and --not-after options, default: %d.%m.%y %T
Serial number in hex. It is randomly allocated by default.
Add extendedKeyUsage flag. One of serverAuth, clientAuth, crlSign, or ocspSigning. Can be used multiple times.
Digest to use for signature creation. One of md5, sha1, sha224, sha256, sha384, or sha512. Defaults to sha1.
Encoding of the created certificate file. Either der (ASN.1 DER) or pem (Base64 PEM), defaults to der.
Include CA basicConstraint extension in certificate.
CRL distribution point URI to include in certificate. Can be used multiple times.
Optional CRL issuer for the CRL at the preceding distribution point.
OCSP AuthorityInfoAccess URI to include in certificate. Can be used multiple times.
Set path length constraint.
Add permitted NameConstraint extension to certificate.
Add excluded NameConstraint extension to certificate.
Add policyMapping from issuer to subject OID.
Add requireExplicitPolicy constraint.
Add inhibitPolicyMapping constraint.
Add inhibitAnyPolicy constraint.

Certificate Policy

Multiple certificatePolicy extensions can be added. Each with the following information:

OID to include in certificatePolicy extension. Required.
Certification Practice statement URI for certificatePolicy.
User notice for certificatePolicy.

EXAMPLES

To save repetitive typing, command line options can be stored in files. Lets assume pki.opt contains the following contents:



  --cacert ca_cert.der --cakey ca_key.der --digest sha256


  --flag serverAuth --lifetime 1460 --type pkcs10

Then the following command can be used to issue a certificate based on a given PKCS#10 certificate request and the options above:



  pki --issue --options pki.opt --in req.der > cert.der

SEE ALSO

pki(1)

2013-08-12 5.2.0