+

Search Tips   |   Advanced Search

Secure messages at the request generator using WSS APIs


We can secure SOAP messages by configuring signing information, encryption, and generator tokens to protect message integrity, confidentiality, and authenticity, respectively. This request (client-side) generator configuration defines the WS-Security requirements for the outgoing SOAP message request.

To secure Web services with WAS, configure the generator and the consumer security constraints. Therefore, in addition to securing messages at the request generator level, also secure messages at the response consumer level.

The request (client-side) generator configuration requirements involve generating a SOAP message request that uses a digital signature, incorporates encryption, and attaches security tokens.

To secure Web service applications, specify several different configurations. Although there is no specific sequence to specify these different configurations, some configurations reference other configurations. For example, decryption configurations reference encryption configurations. Use the following interfaces to configure Web services security and to define policy types to secure the SOAP messages:

The following high-level steps use the WSS APIs:

 

 

Results

After completing these procedures, we have secured messages at the request generator level.

 

Next steps

Next, if not already configured, secure messages with signature verification, decryption, and consumer tokens at the response consumer (client-side) level.


Set encryption to protect message confidentiality using the WSS APIs
Set generator signing information to protect message integrity using the WSS APIs
Attach the generator token using WSS APIs to protect message authenticity

 

Related tasks


Secure messages at the response consumer using WSS APIs
Secure Web services applications using the WSS APIs at the message level