#2895 Audit log messages have applet version info that does not match that on the token when using tpsclient tokens
Closed: migrated 3 years ago by dmoluguw. Opened 6 years ago by mharmsen.

Audit log messages have applet version info that does not match that on the token when using tpsclient tokens

Steps to Reproduce:

Enroll a formatted token using tpsclient

Actual results:

----------------------------
Token "10000000000000000001"
----------------------------
  Token ID: 10000000000000000001
  User ID: testuser1
  Type: userKey
  Status: FORMATTED
  Next States: DAMAGED, PERM_LOST, SUSPENDED, TERMINATED
  Applet ID: 1.4.58768072
  Key Info: 0101
  Date Created: Fri Jul 28 13:19:54 EDT 2017
  Date Modified: Fri Jul 28 13:30:13 EDT 2017

When the status of the token is as above, enrollment of the token using tpsclient gives the following audit messages

0.http-bio-25080-exec-12 - [28/Jul/2017:13:37:05 EDT] [14] [6] [AuditEvent=TOKEN_OP_REQUEST][IP=10.19.34.100][CUID=10000000000000000001][MSN=01%02%03%04%][Outcome=success][OP=enroll][AppletVersion=0.0.6fbbc105] token processor op request made
0.http-bio-25080-exec-12 - [28/Jul/2017:13:37:05 EDT] [14] [6] [AuditEvent=TOKEN_AUTH_SUCCESS][IP=10.19.34.100][SubjectID=testuser1][CUID=10000000000000000001][MSN=01%02%03%04%][Outcome=success][OP=enroll][tokenType=userKey][AppletVersion=0.0.6fbbc105][AuthMgr=ldap1] token authentication success
0.http-bio-25080-exec-12 - [28/Jul/2017:13:37:09 EDT] [14] [6] [AuditEvent=TOKEN_APPLET_UPGRADE_SUCCESS][IP=10.19.34.100][SubjectID=testuser1][CUID=10000000000000000001][MSN=01%02%03%04%][Outcome=success][KeyVersion=0101][oldAppletVersion=0.0.6fbbc105][newAppletVersion=1.4.54de790f][Info=null] token applet upgrade success
0.http-bio-25080-exec-12 - [28/Jul/2017:13:37:10 EDT] [14] [6] [[AuditEvent=TOKEN_CERT_ENROLLMENT][IP=10.19.34.100][SubjectID=testuser1][CUID=10000000000000000001][Outcome=success][tokenType=userKey][KeyVersion=0101][Serial=98562365][CA_ID=ca1][Info=null] token certificate enrollment request made
0.http-bio-25080-exec-12 - [28/Jul/2017:13:37:12 EDT] [14] [6] [[AuditEvent=TOKEN_CERT_ENROLLMENT][IP=10.19.34.100][SubjectID=testuser1][CUID=10000000000000000001][Outcome=success][tokenType=userKey][KeyVersion=0101][Serial=13214885][CA_ID=ca1][Info=null] token certificate enrollment request made

Expected results:

oldAppletVersion=1.4.54de790f

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=1476391
- Custom field type adjusted to None
- Custom field version adjusted to None

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

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