It has become clear that we need to be more flexible to allow better configuration of the SubjectAlterNameExtension. This feature request is to allow admins to configure so that the user-supplied SAN within the CSR can be merged with the default ones specified in the profile.
there is also a request to allow the cn component to be copied into one of the SAN's. We could add that as well.
Per CS/DS Meeting of 11/24/2014 - 10.3
Stumbled across this whilst trying to find out why the SANs in my CSR were being lost/dropped when using the "Manual Server Certificate Enrollment" web inteface (10.2.0 on a fresh Fedora21, straight from repos). Does this affect all of the dog tags endpoints (ie. webUI, REST API + CLI)?
Whilst i'm here, I'd like to say thanks for all your hardwork and dedication on this product; I've looked at several alternatives, and this is the only one which is both feature rich, and simple to deploy. Nice job!
Metadata Update from @cfu: - 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/1738
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.