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

Custom SSLContext using async http-client5 does not work

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • 3.4.6, 3.5.1
    • 3.5.2, 3.4.7, 4.0.0
    • Transports
    • None
    • Unknown

    Description

      AsyncHTTPConduit configures httpclient5 tlsstrategy here

      however this configuration is actually never used. Instead, the http-client5 is always built using the system default TlsStrategy here

      The result is that custom SSLContext configured in the httpconduit is not honored.

      The current workaround is to keep using cxf-rt-transports-http-hc, or force using the sync httpclient.

      I did a quick test propagating the RegistryBuilder<TlsStrategy> built at AsyncHTTPConduit up until the httpclient is built and the custom SSLContext started being used.

      Attachments

        Issue Links

        relates to

        Bug - A problem which impairs or prevents the functions of the product. CXF-8667 Custom certificate alias not being used when using HC5 AsyncHTTPConduit

        • Major - Major loss of function.
        • Resolved

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            fernandosci Fernando Soares Carnevale Ito
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment