#1559 Job notification email is not send when caDirUserCert certificate is issued
Closed: fixed 6 years ago Opened 8 years ago by rpattath.

Job notification email is not send when caDirUserCert certificate is issued

Steps to Reproduce:

This should be tested in on CA. Set the following config parameters ( these
should be done via the console):

subSystemId.notification.certIssued.emailSubject=Your Certificate Request
subSystemId.notification.certIssued.emailTemplate=emails/certIssued_CA.html
subSystemId.notification.certIssued.enabled=true
subSystemId.notification.certIssued.senderEmail=yourId@yourCompany.com

Actual results:

Email notification is not sent when a cert of type caDirUserCert is issued

Expected results:

Email notification should be sent

Additional info:

CA debug log messages:

[13/Aug/2015:17:03:08][Thread-24]: RunListeners:: Queue: 1  noSingleRequest
[13/Aug/2015:17:03:08][Thread-24]: getRequest  mRequests=1
mSearchForRequests=false
[13/Aug/2015:17:03:08][Thread-24]: getRequest  getting request: 94
[13/Aug/2015:17:03:08][Thread-24]: In LdapBoundConnFactory::getConn()
[13/Aug/2015:17:03:08][Thread-24]: masterConn is connected: true
[13/Aug/2015:17:03:08][Thread-24]: getConn: conn is connected true
[13/Aug/2015:17:03:08][Thread-24]: getConn: mNumConns now 2
[13/Aug/2015:17:03:08][Thread-24]: returnConn: mNumConns now 3
[13/Aug/2015:17:03:08][Thread-24]: getRequest  request 94 found
[13/Aug/2015:17:03:08][Thread-24]: getRequest  mRequests=0
mSearchForRequests=false done
[13/Aug/2015:17:03:08][Thread-24]: RunListeners: IRequestListener =
com.netscape.cms.listeners.CertificateIssuedListener
[13/Aug/2015:17:03:08][Thread-24]: CertificateIssuedListener: accept 94
[13/Aug/2015:17:03:08][Thread-24]: CertificateIssuedListener: accept check
status
[13/Aug/2015:17:03:08][Thread-24]: accept() enrollment/renewal request...
[13/Aug/2015:17:03:08][Thread-24]: CertificateIssuedListener: Sending email
notification..
[13/Aug/2015:17:03:08][Thread-24]: about to try subjectalternatename
[13/Aug/2015:17:03:08][Thread-24]: got an subjectalternatename email
[13/Aug/2015:17:03:08][http-bio-30044-exec-8]: ProfileSubmitServlet: done
serving
[13/Aug/2015:17:03:08][http-bio-30044-exec-8]: CMSServlet: curDate=Thu Aug 13
17:03:08 EDT 2015 id=caProfileSubmit time=197
[13/Aug/2015:17:03:08][Thread-24]: RunListeners: IRequestListener =
com.netscape.ca.CRLIssuingPoint$RevocationRequestListener
[13/Aug/2015:17:03:08][Thread-24]: RunListeners: IRequestListener =
com.netscape.cmscore.ldap.LdapRequestListener
[13/Aug/2015:17:03:08][Thread-24]: LdapRequestListener handling publishing for
enrollment request id 94
[13/Aug/2015:17:03:08][Thread-24]: Checking publishing for request 94
[13/Aug/2015:17:03:08][Thread-24]: In  PublisherProcessor::publishCert
[13/Aug/2015:17:03:08][Thread-24]: PublisherProcessor: in publishNow()
[13/Aug/2015:17:03:08][Thread-24]: In LdapBoundConnFactory::getConn()
[13/Aug/2015:17:03:08][Thread-24]: masterConn is connected: true
[13/Aug/2015:17:03:08][Thread-24]: getConn: conn is connected true
[13/Aug/2015:17:03:08][Thread-24]: getConn: mNumConns now 2
[13/Aug/2015:17:03:08][Thread-24]: LdapSimpleMap: cert subject
dn:UID=pkiuser2,OU=people,DC=pki-ca
[13/Aug/2015:17:03:08][Thread-24]: MapAVAPattern: attr O not formed from: cert
subject UID=pkiuser2,OU=people,DC=pki-ca-- no subject component : o
[13/Aug/2015:17:03:08][Thread-24]: Error mapping:
mapper=com.netscape.cms.publish.mappers.LdapSimpleMap@6a7e6f83 error=pattern
not matched
[13/Aug/2015:17:03:08][Thread-24]: returnConn: mNumConns now 3
[13/Aug/2015:17:03:08][Thread-24]: PublishProcessor::publishCert : Failed to
publish using rule:  LdapUserCertRule
[13/Aug/2015:17:03:08][Thread-24]: RunListeners: IRequestListener =
com.netscape.cms.listeners.CertificateRevokedListener
[13/Aug/2015:17:03:08][Thread-24]: RunListeners: mRequest = 94
[13/Aug/2015:17:03:08][Thread-24]: updatePublishingStatus
mSavePublishingCounter: 7 mSavePublishingStatus: 200
[13/Aug/2015:17:03:08][Thread-24]: RunListeners:  noQueue  SingleRequest
[13/Aug/2015:17:03:08][Thread-24]: RequestRepository:  setPublishingStatus
mBaseDN: ou=ca,ou=requests,dc=pki-ca  status: -1
[13/Aug/2015:17:03:08][Thread-24]: In LdapBoundConnFactory::getConn()
[13/Aug/2015:17:03:08][Thread-24]: masterConn is connected: true
[13/Aug/2015:17:03:08][Thread-24]: getConn: conn is connected true
[13/Aug/2015:17:03:08][Thread-24]: getConn: mNumConns now 2
[13/Aug/2015:17:03:08][Thread-24]: returnConn: mNumConns now 3
[13/Aug/2015:17:03:08][Thread-24]: Number of publishing threads: 0

Per CS/DS meeting of 08/24/2015 - 10.3.

Per Bug Triage of 05/05/2016: 10.4

NOTE: work with QE, may be invalid

Metadata Update from @rpattath:
- Issue set to the milestone: UNTRIAGED

7 years ago

Metadata Update from @cfu:
- Issue assigned to cfu

6 years ago

note: my investigation shows that this is only a configuration thing. See below checkin comment:

Author: Christina Fu cfu@redhat.com
Date: Fri Sep 1 11:19:17 2017 -0700

Ticket #1559 email notification failed.

This is only a patch that provides more debugging to shed some light on what's happening.
What happends is that one needs to set smtp.host to your site's smtp server:
e.g.: smtp.host=smtp.Example.com

Change-Id: I05b4db05ad19a2e58f629487d7edcb4ddb014ce5

Metadata Update from @cfu:
- 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: fixed

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: UNTRIAGED)

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.0 (was: 10.5)

6 years ago

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.5.0-1.fc27

6 years ago

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/2118

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata