Currently the CA provides separate CMC servlets with different URLs for all profiles that it supports. The profile ID is stored as servlet parameter in the web.xml. To support a new profile, the web.xml has to be customized to add a new servlet for the new profile.
To improve usability there should be a single CMC servlet that supports any profile requested by the user. The profile ID can be specified as URL query parameter.
Metadata Update from @edewata: - 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 type adjusted to None - Custom field version adjusted to None - Issue priority set to: major - Issue set to the milestone: 10.5
Metadata Update from @edewata: - Issue assigned to edewata
Code review: * https://review.gerrithub.io/#/c/379577/
Fixed in master: * https://github.com/dogtagpki/pki/commit/9e33fcc37547997d74c6325192b3fbacc03391ce
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue set to the milestone: 10.5.0 (was: 10.5) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.5.0-1.fc27
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/2935
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.
Login to comment on this ticket.