No info about mapping resolver in audit log messages
pki-tps-10.4.1-10.el7pki.x86_64
always
mappingResolver.enrollProfileMappingResolver.mapping.0.filter.appletMajorVersion=1 mappingResolver.enrollProfileMappingResolver.mapping.0.filter.appletMinorVersion= mappingResolver.enrollProfileMappingResolver.mapping.0.filter.tokenATR= mappingResolver.enrollProfileMappingResolver.mapping.0.filter.tokenCUID.end=10000000000000000000 mappingResolver.enrollProfileMappingResolver.mapping.0.filter.tokenCUID.start=00000000000000000001 mappingResolver.enrollProfileMappingResolver.mapping.0.filter.tokenType=userKey mappingResolver.enrollProfileMappingResolver.mapping.0.target.tokenType=userKey
messages in audit log are as follows
0.http-bio-25080-exec-2 - [15/Aug/2017:15:11:55 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.4.58768072] token processor op request made 0.http-bio-25080-exec-2 - [15/Aug/2017:15:12:06 EDT] [14] [6] [AuditEvent=TOKEN_AUTH_SUCCESS][IP=10.13.129.77][SubjectID=scpuser3][CUID=00050045A702001F0007][MSN=00%00%00%00%][Outcome=success][OP=enroll][tokenType=userKey][AppletVersion=1.4.58768072][AuthMgr=ldap1] token authentication success 0.http-bio-25080-exec-2 - [15/Aug/2017:15:12:09 EDT] [14] [6] [[AuditEvent=TOKEN_CERT_ENROLLMENT][IP=10.13.129.77][SubjectID=scpuser3][CUID=00050045A702001F0007][Outcome=success][tokenType=userKey][KeyVersion=010370][Serial=96388344][CA_ID=ca1][Info=null] token certificate enrollment request made 0.http-bio-25080-exec-2 - [15/Aug/2017:15:12:17 EDT] [14] [6] [[AuditEvent=TOKEN_CERT_ENROLLMENT][IP=10.13.129.77][SubjectID=scpuser3][CUID=00050045A702001F0007][Outcome=success][tokenType=userKey][KeyVersion=010370][Serial=6855785][CA_ID=ca1][Info=null] token certificate enrollment request made
The follwing are the messages in the debug log
[15/Aug/2017:15:11:55][http-bio-25080-exec-2]: TPSProcessor.getResolverInstanceName: entering for operaiton : enroll [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: TPSProcessor.getResolverInstanceName: getting config: op.enroll.mappingResolver [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: TPSProcessor.getResolverInstanceName: returning: enrollProfileMappingResolver [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: TPSProcessor.createFilterMappingParams: after new MappingFilterParams [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: TPSProcessor.createFilterMappingParams: MappingFilterParams set [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: starts [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: param major_version =1 [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: param minor_version =1 [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: param cuid =00050045A702001F0007 [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingParams.getString: param null:fp_ext_keySet [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: OK to not have keySet extension. Continue. [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: mapping params retrieved. [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: getting mapping order:mappingResolver.enrollProfileMappingResolver.mapping.order [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: mapping: 0 [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: mappingConfigName: mappingResolver.enrollProfileMappingResolver.mapping.0.target.tokenType [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: targetMappedName: userKey [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: mappingConfigName: mappingResolver.enrollProfileMappingResolver.mapping.0.filter.tokenType [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: tokenType: userKey [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: mappingConfigName: mappingResolver.enrollProfileMappingResolver.mapping.0.filter.keySet [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: keySet: null [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: mappingConfigName: mappingResolver.enrollProfileMappingResolver.mapping.0.filter.tokenATR [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: tokenATR: [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: mappingConfigName: mappingResolver.enrollProfileMappingResolver.mapping.0.filter.tokenCUID.start [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: tokenCUIDStart: 00000000000000000001 [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: mappingConfigName: mappingResolver.enrollProfileMappingResolver.mapping.0.filter.tokenCUID.end [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: tokenCUIDEnd: 10000000000000000000 [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: mappingConfigName: mappingResolver.enrollProfileMappingResolver.mapping.0.filter.appletMajorVersion [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: majorVersion: 1 [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: mappingConfigName: mappingResolver.enrollProfileMappingResolver.mapping.0.filter.appletMinorVersion [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: minorVersion [15/Aug/2017:15:11:55][http-bio-25080-exec-2]: FilterMappingResolver.getResolvedMapping for tokenType: Selected mapped name: userKey
It would be good to have some info in the audit log that shows which mapping resolver was selected for the operation
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=1481813 - 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/3300
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.