How do you consume a SOAP web service with TLS?

• A. Install a separate TLS proxy in front of the service.
• B. Configure TLS in the REST client.
• C. Add TLS configuration to WSC connector pom configuration.
• D. Disable TLS for testing.

Answer: (C)

Consuming a SOAP service secured with TLS requires setting up client-side TLS on the SOAP client. The Web Service Consumer is the SOAP client in Mule, so TLS must be configured for that connector. You create a TLS context (including your truststore, and, if needed, a keystore and client certificate) and attach that TLS context to the Web Service Consumer configuration. This ensures the HTTPS handshake with the service uses the proper certificates and validation.

This approach is the correct one because it directly configures transport security for the SOAP call itself. Using a separate TLS proxy adds extra hops without configuring the client properly, TLS settings for REST are not applied to SOAP, and turning TLS off for testing defeats the purpose of TLS.