I seem to have noticed that creating a signed cert w/ a C-Name as the common name rather than the master node's A-record causes me to get cert errors even though the cert is valid. Doing the reverse ends up w/ the same result.
The only time the cert shows as 'valid' is when I connect to the master node via it's IP or A record shown @ the consoles login screen. Is this normal behavior? I feel that it may be a bug as I did not see these issues w/ 5.8.
For example:
Master Node IP: 192.168.1.50
Master Node A Record: vropsmaster-node.localdom.com
Master Node C Name: vrops.localdom.com
Certificate Info:
Common Name: vrops.localdom.com
Subject Alternative Name(s):
DNS: vropsmaster-node.localdom.com
IP: 192.168.1.50
In this case, vropsmaster-node.localdom.com and 192.168.1.50 come back as having valid certificates. Trying to connect to vrops.localdom.com has Chrome, IE, and Safari returning with host name mismatch errors for the cert. Screenshot from Safari attached.