Contact Us 1-800-596-4880

WSS Module - Mule 4

Anypoint WSS module enables you to process and validate an inbound SOAP request against a given Web Service Security (WSS) extension configuration to, for example, validate the request’s signature, perform an LDAP authentication, or decrypt the inbound message. The WSS module also enables you to sign your response by adding a WSS header to it, or to encrypt your outbound message.

For information about compatibility and fixed issues, see WSS Module Release Notes.

Before You Begin

To use this connector, you must be familiar with:

  • The WSS module’s API

  • Anypoint Connectors

  • Mule runtime engine (Mule)

  • Elements and global elements in a Mule flow

  • How to create a Mule app using Anypoint Studio

Before creating an app, you must have access to:

  • The WSS module target resource

  • Anypoint Platform

  • Anypoint Studio version 7.x or later

  • Web Services Security (WSS) extension for SOAP

Common Use Cases For the Connector

The WSS module enables you to validate WSS headers in inbound SOAP requests to your application to:

  • Decrypt a SOAP envelope according to the encryption information

  • Validate a signature

  • Verify the freshness of the message using timestamp information

  • Verify the Username and Password credentials of UsernameToken

  • Verify the LDAP credentials of UsernameToken

  • Determine whether UsernameToken is expired

  • Determine whether a SAML assertion expired

  • Verify the signature of a SAML assertion.

  • Verify that a SAML assertion has a specific confirmation method.

Using the WSS module, you can also add WSS headers to your outbound SOAP response to:

  • Encrypt some or all of your SOAP message content

  • Sign your SOAP message

See the WSS Module Examples section for detailed examples.

Audience

Next Step

After you complete the prerequisites and experiment with templates and examples, you are ready to create an app and configure the connector using Anypoint Studio.

View on GitHub