Once a self signed certificate is added to the Security - SSL Integrations section in configurator you can not over write it again later using Configurator.
When using SSL , it is imperative that the SBM server components can verify trusted status of an SSL certificate . This could be any URL or web service that communicates via SSL/HTTPS, such as a secure mail server or an orchestration endpoint etc. To verify the trusted status of a certificate, you must put all the certificate authority (CA) public keys from the certificate signing chain into the trusted certificate store. For
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.
If you have a custom certificate provided by a local authority then once you apply it to IIS via configurator UI it works fine but.... Any subsquent changes to configurator come back with an error within the configurator dialog "Error while applying IIS SSL settings" once they are applied. The logs stated "A specified login session does not exist.
In Configurator, on the Component Server view, for the Application Engine (AE) component, uncheck the HTTP option so only the HTTPS option is checked. However, for this to work correctly, the AE host name must also match the "Issued To" name of the certificate in Configurator on the IIS Server view.
Import the Certificate Authority chain that signed your SQL Server SSL certificate into the Windows Certificate Store. Open the SBM Configurator and add either ";ssl=require or ";ssl=request
Promotions and deploys fail with errors such as:ERROR -- Failed to obtain security token: Web Services "http:// /gsoap/gsoap_ ssl .dll?sbminternalservices72" returned an error: "soap_wsse_verify_X509" Important:
