Renewal notification email sent even after the cert renewed.
Steps to Reproduce:
1. Configure job scheduler enabled for certRenewalNotifications in CA' CS.cfg. Set the cron job to run once per day. Provide e-mail addresses and following offsets with value 1. jobsScheduler.job.certRenewalNotifier.notifyEndOffset=1 jobsScheduler.job.certRenewalNotifier.notifyTriggerOffset=1 Restart CA. 2. Request a 'Manual User Dual-Use Certificate Enrollment' certificate. 3. From the agent page approve with validity that expires in a day. Example: 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. User Import the cert on the browser. 5. Now that the cron job runs, 2 notifications are sent, one is a renewal notification summary and other is notification for the user to the user with a url to renew. 6. User follow the url link in the renewal notification and renew the cert by selecting 'Self-renew user SSL client certificates' profile. Cert gets renewed. 7. Cron job is run next day.
Actual results:
Two notifications are sent, one is a renewal notification summary (has the old cert which user has renewed) and other is notification for the user with a url to renew. This is annoying spam e-mail, since renew notification is sent even after user renews the cert. Number of times user gets spam e-mails with these notifications depends on the value of 'notifyEndOffset'.
Expected results:
Should not send renewal notifications after the cert gets renewed. Renewal notification summary should not have the renewed (old) certificate.
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=504053 (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
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/2229
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.