(Related to #1035 and #1212)
With #1035 having been addressed to perform the path length constraints sanity check properly, in the event that the path length constraints are actually invalid, the error com.netscape.certsrv.base.PKIException: Error changing profile data is reported (as before) but the profile is still added (as before).
com.netscape.certsrv.base.PKIException: Error changing profile data
Steps to reproduce are as per #1035, but using an obviously invalid configuration, e.g. basicConstraintsMaxPathLen=foo
basicConstraintsMaxPathLen=foo
The profile should not be added when it contains invalid configuration.
This issue could be more general than just BasicConstraintsExtConstraint or even EnrollConstraint and if this is the case, the general problem should be fixed.
BasicConstraintsExtConstraint
EnrollConstraint
Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2 Backlog
Per 10.2.3 TRIAGE meeting of 02/26/2015: 10.3
NOTE: Moved from 10.2 Backlog since it was not a documentation/man page issue.
Metadata Update from @ftweedal: - Issue set to the milestone: UNTRIAGED
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/1777
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.