#2493 keySetMappingResolver is not listed under the profile mapping list on UI and cli
Closed: migrated 3 years ago by dmoluguw. Opened 7 years ago by rpattath.

keySetMappingResolver is not listed under the profile mapping list on UI and
cli

Steps to Reproduce:

1. On TPS Web UI keySetMappingResolver is not listed under Profile Mappings
page

2.[root@nocp4 certsdb]# pki -d . -c redhat -n "PKI TPS Administrator for
Example.Org" -h localhost -p 25080 tps-profile-mapping-find
WARNING: BAD_CERT_DOMAIN encountered on 'CN=nocp4.idm.lab.eng.rdu2.redhat.com,O
U=pki-tps-rpattath-Sep23-2016,O=idm.lab.eng.rdu2.redhat.com Security Domain'
indicates a common-name mismatch
-----------------
3 entries matched
-----------------
  Profile Mapping ID: enrollProfileMappingResolver
  Status: Enabled

  Profile Mapping ID: formatProfileMappingResolver
  Status: Enabled

  Profile Mapping ID: pinResetProfileMappingResolver
  Status: Enabled

Additional info:

In TPS CS.cfg the mapping exists in

mappingResolver.list=formatProfileMappingResolver,enrollProfileMappingResolver,
pinResetProfileMappingResolver,keySetMappingResolver

but not in

target.Profile_Mappings.list=enrollProfileMappingResolver,formatProfileMappingR
esolver,pinResetProfileMappingResolver

Per PKI Bug Council Meeting of 10/04/2016: 10.4

  • consider merging the two lists in order to fix this

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

7 years ago

Metadata Update from @mharmsen:
- Custom field feature adjusted to ''
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field version adjusted to ''
- Issue close_status updated to: None
- Issue set to the milestone: 10.4 (was: UNTRIAGED)

7 years ago

Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.

Metadata Update from @mharmsen:
- Issue set to the milestone: FUTURE (was: 10.4)

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

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