Uploaded image for project: 'WSS4J'
  1. WSS4J
  2. WSS-507

ThreadLocal based Security Provider proxy

    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.2
    • Component/s: WSS4J Core
    • Labels:
      None

      Description

      This feature request is about adding a mechanism for making WSS4J (and possibly other projects relying on it) transparently use a Security Provider without globally installing it the JVM. This prevents side effects on other frameworks running within the same JVM and not wanting the BouncyCastle provider currently registered by WSS4J.
      The idea is to register a provider acting as a proxy to a different and thread local scoped provider. The proxied provider reference would have to be set and cleaned up by the WSS4J consumers. The reference being thread local ensures different threads don't have access to it. When no proxied provider is set, the installed provider basically serves no algorithm / service.

        Attachments

        1. proposal.diff
          8 kB
          Alessio Soldano

          Issue Links

            Activity

              People

              • Assignee:
                coheigea Colm O hEigeartaigh
                Reporter:
                asoldano Alessio Soldano
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: