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

# WSS Module

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

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

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

## Audience

- New user

  To create your Mule app, see:

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

  - [Examples](https://docs.mulesoft.com/wss-module/1.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/1.1/wss-xml-maven)

  - [Examples](https://docs.mulesoft.com/wss-module/1.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/1.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)