As of SBM 11.3, it doesn't look possible to remove TLS 1.0 from both the Server.xml ( Tomcat ) and the SChannel Registry key ( IIS ) and have deploys reach the "Completed" status. The deploy itself will succeed and your changes will get deployed. It is just the callback from the Application Engine to the Repository telling the system the deploy completed that fails so the status stays in "Waiting" forever.
for Client TLS in IIS and Tomcat , you may prevent SBM from talking to other servers / programs. for Server TLS in IIS and Tomcat, you may prevent other programs from talking to SBM. Here is how we should proceed to verify on the test server.
Summary You can now select the Java TLS provider of your choice, including the OpenJSSE Provider , which enables you to select TLS 1.3 with Tomcat . TLS configuration improvements (ENH326186)
3. Define Outgoing TLS Rule for Jenkins Secure Port Similarly, a TLS rule will also be required for outgoing communication from the Tomcat task to the Jenkins Server. NOTE: Some of the entries referenced below have already been defined
