This article is valid for Nexus OCSP responder 6.1 and later.

This article describes the ocsp.conf file installed with Nexus OCSP Responder, that is, the default configuration.

Scramble sensitive configuration parameters

Providers

The order of cryptographic providers used by the Nexus OCSP Responder.

ocsp.providers.1=org.bouncycastle.jce.provider.BouncyCastleProvider
ocsp.providers.2=com.id2tech.security.provider.ID2
ocsp.providers.3=com.id2tech.security.store.ID2Store

Validators

For more information, see Validation section.

CRL Validator

ocsp.validation.1.type=crl
ocsp.validation.1.cacheDir=crls
ocsp.validation.1.provider.1.type=push
ocsp.validation.1.provider.1.listen.url=http://*:8081/

CIL Validator

ocsp.validation.2.type=cil
ocsp.validation.2.cacheDir=cils
ocsp.validation.2.provider.1.type=push
ocsp.validation.2.provider.1.listen.url=http://*:8082/

Responders

For more information, see OCSP responder section.

Basic Responder

Non Issued Basic Responder

Fallback Responder

Key Stores

For more information, see Key management section.

Log file

For more information, see System management section.

Java Util Logging level

ocsp.java.util.logging.level - The Java Util Logging level that should be redirected to OCSP agent to be captured.

Possible values: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST.
- SEVERE, WARNING, INFO, CONFIG are redirected with class=oper.
- FINE, FINER, FINEST are redirected with class=trace.
Output printed to system err/out is printed with level FINE. For example when enabling debugging of TLS connections with the Java VM parameter: - Djavax.net.debug=ssl:handshake

Default value

Global log parameters

Configurations for cmsdk-connection

cmsdk-connection.conf

Configuration parameters in this file are used for connecting to a CF service when using a responder of type fallback. Relative paths specified below are relative the <config-root>.

CM connection parameters

cmhost
Must be set to the network id of the machine that hosts the CF that should be used.

cmconnectiontimeout
Number of milliseconds the connector will wait trying to connect to the CF server. Default value is 0, meaning infinite.

cmreadtimeout
Number of milliseconds the connector will wait trying to receive data from the CF server. Default value is 3600000, meaning one hour.

cmconnections
The maximum amount of concurrent officer connections to CF to allocate to the officer pool.

cmclientretries
How many times sending a request should be retried if the connection to CM is unexpectedly closed. Default value is 0.

CM officer

The CM officer is specified by either the keyfile or the subject parameter. These parameters specifies the CM officer to be used when establishing a connection to the CM Server and to create signatures for requests. Required when using the fallback responder type.
officer.keyfile contains the file path of the soft token (.p12 file) containing the key(s) and certificate(s) of the CM officer.
officer.certificate.subject contains the name or part of the name (subject DN) of the CM officer. This parameter is used to select a certificate from those provided by the configured PKCS11 libraries.

officer.password contains the password/PIN code needed to access the token holding the officer's identity.

officer.pkcs11 specifies a PKCS#11 library that should be searched for the CM officer certificate when it is loaded from the PKCS#11 key store.

TLS parameters

ssl.rootfilename contains the path of the file or directory that contains the trusted root CA's. The file or directory must contain one of the certificates in the chain that CF will use to identify itself.

Nexus Documentation

Default OCSP configuration