Integrity Lifecycle Manager Client doesn't check the Common Name (CN) of a provided server certificate
Applies To
- PTC RV&S (formerly Integrity Lifecycle Manager) 10.9
Description
- Integrity Client doesn't check the CN of a provided server certificate
- The Integrity Server still allows connecting to a server using TLS, even if the CN of the provided certificate of this server does not match the hostname, which the client used to connect to the server
- The Integrity Client seems to bypass the hostname verification and connects to the server without any warning/error message
- The request if for the Integrity Client to refuse the connection, as the hostname used to connect to the Integrity server does not match the CN of the provided certificate