Audit log messages have tokenType=null for the event TOKEN_AUTH_SUCCESS
pki-tps-10.4.1-10.el7pki.x86_64
always
1.Configure TPS to perform key recovery using externalReg 2.Enroll a token
Cert/key recovery is successful but AuditEvent=TOKEN_AUTH_SUCCESS has tokenType null
0.http-bio-25080-exec-10 - [22/Aug/2017:08:55:44 EDT] [14] [6] [AuditEvent=TOKEN_AUTH_SUCCESS][IP=10.13.129.77][SubjectID=pkiuser2][CUID=00050045A702001F0007][MSN=00%00%00%00%][Outcome=success][OP=enroll][tokenType=null][AppletVersion=1.5.558cdcff][AuthMgr=ldap1] token authentication success 0.http-bio-25080-exec-10 - [22/Aug/2017:08:55:59 EDT] [14] [6] [[AuditEvent=TOKEN_KEY_RECOVERY][IP=10.13.129.77][SubjectID=pkiuser2][CUID=00050045A702001F0007][Outcome=success][tokenType=externalRegAddToToken][KeyVersion=010370][Serial=152103590][CA_ID=ca1][KRA_ID=kra1][Info=null] token certificate/key recovery request made 0.http-bio-25080-exec-10 - [22/Aug/2017:08:55:59 EDT] [14] [6] [[AuditEvent=TOKEN_CERT_RETRIEVAL][IP=10.13.129.77][SubjectID=pkiuser2][CUID=00050045A702001F0007][Outcome=success][tokenType=externalRegAddToToken][KeyVersion=010370][Serial=152103590][CA_ID=ca1][Info=null] token certificate retrieval request made
AuditEvent=TOKEN_AUTH_SUCCESS should have tokenType=externalRegAddToToken
Metadata Update from @dmoluguw: - 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=1484029 - 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/3302
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.