WS-SecurityPolicy 1.2 Actions
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 authentication actions to verify that the requests for virtual services contain a specified WS-SecurityPolicy element. Mediator provides the following actions:
Require WSS SAML Token: Requires that a WSS Security Assertion Markup Language (SAML) assertion token be present in the message header to validate to validate service consumers.
Require WSS Username Token: Requires that a WSS username token and password be present in the message header to validate service consumers.
Require WSS X.509 Token: Requires that a WSS X.509 token be present in the message header 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. Mediator provides the following actions:
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.