Path to the service's keystore file.
|
Value |
String (a filepath). For the recommended path, see Copying certificates and keys. |
|
Default |
(none) By default, the NLP service uses the Java keystore. |
|
How to set |
In Management Station, set on the Natural Language Processing service. If not using Management Station, set in the NLP service configuration file (User-nlpsxx.properties, see Configuration roadmap). |
|
Usage |
Typically changed once, when setting up secure connections during the transition from development to production environments. See Securing connections with SSL/TLS. If you specify this parameter, the new filepath becomes your keystore and truststore. To define a separate truststore, see httpClient.truststore. This parameter is applicable when using HTTPS. See Securing connections with SSL/TLS. |
Use this keystore to store CA certificates for the NLP service to authenticate itself to clients.
You can store additional certificates in this keystore for the NLP service to identify itself to servers that request authentication. This is relevant when the NLP service communicates as a client. However, you can only store those certificates in the keystore when the httpClient.truststore is empty because the system uses the truststore if it is defined.
