request related to ticket https://pagure.io/dogtagpki/issue/1316 and community comments in thread at https://www.redhat.com/archives/pki-users/2018-March/msg00007.html
we need to have the CNtoSAN or SAN extension into the internal SSL server certificate by default when pkispawn creates a new instance. an example file with SubjectAltNameExtDefault already exist at /usr/share/pki/ca/conf/serverCert.profile.exampleWithSAN
if there are no particular objections, the SAN config file should be used instead of the current /usr/share/pki/ca/conf/serverCert.profile
it should either have the SubjectAltNameExtDefault or the more recent commonNameToSANDefaultImpl extension (preferred) described at http://www.dogtagpki.org/wiki/PKI_10.4_Copy_CN_To_SAN
bz 1562423 - SAN in internal SSL server certificate in pkispawn configuration step https://bugzilla.redhat.com/show_bug.cgi?id=1562423
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
Metadata Update from @cfu: - Issue assigned to cfu
https://review.gerrithub.io/#/c/dogtagpki/pki/+/411649/
Metadata Update from @cfu: - Assignee reset
looks like this is a duplicate of https://pagure.io/dogtagpki/issue/2995
Closing.
Metadata Update from @cfu: - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5.8 (was: 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/3097
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.
Login to comment on this ticket.