No audit log messages when token enrollment fails when the ldap user has a different CUID
pki-tps-10.4.1-10.el7pki.x86_64
always
dn: uid=pkiuser1,dc=lab,dc=eng,dc=pnq,dc=redhat,dc=com objectClass: person objectClass: organizationalPerson objectClass: inetorgperson objectClass: top objectClass: extensibleobject cn: pkiuser1 sn: pkiuser1 uid: pkiuser1 givenName: pkiuser1 mail: pkiuser1@example.org firstname: pkiuser1 edipi: 123456789 pcc: AA exec-edipi: 999999999 exec-pcc: BB exec-mail: pkiuser1@EXAMPLE.com certstoadd: 67,ca1,19,kra1 certsToAdd: 86,ca1,24,kra1 certsToAdd: 88,ca1,25,kra1 tokenCUID: 409061457E9127120B2A
2.Token used has a different CUID
Key recovery fails but no failure messages in the audit log
0.http-bio-25080-exec-12 - [22/Aug/2017:08:58:27 EDT] [14] [6] [AuditEvent=TOKEN_OP_REQUEST][IP=10.13.129.77][CUID=00050045A702001F0007][MSN=00%00%00%00%][Outcome=success][OP=enroll][AppletVersion=1.5.558cdcff] token processor op request made 0.http-bio-25080-exec-12 - [22/Aug/2017:08:58:32 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
debug log
[22/Aug/2017:08:58:32][http-bio-25080-exec-12]: In LdapBoundConnFactory::getConn() [22/Aug/2017:08:58:32][http-bio-25080-exec-12]: masterConn is connected: true [22/Aug/2017:08:58:32][http-bio-25080-exec-12]: getConn: conn is connected true [22/Aug/2017:08:58:32][http-bio-25080-exec-12]: getConn: mNumConns now 2 [22/Aug/2017:08:58:32][http-bio-25080-exec-12]: LDAPDatabase: adding cn=20170822085832921000.2d,ou=Activities,o=pki-tps-Aug11-TPS [22/Aug/2017:08:58:32][http-bio-25080-exec-12]: returnConn: mNumConns now 3 [22/Aug/2017:08:58:32][http-bio-25080-exec-12]: TPSSession.process: Message processing failed: isExternalReg: token CUID not matching record:00050045A702001F0007 : 00050045A702001F0001 [22/Aug/2017:08:58:32][http-bio-25080-exec-12]: TPSConnection.write: Writing: s=43&msg_type=13&operation=1&result=1&message=43 [22/Aug/2017:08:58:32][http-bio-25080-exec-12]: TPSSession.process: leaving: result: 1 status: STATUS_ERROR_NOT_TOKEN_OWNER [22/Aug/2017:08:58:32][http-bio-25080-exec-12]: After session.process() exiting ..
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=1484012 - 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/3303
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.