Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-3463

Allow programmatic injection of TLSClientParameters, before an HTTPConduit is created.

    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Not A Problem
    • Affects Version/s: 2.3.4
    • Fix Version/s: None
    • Component/s: Configuration, Core
    • Labels:
      None
    • Environment:

      Embedded jetty and CXF installation, but without using Spring configuration. Connecting to an HTTPS SOAP service.

      Description

      With programmatic configuration:

      Allow for the creation and injection of a default set of TLSClientParameters to be set, which will be used by all HTTPConduits. This could be accomplished, for example, through a call to

      BusFactory.getDefaultBus().setExtension(myDefaultTlsClientParamters, TLSClientParameters.class);

      Reason:

      When trying to connect to a SOAP service over HTTPS, the HTTPConduit created only uses the default TLSClientParameters. This causes a connection failure (evidenced by a WSDL parsing exception), if there are any specific requirements needed to make the SSL connection (for example, specific cipher suites).

      This can be worked around by implementing both ConduitInitiatorManager and ConduitInitiator wrappers, which can set the TLSClientParamters as needed before the HTTPConduit is returned for usage. However, this is a bit unwieldy, as well as creates set of classes whose reasons for existence may be unclear to developers not familiar with their creation.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              peter.schwarz Peter Schwarz
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: