Audit log messages missing when token is enrolled using unsupported key sizes
Steps to Reproduce:
Enroll a smartcard token using key size 3072 for signing and encryption certs
Actual results:
Enrollment fails but audit log has the following messages 0.http-bio-25080-exec-3 - [02/Aug/2017:09:50:09 EDT] [14] [6] [AuditEvent=TOKEN_OP_REQUEST][IP=10.13.129.77][CUID=4090614575C1240E0327][MSN=FF%FF%FF%FF%][Outcome=success][OP=enroll][AppletVersion=1.4.58768072] token processor op request made 0.http-bio-25080-exec-3 - [02/Aug/2017:09:50:25 EDT] [14] [6] [AuditEvent=TOKEN_AUTH_SUCCESS][IP=10.13.129.77][SubjectID=scuser1][CUID=4090614575C1240E0327][MSN=FF%FF%FF%FF%][Outcome=success][OP=enroll][tokenType=userKey][AppletVersion=1.4.58768072][AuthMgr=ldap1] token authentication success 0.http-bio-25080-exec-3 - [02/Aug/2017:09:50:34 EDT] [14] [6] [AuditEvent=TOKEN_OP_REQUEST][IP=10.13.129.77][CUID=4090614575C1240E0327][MSN=FF%FF%FF%FF%][Outcome=success][OP=format][AppletVersion=1.4.58768072] token processor op request made 0.http-bio-25080-exec-3 - [02/Aug/2017:09:50:49 EDT] [14] [6] [AuditEvent=TOKEN_APPLET_UPGRADE_SUCCESS][IP=10.13.129.77][SubjectID=scuser1][CUID=4090614575C1240E0327][MSN=FF%FF%FF%FF%][Outcome=success][KeyVersion=0101][oldAppletVersion=1.4.58768072][newAppletVersion=1.4.58768072][Info=null] token applet upgrade success 0.http-bio-25080-exec-3 - [02/Aug/2017:09:50:50 EDT] [14] [6] [AuditEvent=TOKEN_FORMAT_SUCCESS][IP=10.13.129.77][SubjectID=scuser1][CUID=4090614575C1240E0327][MSN=FF%FF%FF%FF%][Outcome=success][tokenType=userKey][AppletVersion=1.4.58768072][KeyVersion=0101][Info=null] token op format success There are format related messages when attempting an enroll operation and no failure messages. There were no audit messages generated on the CA side.
Expected results:
Failure messages in TPS audit log and since it a failure while generating cert I feel there should be failure messages on CA audit as well
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=1477644 - Custom field type adjusted to None - Custom field version adjusted to None
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/3015
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)