#3146 Support for ca-profile-mod with multiple userExtensionDefaultImpl
Closed: migrated 3 years ago by dmoluguw. Opened 4 years ago by cipherboy.

Created attachment 1458553 [details]
profile.xml

Description of problem:

In current case, If we have more than one userExtensionDefaultImpl
ca-profile-mod doesn't work and failed with:

[12/Jul/2018:15:59:42][http-bio-8443-exec-13]: BasicProfile: createProfilePolicy:  config created.
[12/Jul/2018:15:59:42][http-bio-8443-exec-13]: BasicProfile: createProfilePolicy: ends
[12/Jul/2018:15:59:42][http-bio-8443-exec-13]: BasicProfile: createProfilePolicy: begins
[12/Jul/2018:15:59:42][http-bio-8443-exec-13]: WARNING attempt to add duplicate Policy userExtensionDefaultImpl:noConstraintImpl Contact System Administrator.
[12/Jul/2018:15:59:42][http-bio-8443-exec-13]: SignedAuditLogger: event CONFIG_CERT_PROFILE
[12/Jul/2018:15:59:42][http-bio-8443-exec-13]: changeProfileData: Error changing profile inputs/outputs/policies: Attempt to add duplicate Policy : userExtensionDefaultImpl:noConstraintImpl

Note: This feature can be a requirement for lab as they wanted to include many certificate request extensions.

--- Workaround--Use ca-profile-edit instead of ca-profile-mod

Version-Release number of selected component (if applicable):

pki-ca-10.5.1-13.1.el7_5.noarch

How reproducible:

always

Steps to Reproduce:
1. Use the profile_1.xml and try to perform ca-profile-mod operation.
2.
3.

Actual results:

Failures in ca-profile-mod when more than one userExtensionDefaultImpl:noConstraintImpl exist in a profile

Expected results:

Should work like the way mod works with other regular profiles.

Additional info:


Metadata Update from @cipherboy:
- 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=1600708
- Custom field type adjusted to None
- Custom field version adjusted to None

4 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/3263

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