#2501 TPS audit log messages does not have information about the cert being recovered or deleted from a token
Closed: migrated 3 years ago by dmoluguw. Opened 7 years ago by rpattath.

TPS audit log messages does not have information about the cert being recovered
or deleted from a token

Steps to Reproduce:

1. Recover a few certs on a token of type externalRegAddToToken.

dn: uid=pkiuser3,ou=People,dc=pki-tps1
objectClass: person
objectClass: organizationalPerson
objectClass: inetorgperson
objectClass: top
objectClass: extensibleobject
cn: pkiuser3
sn: pkiuser3
uid: pkiuser3
givenName: pkiuser3
mail: pkiuser3@example.org
firstname: pkiuser3
tokenType: externalRegAddToToken
userPassword:: e1NTSEF9ZXJXMFptMjlKRks5REpkdGRzNk9QQWJtWm5yeHJTK2NjWGpjeXc9PQ=
 =
certstoadd: 58,ca1
certstoadd: 53,ca1,14,kra1

2. Delete a cert from the token by modifying the ldap entry as follows

dn: uid=pkiuser3,ou=People,dc=pki-tps1
objectClass: person
objectClass: organizationalPerson
objectClass: inetorgperson
objectClass: top
objectClass: extensibleobject
cn: pkiuser3
sn: pkiuser3
uid: pkiuser3
givenName: pkiuser3
mail: pkiuser3@example.org
firstname: pkiuser3
tokenType: externalRegAddToToken
userPassword:: e1NTSEF9ZXJXMFptMjlKRks5REpkdGRzNk9QQWJtWm5yeHJTK2NjWGpjeXc9PQ=
 =
certstoadd: 58,ca1

Actual results:

audit log messages

0.http-bio-25080-exec-8 - [04/Oct/2016:12:57:37 EDT] [14] [6] [AuditEvent=TOKEN
_AUTH_SUCCESS][IP=10.13.129.54][SubjectID=pkiuser3][CUID=4090614575C1240E0326][
MSN=FF%FF%FF%FF%][Outcome=success][OP=enroll][tokenType=null][AppletVersion=1.4
.54de790f][AuthMgr=ldap1] token authentication success
0.http-bio-25080-exec-8 - [04/Oct/2016:12:57:42 EDT] [14] [6] [[AuditEvent=TOKE
N_KEY_RECOVERY][IP=10.13.129.54][SubjectID=pkiuser3][CUID=4090614575C1240E0326]
[Outcome=success][tokenType=externalRegAddToToken][KeyVersion=0101][Serial=53][
CA_ID=ca1][KRA_ID=kra1][Info=null] token certificate/key recovery request made
0.http-bio-25080-exec-8 - [04/Oct/2016:12:57:42 EDT] [14] [6] [[AuditEvent=TOKE
N_CERT_RETRIEVAL][IP=10.13.129.54][SubjectID=pkiuser3][CUID=4090614575C1240E032
6][Outcome=success][tokenType=externalRegAddToToken][KeyVersion=0101][Serial=53
][CA_ID=ca1][Info=null] token certificate retrieval request made





0.http-bio-25080-exec-9 - [04/Oct/2016:12:58:23 EDT] [14] [6] [AuditEvent=TOKEN
_OP_REQUEST][IP=10.13.129.54][CUID=4090614575C1240E0326][MSN=FF%FF%FF%FF%][Outc
ome=success][OP=enroll][AppletVersion=1.4.54de790f] token processor op request
made
0.http-bio-25080-exec-9 - [04/Oct/2016:12:58:31 EDT] [14] [6] [AuditEvent=TOKEN
_AUTH_SUCCESS][IP=10.13.129.54][SubjectID=pkiuser3][CUID=4090614575C1240E0326][
MSN=FF%FF%FF%FF%][Outcome=success][OP=enroll][tokenType=null][AppletVersion=1.4
.54de790f][AuthMgr=ldap1] token authentication success

Expected results:

Information about the recovered/deleted certs must be logged

Per PKI Bug Council of 10/10/2016: 10.4.0

Per PKI Bug Council of 11/29/2016: 10.4 - critical

Isn't this cert recovered? [Serial=53][CA_ID=ca1]

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

7 years ago

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.5 (was: 10.4)

6 years ago

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

6 years ago

[20171025] - Offline Triage ==> 10.6

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

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

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.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata