After the SubjectAltNameCopyCNDefault profile component is available (#1710; see also http://www.freeipa.org/page/V4/RFC_2818_certificate_compliance) we should define a new profile that uses this component to ensure that we issue server certificates that are RFC 2818-compliant.
This new profile should be made the default for Dogtag's own server certificates.
See discussion thread for full details: https://www.redhat.com/archives/pki-devel/2016-March/msg00036.html
On 03/23/2016, mharmsen conferred with ftweedal over IRC, and it was determined that this was not urgent enough to fix in the 10.3 timeframe.
Metadata Update from @ftweedal: - Issue assigned to 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/2353
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.