Chapter 17. Automated Notifications
/etc/init.d/rhpki-ca stop
2. Open the CS.cfg file for that instance. This file is in the instance's conf/ directory.
3. Edit all of the configuration parameters for the notification type being enabled.
For certificate issuing notifications, there are four parameters:
ca.notification.certIssued.emailSubject
ca.notification.certIssued.emailTemplate
ca.notification.certIssued.enabled
ca.notification.certIssued.senderEmail
For certificate revocation notifications, there are four parameters:
ca.notification.certRevoked.emailSubject
ca.notification.certRevoked.emailTemplate
ca.notification.certRevoked.enabled
ca.notification.certRevoked.senderEmail
For certificate request notifications, there are five parameters:
ca.notification.requestInQ.emailSubject
ca.notification.requestInQ.emailTemplate
ca.notification.requestInQ.enabled
ca.notification.requestInQ.recipientEmail
ca.notification.requestInQ.senderEmail
The parameters for the notification messages are explained in
Automated
Notifications".
4. Save the file.
5. Restart the CA instance.
/etc/init.d/rhpki-ca start
6. If a job has been created to send automated messages, check that the mail server is correctly
Section 3.5, "Mail
configured. See
7. The messages that are sent automatically can be customized; see
Notification Messages"
17.2.2. Testing Configuration
To test whether the subsystem sends email notifications as configured, do the following:
1. Change the email address in the notification configuration for the request in queue notification to
an accessible agent or administrator email address.
2. Open the end-entities page, and request a certificate using the agent-approved enrollment form.
400
Server".
for more information.
Section 17.2, "Setting Up
Section 17.3, "Customizing
Need help?
Do you have a question about the CERTIFICATE SYSTEM 7.2 - ADMINISTRATION and is the answer not in the manual?
Questions and answers