MID Server certificate check fails with message "No subject alternative names"Issue When a MID Server makes an HTTP request, it performs certificate checks as defined in the MID security policy. The Hostname check compares the certificate's Subject Alternative Names with the URL used in the HTTP request.If the MID Server makes an HTTP request to an IP address instead of FQDN, it may fail with one of the following errors:No subject alternative names matching IP address <ip> foundNo subject alternative names presentSymptomsThis could impact Discovery because it often connects with IP address. Other functionality can also be impacted, such as REST messages.ReleaseAllCauseThe Subject Alternative Names in the certificate do not contain an entry for the IP address used in the HTTP request.Please note that SAN entries in certificates have a datatype and IP address must use an IP address datatype. If IP address is added with any incorrect datatype, like: DNS, it will not be correctly evaluated. Resolution1. Generate a new certificate with the IP address in the Subject Alternative Names. 2. Ensure that the SAN data type is set to IP address type. 3. Deploy the new certificate to the target.4. Test the functionality to confirm that the issue is resolved.