--- schema_version: "1" id: 19e27cd76367bb6512217c8f9107c40bc4ad8e5ac9584e351cc61bec68fa2302 title: Validate Operation Examples collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/wss-module/2.0/validate-wss-examples.md canonical_url: https://docs.mulesoft.com/wss-module/2.0/validate-wss-examples source_site: docs.mulesoft.com content_type: documentation content_hash: b97c19dbc5a663b6e4155e3a1819dc795d8160d64095802128f1b8b3002a7fa5 description: MuleSoft Documentation Site release: "2.0" latest: false --- --- product: WSS Module version: 2.0 --- # Validate Operation Examples > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This `validate` operation validates an incoming SOAP request that contains WSS information. The WSS module validates the request against a `WssInboundConfig` configuration.

Table 1. Parameters
Name	M	ES	Default Value	Type	Description
`request`	Yes	No	n.a.	`TypedValue <InputStream>`	SOAP request
`version`	No	No	`SOAP_12`	`SoapVersion`	SOAP protocol version

The output is the same SOAP request received. The operation does not return any attributes.

Table 2. Errors
Namespace	Type	Parent	Description
WSS	SECURITY_VALIDATING	n.a.	Thrown when the request is not valid or no WS-Security information is found
WSS	MISSING_CERTIFICATE	n.a.	Thrown when unable to get a certificate from either the truststore or the keystore

## Decryption > [!NOTE] Do not apply transformations to your message’s payload when performing cryptographic > operations. Transform operations don’t exclude cryptographic signatures. This example shows you how to decrpyt a request using a keystore: Request Example ```XML CN=OLEKSIYS-W3T,OU=Sun Java System Application Server,O=Sun Microsystems,L=Santa Clara,ST=California,C=US1182300426xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx= xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx= ``` Multipart Request Example ```XML ------=_Part_8049_2119795515.1555963425591 Content-Type: application/soap+xml Content-ID: main CN=OLEKSIYS-W3T,OU=Sun Java System Application Server,O=Sun Microsystems,L=Santa Clara,ST=California,C=US1182300426xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx= xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/xxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx= ------=_Part_8049_2119795515.1555963425591 Content-Type: application/json Content-Disposition: related; name="file1"; filename="a.json" Content-ID: file1 { "title": "Java in Action", "author": "Mario Fusco", "year": 2014 } ------=_Part_8049_2119795515.1555963425591-- ``` Decryption Example ```XML

``` ## UsernameToken Validation > [!NOTE] Do not apply transformations to your message’s payload when performing cryptographic > operations. Transform operations don’t exclude cryptographic signatures. The following examples show you how to validate against either an [LDAP server](#ldap-validate) or a provided [username/password credentials pair](#username-password). Use LDAP authentication to validate multiple users. Credentials validation does not support validation of multiple users. ### LDAP Authentication This example shows `usernameToken` validation against an LDAP server. The username and password from the request are validated in the LDAP server. Request Example ```XML username password test username ``` Validation Example ```XML

``` ### Credentials Authentication This example shows a `usernameToken` validation against a configured pair of username and password: Request Example ```XML username username test username ``` Multipart Request Example ```XML ------=_Part_8049_2119795515.1555963425591 Content-Type: application/soap+xml Content-ID: main username username test username ------=_Part_8049_2119795515.1555963425591 Content-Type: application/json Content-Disposition: related; name="file1"; filename="a.json" Content-ID: file1 { "title": "Java in Action", "author": "Mario Fusco", "year": 2014 } ------=_Part_8049_2119795515.1555963425591-- ``` Validation Example ```XML

``` ## Validate Signature The following examples show you how to validate signatures in your incoming requests against a configured [trustore](#validate-trustore-signature), a [binary security token](#validate-binary-security-token), or a [X.509 certificate](#validate-x509-certificate). ### Trustore > [!NOTE] Do not apply transformations to your message’s payload when performing cryptographic > operations. Transform operations don’t exclude cryptographic signatures. Example of validation of the request signature against a configured truststore to ensure that only valid messages from trusted senders are received: Request Example ```XML yLFLEkH4/MjYbZ4viZxjou9/4os=xxxxxxx+xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxX+xxxxxxxxxxxxxxxxxxxx/xxxxxxxx xxxxxxx/xxxxxxxxxx xxxxxxxx+xxx/xxxxxxxxxxx==CN=Unknown,OU=Unknown,O=Unknown,L=Unknown,ST=Unknown,C=US1545521240 test ``` Validation Example ```XML

``` ### BinarySecurityToken Signature > [!NOTE] Do not apply transformations to your message’s payload when performing cryptographic > operations. Transform operations don’t exclude cryptographic signatures. Example of validation against the truststore of a request signed with a binary security token. Request Example ```XML xxxxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxx+xxxxxx/xxxxxxxxxxxxxxH/d9uuvKNSGhJPNoJtm1DhWBQmI=xxxxxxxxx+xxxx/xxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx== ? ? ? ? ? ? ? ? ? ? ``` Validation Example ```XML

``` ### X.509 Certificate > [!NOTE] Do not apply transformations to your message’s payload when performing cryptographic > operations. Transform operations don’t exclude cryptographic signatures. The following example shows validation of an X.509 certificate issuer by pattern: Request Example ```XML yLFLEkH4/MjYbZ4viZxjou9/4os=xxxxxxxxxxx==CN=Unknown,OU=Unknown,O=Unknown,L=Unknown,ST=Unknown,C=US1545521240 test ``` Validation Example ```XML

``` ## Validate Timestamp > [!NOTE] Do not apply transformations to your message’s payload when performing cryptographic > operations. Transform operations don’t exclude cryptographic signatures. This example shows you how to validate the `` element in your incoming SOAP requests: Request Example ```XML 2001-09-13T08:42:00Z 2001-10-13T09:00:00Z test timestamp ``` Timestamp Validation Example ```XML

``` ## Validate SAML The following examples show you how to validate both [signed](#signed-saml) or [unsigned](#unsigned-saml) SAML assertions in your incoming SOAP requests. ### Signed SAML Assertion > [!NOTE] Do not apply transformations to your message’s payload when performing cryptographic > operations. Transform operations don’t exclude cryptographic signatures. Example of a signed SAML assertion that requires the `Subject Confirmation Method` to be `Bearer`: Request Example ```XML WssTestxX+xxxxxxxxxx=mT9648OrsRiYV/xxxx/xxxxxxxx/xxxxxx==CN=Unknown,OU=Unknown,O=Unknown,L=Unknown,ST=Unknown,C=USxxxxxxxxxxxx+xxxxxxxxxxxxxxxxxx=o=test test ``` Signed SAML Assertion Validation Example ```XML

``` ### Unsigned SAML Assertion > [!NOTE] Do not apply transformations to your message’s payload when performing cryptographic > operations. Transform operations don’t exclude cryptographic signatures. Example of SAML assertion of unsigned SOAP message: Request Example ```XML WssTesto=test test ``` Unsigned SAML Assertion Validation Example ```XML

```