Integration Server 10.11 | Web Services Developer’s Guide | Securing Web Services Using WS-SecurityPolicy | Policies Based on WS-SecurityPolicy that Integration Server Provides | X509Authentication_Encryption
 
X509Authentication_Encryption
The X509Authentication_Encryption policy uses X509 certificates to provide client authentication, uses asymmetric binding to encrypt messages to ensure message confidentiality, and includes a Timestamp token to guard against replay attacks. This policy does not enforce signatures.
When the policy is attached to:
Message type
To enforce the policy, Integration Server...
Consumer web service descriptor
outbound request
*Adds an X509 token to the security header.
*Adds a signed Timestamp token to the security header. Integration Server determines the timestamp expiration date to specify using the WS Security Properties of the endpoint alias or by using watt.server.ws.security server configuration parameters. For more information, see webMethods Integration Server Administrator’s Guide. Integration Server signs the Timestamp token using the its private key.
*Encrypts the SOAP body of the outbound request message using the server’s certificate.
For details about how Integration Server determines the certificate to use in the X509 token and the certificate to use for encrypting, see Web Service Provider: Response (Outbound Security) Detailed Usage and Resolution Order.
inbound response
*Requires a signed Timestamp token, which Integration Server validates to ensure against replay attacks.
*Requires that the SOAP body of the inbound response be encrypted and decrypts the message. For the resolution order that Integration Server uses to determine the private key it uses for decryption, see Web Service Consumer: Response (Inbound Security) Detailed Usage and Resolution Order.
Provider web service descriptor
inbound request
*Requires an X509 token in the security header. Integration Server authenticates the sender of the inbound request using the X.509 certificate from the security header of the inbound request.
*Requires a signed Timestamp token in the security header, which Integration Server validates to ensure against replay attacks.
*Requires that the SOAP body of the inbound request be encrypted and decrypts the SOAP body. For the resolution order that Integration Server uses to determine the private key it uses for decryption, see Web Service Provider: Request (Inbound Security) Detailed Usage and Resolution Order.
outbound response
*Adds a signed Timestamp token to the security header. Integration Server determines the timestamp expiration date to specify using the WS Security Properties of the endpoint alias or by using watt.server.ws.security server configuration parameters. For more information, see webMethods Integration Server Administrator’s Guide. Integration Server signs the Timestamp token using the its private key.
*Encrypts the SOAP body of the outbound response message using the server’s certificate. For the resolution order that Integration Server uses to determine the certificate it uses for encryption, see Web Service Provider: Response (Outbound Security) Detailed Usage and Resolution Order.