CA and TPS audit log messages should mention the key size info during token enrollment
Steps to Reproduce:
Perform a smartcard enrollment
Actual results:
CA audit log messages 0.http-bio-21443-exec-16 - [01/Aug/2017:14:28:53 EDT] [14] [6] [AuditEvent=PROFILE_CERT_REQUEST][SubjectID=TPS-nocp1.idm.lab.eng.rdu2.redhat.com-25443][Outcome=Success][ReqID=79][ProfileID=caTokenUserEncryptionKeyEnrollment][CertSubject=UID=scuser1,O=Token Key User] certificate request made with certificate profiles 0.http-bio-21443-exec-16 - [01/Aug/2017:14:28:53 EDT] [14] [6] [AuditEvent=CERT_REQUEST_PROCESSED][SubjectID=TPS-nocp1.idm.lab.eng.rdu2.redhat.com-25443][Outcome=Success][ReqID=79][CertSerialNum=16151503] certificate request processed TPS audit log: 0.http-bio-25080-exec-1 - [01/Aug/2017:14:28:43 EDT] [14] [6] [[AuditEvent=TOKEN_CERT_ENROLLMENT][IP=10.13.129.77][SubjectID=scuser1][CUID=4090614575C1240E0327][Outcome=success][tokenType=userKey][KeyVersion=0101][Serial=217734641][CA_ID=ca1][Info=null] token certificate enrollment request made 0.http-bio-25080-exec-1 - [01/Aug/2017:14:28:53 EDT] [14] [6] [[AuditEvent=TOKEN_CERT_ENROLLMENT][IP=10.13.129.77][SubjectID=scuser1][CUID=4090614575C1240E0327][Outcome=success][tokenType=userKey][KeyVersion=0101][Serial=16151503][CA_ID=ca1][Info=null] token certificate enrollment request made
Expected results:
key size information should be stored in the audit log messages
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1477318 - Custom field type adjusted to None - Custom field version adjusted to None - Issue priority set to: major - Issue set to the milestone: 10.5
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Per 10.5.x/10.6 Triage: 10.5
Metadata Update from @mharmsen: - Custom field lowhangingfruit adjusted to jmagne: low hanging and kind of useful info for audit log. - Issue set to the milestone: 10.5 (was: 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/2922
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)