The Domino server task communicates with the REST API through the
KeepManagementURL. It has a default value of
http://localhost:8889. You can overwrite this ssetting in the
notes.ini by editing (or creating if missing) the entry
KeepManagementURL (case sensitive). Having configured an TLS certificate you need to make sure the entry starts with
https:// and uses the host name your TLS certificate has been issued for.
::1 will not work. Configuring TLS doesn't change the port, so when you host, your TLS certificate is issued for, is
domino.demo.com and your old entry was missing or is the default of
http://localhost:8880, then your new value needs to be:
https://domino.demo.com:8889 For more information, see Domino REST API task and ports.
Domino REST API comes with reasonable default configuration settings. They allow you to start evaluating and testing out-of-the-box. For an actual deployment, you want to understand the details as outlined here.
The configuration follows the concept of an Overlay File System, where the base configuration is retrieved from the jar file and then overlaid with all the JSON files (if present) in the
keepconfig.d directory within the Notes data directory and finally, the environment parameters, if any of those exist. Check the details here.
Parameters are case sensitive.
|HTTP(S) port for the Domino REST API service.
|Endpoint for Prometheus Metrics.
|Lifetime in minutes for the internal JWT provider. Default value is 60 mins.
|Maximum lifetime in minutes that the JWT tokens get accepted.
|TLS file with key for jks, pem or pfx.
|Password for jks and pfx key file.
|Passphrase for posting to http://localhost:adminport/shutdown to shut down Domino REST API.
|Username for accessing Health check (Port 8886)
|Password for accessing Health check (Port 8886)
The current configuration can be retrieved, with sensitive information masked, on the management port such as