#3018 CMC profiles: Some CMC profiles have wrong input class_id
Closed: fixed 5 years ago Opened 5 years ago by cfu.

It appears that some CMC profiles point to
input.i1.class_id=certReqInputImpl
instead of
input.i1.class_id=cmcCertReqInputImpl

Although programatically requests are handled correctly, it is confusing when documenting.
Should also inveatigate the usefulness of
input.i2.class_id=submitterInfoInputImpl
and get rid of that as that doesn't look like something needed or even allowed.


Metadata Update from @cfu:
- Custom field component adjusted to CMC
- 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=1576151
- Custom field type adjusted to defect
- Custom field version adjusted to None
- Issue set to the milestone: 10.5

5 years ago

Metadata Update from @cfu:
- Issue assigned to cfu

5 years ago

Per 10.5.x/10.6 Triage: 10.5

Metadata Update from @mharmsen:
- Issue priority set to: critical

5 years ago

commit 3c020c16de373752c746d5f00f3fa60428fff65f
Author: Christina Fu cfu@redhat.com
Date: Wed May 16 14:52:21 2018 -0700

Ticket 3018 CMC profiles: Some CMC profiles have wrong input class_id

This patch fixes the profile input area where
cmcCertReqInputImpl should replace certReqInputImpl
and submitterInfoInputImpl should not be present

fixes https://pagure.io/dogtagpki/issue/3018

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

5 years ago

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

5 years ago

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.5.8-1.fc27

5 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/3136

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.

Login to comment on this ticket.

Metadata