Description of problem:
The key recovery should fail with an exception rather than a segmentation fault after disabling the kra.allowEncDecrypt.archival=false and kra.allowEncDecrypt.recovery=false flag. Issue : After disabling the below flag and restart KRA. key recovery should failed but through command but it getting success.
kra.allowEncDecrypt.archival=false
kra.allowEncDecrypt.recovery=false
Version-Release number of selected component (if applicable): 10.5.9-7.el7_6
How reproducible: Disable the kra.allowEncDecrypt.archival=false and kra.allowEncDecrypt.recovery=false flag and retrieve the key through cmd.
Steps to Reproduce: 1.Disable the kra.allowEncDecrypt.archival=false and kra.allowEncDecrypt.recovery=false flag 2.retrieve the key through pki cmd
Actual results: Success
Expected results: Should be failed after disabling the flag.
Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1658031
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=1658031 - Custom field type adjusted to None - Custom field version adjusted to None
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/3258
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)