Summary of Actions in the WS-SecurityPolicy Category

Mediator provides two kinds of actions that support WS-SecurityPolicy 1.2: authentication actions and XML security actions.

Authentication Actions (WS-SecurityPolicy 1.2)

Mediator uses the following authentication actions to verify that the requests for virtual services contain a specified WS-Security element:

Require WSS Username Token	Uses WS-SecurityPolicy authentication to validate user names and passwords that are transmitted in the SOAP message header for the WSS Username token.
Require WSS X.509 Token	Identifies consumers based on a WSS X.509 token.
Require WSS SAML Token	Uses a WSS Security Assertion Markup Language (SAML) assertion token to validate service consumers.

XML Security Actions (WS-SecurityPolicy 1.2)

These actions provide confidentiality (through encryption) and integrity (through signatures) for request and response messages.

Require Signing	Requires that a request's XML element (which is represented by an XPath expression) be signed.
Require Encryption	Requires that a request's XML element (which is represented by an XPath expression) be encrypted.
Require SSL	Requires that requests be sent through SSL client certificates and can be used by both SOAP and REST services.
Require Timestamps	Requires that timestamps be included in the request header. Mediator checks the timestamp value against the current time to ensure that the request is not an old message. This serves to protect your system against attempts at message tampering, such as replay attacks.