TEC Workbook - IBM

IBM Software
__17. For Incoming WSS, select: DecryptAndVerify
__18. Click the Aut button to hide the authorization security settings.
__19. Click the green submit button to submit the request to ProductServiceProxy. Look closely at the
response. This time, soapUI was able to decrypt the contents of the SOAP body.
__20. Look back at the probe window; click the Refresh button. You should see two transactions in the
list. Feel free to inspect the new transactions that include the encryption steps.
3.3.2 Field Level Encryption
In the previous steps, you saw how to encrypt the entire SOAP body. In some circumstances, it may be
preferable to encrypt only specific elements.
Now you’ll modify the encrypt action so that only the tag will be encrypted.
__1. Reopen the policy editor by clicking on the ellipsis button in the Multi-Protocol Gateway Policy
field.
__2. In the configured rules section at the bottom, click on the Server to Client rule to make it the
active rule in the editor.
__3. Double click the encrypt action to open its configuration settings.
__4. In the Message Type section, choose Selected Elements (Field-Level). When you make this
selection, a new field, Document Crypto Map will appear.
The Document Crypto Map is used to tell the encrypt action which element(s) are to be encrypted. Since
the document will be in XML, the most natural way of selecting the target elements is with XPath
expressions. The Document Crypto Map represents a collection of XPath expressions which identify the
elements to be encrypted.
__5. Click the plus (+) button next to the Document Crypto Map dropdown.
__6. For the Name field, type: MyCryptoMap
__7. For the Operation, make sure Encrypt (WS-Security) is selected.
__8. In the XPath Expression field, type: //*[local-name()='benefits']
__9. Click the Add button to add this XPath to the list of expressions.
__10. Click the Apply button.
Page 66 WebSphere Lab Jam