#1181 CA: subject dn for ssl server cert
Closed: wontfix by ftweedal. Opened by saipandi.

I am testing on CA on fedora 20. So if I configure the ca's ssl_server_cert_subject_dn to be some random value other than cn=hostname, the installation goes through fine and I can access the web page on firefox browser as well but wget does not work. It gives a warning that the accepted cn=hostname but it sees cn=configured value.

Thus, this doesn't work on all tools for accessing the web page and hence there should be a check for cn=hostname for ssl server certificate and the installation should not go through fine if the parameter is configured incorrectly.


Metadata Update from @saipandi:
- Issue set to the milestone: UNTRIAGED

Going to close this as WONTFIX. Overriding ssl_server_cert_subject_dn to a value other
than the hostname is going to cause problems with certificate validation. The knob should
not be changed, and there is no good reason to change it. But I don't see it as a high priority to
do anything about this, given we have so much else to do.

If anyone disagrees please reopen or dicsuss.

Metadata Update from @ftweedal:
- Custom field feature adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

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/1744

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.

Metadata