Renewal Notification message body is incorrect. It has "You can renew this certificate by clicking the "Renewal" button at the following URL: https://qe-blade-07.idm.lab.bos.redhat.com:9444", there is no Renewal button at this url.
Steps to Reproduce:
1. Configure job scheduler enabled for certRenewalNotifications in CA's CS.cfg. Set the cron job to run once per day. jobsScheduler.job.rnJob1.emailSubject=Certificate Renewal Notification jobsScheduler.job.rnJob1.emailTemplate=emails/rnJob1.txt jobsScheduler.job.rnJob1.notifyEndOffset=1 jobsScheduler.job.rnJob1.notifyTriggerOffset=1 jobsScheduler.job.rnJob1.pluginName=RenewalNotificationJob jobsScheduler.job.rnJob1.senderEmail=yourId@yourCompany.com jobsScheduler.job.rnJob1.summary.emailSubject=Certificate Renewal Notification Summary jobsScheduler.job.rnJob1.summary.emailTemplate=emails/rnJob1Summary.txt jobsScheduler.job.rnJob1.summary.enabled=true jobsScheduler.job.rnJob1.summary.itemTemplate=emails/rnJob1Item.txt jobsScheduler.job.rnJob1.summary.recipientEmail=cfu@netscape.com jobsScheduler.job.rnJob1.summary.senderEmail=yourId@yourCompany.com restart CA. 2.Request a 'Manual User Dual-Use Certificate Enrollment' certificate. 3. From the aent page approve with validity that expires in a day. Validity: Not Before: Wednesday, June 3, 2009 6:00:10 PM EDT America/New_York Not After: Thursday, June 4, 2009 5:00:10 PM EDT America/New_York 4. Now the cron job runs.
Actual results:
Two e-mails are sent. Summary e-mail and a renewal notification. Renewal notification has message body: The following certificate is going to expire (or has expired) on Thu Jun 04 17:00:10 EDT 2009 Serial number = 0x5e SubjectDN = UID=renewal4,E=aakkiang@redhat.com,CN=renewal4 You can renew this certificate by clicking the "Renewal" button at the following URL: https://qe-blade-07.idm.lab.bos.redhat.com:9444 There is no Renewal button in the URL provided.
Expected results:
The message should guide user to Follow the link 'SSL End Users Services' and 'Renew certs by selecting the renewal profile'.
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=504051 (Red Hat Certificate System)
Per CS/DS meeting of 11/02/2015: 10.4 - minor
Closed as WONT FIX for RHCS 8.x version of product.
Metadata Update from @aakkiang: - Issue set to the milestone: UNTRIAGED
Metadata Update from @mharmsen: - Custom field feature adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: None - Issue set to the milestone: 10.6 (was: UNTRIAGED)
Per 10.5.x/10.6 Triage: 10.6
alee: should be fixed, but this email is likely something that would be customized in practice.
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2230
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.