Now you can use the root key above to issue a root certificate (ca.cert.pem).

In this example, the certificate is set to expire in ten years. As this is a CA certificate,
use the v3_ca extension. You will be prompted for some responses, which you can fill with whatever you like.

For convenience, defaults can be set in the openssl configuration file.

The default digest is SHA-1. SHA-1 is considered insecure.
Pass the -sha256 option to use a more secure digest.

# openssl.cnf## OpenSSL example configuration file.# This is mostly being used for generation of certificate requests.## This definition stops the following lines choking if HOME isn't# defined.HOME= .
RANDFILE=$ENV::HOME/.rnd
# Extra OBJECT IDENTIFIER info:#oid_file = $ENV::HOME/.oidoid_section= new_oids
# To use this configuration file with the "-extfile" option of the# "openssl x509" utility, name here the section containing the# X.509v3 extensions to use:# extensions =# (Alternatively, use a configuration file that has only# X.509v3 extensions in its main [= default] section.)[ new_oids ]# We can add new OIDs in here for use by 'ca', 'req' and 'ts'.# Add a simple OID like this:# testoid1=1.2.3.4# Or use config file substitution like this:# testoid2=${testoid1}.5.6# Policies used by the TSA examples.tsa_policy1=1.2.3.4.1
tsa_policy2=1.2.3.4.5.6
tsa_policy3=1.2.3.4.5.7
####################################################################[ ca ]default_ca= CA_default # The default ca section####################################################################[ CA_default ]dir= /home/or/workspace/prj/me/TS/crt # Where everything is keptcerts=$dir/certs # Where the issued certs are keptcrl_dir=$dir/crl # Where the issued crl are keptdatabase=$dir/index.txt # database index file.#unique_subject = no # Set to 'no' to allow creation of# several ctificates with same subject.new_certs_dir=$dir/newcerts # default place for new certs.certificate=$dir/cacert.pem # The CA certificateserial=$dir/serial # The current serial numbercrlnumber=$dir/crlnumber # the current crl number# must be commented out to leave a V1 CRLcrl=$dir/crl.pem # The current CRLprivate_key=$dir/private/cakey.pem# The private key
RANDFILE=$dir/private/.rand # private random number filex509_extensions= usr_cert # The extentions to add to the cert# Comment out the following two lines for the "traditional"# (and highly broken) format.name_opt= ca_default # Subject Name optionscert_opt= ca_default # Certificate field options# Extension copying option: use with caution.# copy_extensions = copy# Extensions to add to a CRL. Note: Netscape communicator chokes on V2 CRLs# so this is commented out by default to leave a V1 CRL.# crlnumber must also be commented out to leave a V1 CRL.# crl_extensions = crl_extdefault_days=365# how long to certify fordefault_crl_days=30# how long before next CRLdefault_md= default # use public key default MDpreserve= no # keep passed DN ordering# A few difference way of specifying how similar the request should look# For type CA, the listed attributes must be the same, and the optional# and supplied fields are just that :-)policy= policy_match
# For the CA policy[ policy_match ]countryName= match
stateOrProvinceName= match
organizationName= match
organizationalUnitName= optional
commonName= supplied
emailAddress= optional
# For the 'anything' policy# At this point in time, you must list all acceptable 'object'# types.[ policy_anything ]countryName= optional
stateOrProvinceName= optional
localityName= optional
organizationName= optional
organizationalUnitName= optional
commonName= supplied
emailAddress= optional
####################################################################[ req ]default_bits=2048default_keyfile= privkey.pem
distinguished_name= req_distinguished_name
attributes= req_attributes
x509_extensions= v3_ca # The extentions to add to the self signed cert# Passwords for private keys if not present they will be prompted for# input_password = secret# output_password = secret# This sets a mask for permitted string types. There are several options.# default: PrintableString, T61String, BMPString.# pkix : PrintableString, BMPString (PKIX recommendation before 2004)# utf8only: only UTF8Strings (PKIX recommendation after 2004).# nombstr : PrintableString, T61String (no BMPStrings or UTF8Strings).# MASK:XXXX a literal mask value.# WARNING: ancient versions of Netscape crash on BMPStrings or UTF8Strings.string_mask= utf8only
# req_extensions = v3_req # The extensions to add to a certificate request[ req_distinguished_name ]countryName= Country Name (2 letter code)countryName_default= AU
countryName_min=2countryName_max=2stateOrProvinceName= State or Province Name (full name)stateOrProvinceName_default= Some-State
localityName= Locality Name (eg, city)0.organizationName = Organization Name (eg, company)0.organizationName_default = Internet Widgits Pty Ltd
# we can do this but it is not needed normally :-)#1.organizationName = Second Organization Name (eg, company)#1.organizationName_default = World Wide Web Pty LtdorganizationalUnitName= Organizational Unit Name (eg, section)#organizationalUnitName_default =commonName= Common Name (e.g. server FQDN or YOUR name)commonName_max=64emailAddress= Email Address
emailAddress_max=64# SET-ex3 = SET extension number 3[ req_attributes ]challengePassword= A challenge password
challengePassword_min=4challengePassword_max=20unstructuredName= An optional company name
[ usr_cert ]# These extensions are added when 'ca' signs a request.# This goes against PKIX guidelines but some CAs do it and some software# requires this to avoid interpreting an end user certificate as a CA.basicConstraints=CA:FALSE
# Here are some examples of the usage of nsCertType. If it is omitted# the certificate can be used for anything *except* object signing.# This is OK for an SSL server.# nsCertType = server# For an object signing certificate this would be used.# nsCertType = objsign# For normal client use this is typical# nsCertType = client, email# and for everything including object signing:# nsCertType = client, email, objsign# This is typical in keyUsage for a client certificate.keyUsage= nonRepudiation, digitalSignature, keyEncipherment
# This will be displayed in Netscape's comment listbox.nsComment="OpenSSL Generated Certificate"# PKIX recommendations harmless if included in all certificates.subjectKeyIdentifier=hashauthorityKeyIdentifier=keyid,issuer
# This stuff is for subjectAltName and issuerAltname.# Import the email address.# subjectAltName=email:copy# An alternative to produce certificates that aren't# deprecated according to PKIX.# subjectAltName=email:move# Copy subject details# issuerAltName=issuer:copy#nsCaRevocationUrl = http://www.domain.dom/ca-crl.pem#nsBaseUrl#nsRevocationUrl#nsRenewalUrl#nsCaPolicyUrl#nsSslServerName# This is required for TSA certificates.extendedKeyUsage= critical,timeStamping
[ v3_req ]# Extensions to add to a certificate requestbasicConstraints= CA:FALSE
keyUsage= nonRepudiation, digitalSignature, keyEncipherment
[ v3_ca ]# Extensions for a typical CA# PKIX recommendation.subjectKeyIdentifier=hashauthorityKeyIdentifier=keyid:always,issuer
# This is what PKIX recommends but some broken software chokes on critical# extensions.basicConstraints= critical,CA:true
# So we do this instead.#basicConstraints = CA:true# Key usage: this is typical for a CA certificate. However since it will# prevent it being used as an test self-signed certificate it is best# left out by default.keyUsage= cRLSign, keyCertSign
# Some might want this also# nsCertType = sslCA, emailCA# Include email address in subject alt name: another PKIX recommendation# subjectAltName=email:copy# Copy issuer details# issuerAltName=issuer:copy# DER hex encoding of an extension: beware experts only!# obj=DER:02:03# Where 'obj' is a standard or added object# You can even override a supported extension:# basicConstraints= critical, DER:30:03:01:01:FF#extendedKeyUsage = critical, clientAuth[ crl_ext ]# CRL extensions.# Only issuerAltName and authorityKeyIdentifier make any sense in a CRL.# issuerAltName=issuer:copyauthorityKeyIdentifier=keyid:always
[ proxy_cert_ext ]# These extensions should be added when creating a proxy certificate# This goes against PKIX guidelines but some CAs do it and some software# requires this to avoid interpreting an end user certificate as a CA.basicConstraints=CA:FALSE
# Here are some examples of the usage of nsCertType. If it is omitted# the certificate can be used for anything *except* object signing.# This is OK for an SSL server.# nsCertType = server# For an object signing certificate this would be used.# nsCertType = objsign# For normal client use this is typical# nsCertType = client, email# and for everything including object signing:# nsCertType = client, email, objsign# This is typical in keyUsage for a client certificate.# keyUsage = nonRepudiation, digitalSignature, keyEncipherment# This will be displayed in Netscape's comment listbox.nsComment="OpenSSL Generated Certificate"# PKIX recommendations harmless if included in all certificates.subjectKeyIdentifier=hashauthorityKeyIdentifier=keyid,issuer
# This stuff is for subjectAltName and issuerAltname.# Import the email address.# subjectAltName=email:copy# An alternative to produce certificates that aren't# deprecated according to PKIX.# subjectAltName=email:move# Copy subject details# issuerAltName=issuer:copy#nsCaRevocationUrl = http://www.domain.dom/ca-crl.pem#nsBaseUrl#nsRevocationUrl#nsRenewalUrl#nsCaPolicyUrl#nsSslServerName# This really needs to be in place for it to be a proxy certificate.proxyCertInfo=critical,language:id-ppl-anyLanguage,pathlen:3,policy:foo
####################################################################[ tsa ]default_tsa= tsa_config1 # the default TSA section[ tsa_config1 ]# These are used by the TSA reply generation only.dir= ./demoCA # TSA root directoryserial=$dir/tsaserial # The current serial number (mandatory)crypto_device=builtin# OpenSSL engine to use for signingsigner_cert=$dir/tsacert.pem # The TSA signing certificate# (optional)certs=$dir/cacert.pem # Certificate chain to include in reply# (optional)signer_key=$dir/private/tsakey.pem # The TSA private key (optional)default_policy= tsa_policy1 # Policy if request did not specify it# (optional)other_policies= tsa_policy2, tsa_policy3 # acceptable policies (optional)digests= md5, sha1 # Acceptable message digests (mandatory)accuracy= secs:1, millisecs:500, microsecs:100 # (optional)clock_precision_digits=0# number of digits after dot. (optional)ordering= yes # Is ordering defined for timestamps?# (optional, default: no)tsa_name= yes # Must the TSA name be included in the reply?# (optional, default: no)ess_cert_id_chain= no # Must the ESS cert id chain be included?# (optional, default: no)

Note about common name:

Common Name (e.g. server FQDN or YOUR name) []:example.local

The Common Name option is the most important, as your domain used with the certificate needs to match it.

If you use the “www” subdomain, this means specifying the “www” subdomain as well!

Note about serial number:

This error (Errorcode:sec_error_reused_issuer_and_serial) occurred in firefox page with this description:

Your certificate contains the same serial number as another certificate issued by the certificate authority.

JSON Web Token is a fairly new standard which can be used for token-based authentication.
Unlike the built-in TokenAuthentication scheme,
JWT Authentication doesn’t need to use a database to validate a token.