You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 5
Next »
This article is valid for Nexus OCSP Responder 6.2 and later.
This article and its sub-articles describe how to configure Nexus OCSP Responder. When running the Nexus OCSP Responder, the application will read files (for example, configuration and truststore) from <configuration root>.
Open the configuration file
- Open the configuration file ocsp.conf for editing:
On Windows, the path to the <configuration root> is chosen during installation and is defined in the string registry key named Arguments in the following Windows registry path:
HKEY_LOCAL_MACHINE\SOFTWARE\Nexus\Service Parameters\OCSP
- On Linux, the path to the <configuration root> is defined in <install root>/bin/nexus-ocsp.conf by the following parameter:
SERVICEARGUMENTS='-p <configuration root>
- You can manually change the path after the installation by redefining the path parameter to point to a new configuration root directory.
Mandatory settings
In the configuration file, each main configurable entity has its own section. The corresponding parameter names are built up with prefixes associated with the entity.
Optional settings
- Do the other settings in the OCSP configuration file (optional).
| Configurable Entity | Description | Prefix |
|---|
Certificate lookup (optional) | If a required certificate cannot be found in the cache, it may be searched in specified directories. | ocsp.certs |
| Back end client (optional) | Certificates can be validated by use of external OCSP responders. The OCSP client that should send the requests, will use several methods to find the responder URLs. | ocsp.client |
| OCSP response cache (optional) | The response cache is a cache where responses from external OCSP responders can be stored. | ocsp.cache |
See these articles for configuration of Nexus OCSP Responder:
The articles that are gathered here: Nexus OCSP Responder descriptions and workflow include descriptions for various concepts used within Nexus OCSP Responder and also some useful workflows.
Specify file paths
You can specify a full path to a file or a directory, such as ocsp.trust.store=C:\Program Files\Nexus\OCSP Responder\certs\trust.store.
Alternatively, specify a relative path (default): ocsp.trust.store=certs/trust.store ("/" makes the specification OS-independent)
On both Windows and Linux environments, the relative path will start from the <configuration root> directory.
Case sensitivity
| Entity | Case sensitive |
|---|
| Configuration parameter names | No |
| File names | Yes (when appearing as values, that is, on the right hand side of an "=") |
| LDAP searchbase and filters | Yes (when appearing as values, that is, on the right hand side of an "=") |
| Distinguished name patterns used for certificate matching | Yes (when appearing as values, that is, on the right hand side of an "=") |
| URLs | Yes (when appearing as values, that is, on the right hand side of an "=") |
| Constants and types | No |
After updates
When you have done configuration updates, restart Nexus OCSP Responder.
Encryption of sensitive configuration parameters
To scramble any configuration parameter in the configuration file, add the keyword encrypted to the parameter definition in the configuration. The next time the application starts, it scans the configuration file for unscrambled values and scrambles the value. The updated configuration file is saved to disk.
For example: *.pin = 1234 is considered to be sensitive and should therefore be scrambled.
- To scramble the parameter, replace the parameter with
*.pin.encrypted = 1234. - The server will find the unscrambled value and scramble it.
- In the resulting configuration file the parameter is rewritten to
*.pin.encrypted = encrypted:MCa12== for example.
