dogtagpki

#3051 getCRL returns 200 on error
Closed: migrated by dmoluguw. Opened by vakwetu.

Closed: migrated
Reopen Issue

Recently we had a case where getCRL was being called (from IPA in an openstack context) without an op=X parameter. This results in a 200 return code with an error message provided in the returned message.

This is confusing, and led to a lot of needless debugging.

What should happen is :
1. The servlet should return a 40x error code
2. Information should be written in the debug log
3. Do we even need this op=X parameter?

Alternatively, a RESTful alternative should be provided that behaves properly, and IPA should use this instead in their rewrite rules.

Metadata Update from @mharmsen:
- 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 set to the milestone: 0.0 NEEDS_TRIAGE

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/3169

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)
Metadata
None
None
None
None
None
None
None
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.