Set up a secure connection to the Hermes Messaging Service
-
- UpdatedJan 30, 2025
- 3 minutes to read
- Yokohama
- Now Platform Capabilities
Secure your Kafka topics by generating a ServiceNow® instance-signed certificate.
Before you begin
Setting up the Hermes Messaging Service requires coordination with your network administrator and with your Kafka administrator. Work with your network administrator to obtain required security certificates and open the required ports. Work with your Kafka administrator to ensure that your Kafka environment is configured correctly and that your applications can connect to the Hermes Messaging Service using the standard Kafka protocol.
Make sure the following setup is in place:
- The Hermes Messaging Service is activated. See Hermes Messaging Service activation.
- The Key Management Framework plugin (com.glide.kmf.global) is activated.
- The Certificates [sys_kmf_certificate] table contains a ServiceNow instance root CA certificate.
- The instance isn't configured with a Custom URL. Custom URLs are not supported with the Instance PKI Certificate Generator.
Role required: hermes_admin, sn_kmf.cryptographic_manager, or admin
For details on assigning KMF roles, see Roles installed with Key Management Framework.
Procedure
Result
You can now create a secure connection to the Hermes Messaging Service.
What to do next
- Review the guidance in Exchanging data using the Hermes Messaging Service.
- Prepare your Apache Kafka client environment
- Configure the SSL connection to Hermes in the producer and consumer properties files using the truststore and keystore files that you generated. For more information, refer to the following topics:
Related Content
- Hermes Messaging Service activation
The Hermes Messaging Service is enabled when the Glide Hermes Message Queue plugin (com.glide.hermes) is activated.
- Revoke a Hermes Messaging Service certificate
Revoke a ServiceNow instance-signed certificate so that it can't be used in secure connections to the Hermes Messaging Service.