I am new to HTTPs and want to have my web application on secure ports. For this, I asked our security department to issue certificates. And I provided them with the CSRs. The CSRs were generated on FQDNs which are not there in the URL.
For example, FQDN against which the CSR was generated was mywebappserver whereas the URL (which has to be changed to secure port and HTTPs is http://hostname.domain.lan:8080/mywebapp.
My colleague told me that he can set up the HTTPs by adding those certificates but browser will show a warning. Because certificates are generated on an FQDN which is not part of the URL.
Can I have some DNS routing, like: customer will access https://hostname.domain.lan:8443/mywebapp and this will redirect to https://mywebappserver:8443/mywebapp but in browser still customers see https://hostname.domain.lan:8443/mywebapp
Objective is to keep communication over HTTPs without any warning in browser. Is it possible?
PS: I can't get certificates again with correct FQDNs.