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

Allow setting additional Security Provider at Exchange level

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

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.0.2, 3.1
    • Component/s: None
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      This is a follow-up from the CXF dev list thread at http://cxf.547215.n5.nabble.com/On-BouncyCastle-installed-as-a-global-security-provider-td5746785.html and is meant to work with the WSS4J changes at https://issues.apache.org/jira/browse/WSS-507 .
      CXF could allow setting a custom (BouncyCastle) security provider in the message exchange; if provided, that would be set into WSS4J ThreadLocalSecurityProvider (when installed) just before running sensible interceptors, and cleaned up just afterwards.
      Attached is an initial patch; I'm going to figure out the other WS-Security interceptors that need to be modified if this approach is fine.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              asoldano Alessio Soldano
              Reporter:
              asoldano Alessio Soldano

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment