This KB article addresses the following issues that may be encountered when using Secure Sockets Layer (SSL) with Release Control: Web service/orchestration calls fail with the error "The https URL hostname does not match the Common Name (CN) on the server certificate" After configuring 2-way SSL, the execution links for manual deployment tasks fail.
When using SSO and http, if the user goes to http://server/tmtrack/tmtrack.dll, they will be redirected to https . However, users may be prompted and told that non-secure content is being used. As an example, the user may get this Security Warning
This has been seen in customers running HTTPS calls through Load Balancers and redirectors. If the same reports are viewed in the SRP shell, they are seen correctly. The problem also happened only on a single system and not on any others similarly configured.
The combination of a redirect to an alias name and using SSL is causing Static Diagnostics to give an error: HTTPS port 443 (IIS): The remote server returned an error: (401) Unauthorized
"Do you want to view only the webpage content that was delivered securely? This webpage contains content that will not be delivered using a secure HTTPS connection, which could compromise the security of the entire webpage."
