We should look through a number of the current PKI related RFCs to see if there is functionality we should bring up to date to match the standards. Some specific areas we should look at are:
We also know that there are some specific areas to investigate, like dealing with different subject encodings, so we should focus on the areas where we know we are not up to the latest standard.
The goal is not to add functionality for everything found in the RFCs. We want to make sure our existing functionality and features follow the standards. If there is functionality defined in the standards that we do not have, we should evaluate if there is a strong use-case and need for us to add that functionality. We should file separate tickets for functionality that we need to bring up to date as we do this investigation.
Here is a preliminary list of SCEP desired enhancements and fixes grouped in categories:
Here is a preliminary list of CRL desired enhancements and fixes grouped in categories:
Here is a preliminary list of CRMF desired enhancements and fixes:
Metadata Update from @nkinder:
- Issue assigned to awnuk
- Issue set to the milestone: 10.1 - 06/13 (June)
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:
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.
to comment on this ticket.