Currently a client can send as many certificate requests as possible to the CA, either intentionally or unintentionally, which may overwhelm the server.
To prevent this problem, the CA should provide an optional mechanism to limit the number of certificate requests that can be submitted over a certain period of time, for example:
Any request that exceeds the limit will be rejected. This will ensure that the server still have resources to perform other tasks.
Per discussions in CS/DS meeting of 02/01/2016: 10.4 major
NOTE: May be pushed out even later.
Per Offline Triage of 11/30/2016-12/01/2016: FUTURE - major
Metadata Update from @edewata: - Issue set to the milestone: FUTURE
Per 10.5.x/10.6 Triage: FUTURE
mharmsen: appears to be a corner case that was discovered and reported by a customer in earlier versions of the product
Metadata Update from @mharmsen: - Custom field feature adjusted to None - Custom field proposedmilestone adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated 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/2308
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.