---
schema_version: "1"
id: e170fc4ffc328c9bc6df2683e42996ad25f8283c61489ae59c0b16920bd7ce03
title: WSS Module 2.1
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/wss-module/2.1/index.md
canonical_url: https://docs.mulesoft.com/wss-module/2.1/
source_site: docs.mulesoft.com
content_type: documentation
content_hash: d4b838e177cadadf4154d2ae0c85dd99c7c6df56ef99d5baadd931ef3f96e6e8
description: MuleSoft Documentation Site
release: "2.1"
latest: false
---
---
product: WSS Module
version: 2.1
---

# WSS Module 2.1

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

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. WSS Module also enables you to sign your
response by adding a WSS header to it, or to encrypt your outbound message.

In version 2.1, the module upgrades the default hashing algorithm from SHA-1 to SHA-256 to enhance
cryptographic security and align with FIPS 140-3 approved standards.

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

## Before You Begin

To use this connector, you must be familiar with:

- The WSS Module 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 or Anypoint Code Builder

- Web Services Security (WSS) extension for SOAP

## Common Use Cases for the Connector

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 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](https://docs.mulesoft.com/wss-module/2.1/wss-examples) section for detailed examples.

## Audience

- New user

  To create your Mule app, see:

  - [Studio Configuration](https://docs.mulesoft.com/wss-module/2.1/wss-studio) to help extend your understanding of WSS Module.

  - [Examples](https://docs.mulesoft.com/wss-module/2.1/wss-examples), with use case information for the connector

- Advanced user

  Read the following:

  - [XML and Maven Support](https://docs.mulesoft.com/wss-module/2.1/wss-xml-maven)

  - [Examples](https://docs.mulesoft.com/wss-module/2.1/wss-examples), with use case information for the connector

## 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](https://docs.mulesoft.com/wss-module/2.1/wss-studio).

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Use Exchange to Discover Connectors, Templates, and Examples](https://docs.mulesoft.com/connectors/introduction/intro-use-exchange)

- [WSS Module on Exchange](https://www.mulesoft.com/exchange/?search=wss-module&type=connector)

- [Salesforce Help](https://help.salesforce.com)