Class WssInboundConfig

java.lang.Object
com.mulesoft.modules.wss.internal.inbound.WssInboundConfig
All Implemented Interfaces:
org.mule.runtime.api.lifecycle.Disposable, org.mule.runtime.api.lifecycle.Initialisable

@Operations(WssInboundOperations.class) @Configuration(name="inbound") public class WssInboundConfig extends Object implements org.mule.runtime.api.lifecycle.Initialisable, org.mule.runtime.api.lifecycle.Disposable
  • Constructor Details

    • WssInboundConfig

      public WssInboundConfig()
  • Method Details

    • initialise

      public void initialise() throws org.mule.runtime.api.lifecycle.InitialisationException
      Specified by:
      initialise in interface org.mule.runtime.api.lifecycle.Initialisable
      Throws:
      org.mule.runtime.api.lifecycle.InitialisationException
    • getActor

      public String getActor()
    • extractSecurityHeader

      public boolean extractSecurityHeader()
    • dispose

      public void dispose()
      Specified by:
      dispose in interface org.mule.runtime.api.lifecycle.Disposable
    • processSecurity

      public org.apache.wss4j.dom.handler.WSHandlerResult processSecurity(Document envelope)
      Processes the security header of a SOAP envelope. Validates all required security elements and returns the processing result. The synchronized block is intentionally limited to only the engine.processSecurityHeader() call to minimize lock contention under high concurrency. The validateResult() call is thread-safe and does not require synchronization as it only reads from immutable configuration (requiredValidations, VALIDATION_ERROR_CODES) and per-request data (result).
      Parameters:
      envelope - The SOAP envelope to process
      Returns:
      The WSHandlerResult containing the processing results
      Throws:
      WssSecurityException - if security processing fails