TEC Workbook - IBM
TEC Workbook - IBM TEC Workbook - IBM
IBM Software __21. In the policy editor, click the Apply Policy button. __22. Click the Close Window link to close the policy editor. __23. Click the Apply button in the Multi-Protocol Gateway configuration page. __24. In the soapUI, click the green submit button to submit the request to your service. The request should now fail with an error message of “Rejected by policy.” To resolve this, you need to tell soapUI to include the WS-Security Usernametoken. __25. In soapUI, make sure the request tab is selected then click the Aut button to show the authentication settings. __26. Change the Outgoing WSS dropdown to be UsrtokenSignEncrypt. __27. Click the Aut button to close the authentication settings. __28. Click the green submit button to submit another request to the service. This time, the request should succeed. If you want to see the WS-Security UsernameToken that soapUI injected into the message, you can use the probe to inspect the transaction. __29. If you want to see the AAA policy reject a bad password, follow these steps: __a. In the soapUI request tab, click on the Aut button to show the authentication settings. __b. Select BadPassword_UNT from the Outgoing WSS dropdown – the password is incorrect for user david. __c. Click the Aut button to hide the authentication settings. __d. Click the green submit button to submit the request. The request should fail with the “Rejected by policy” message. __e. Restore the Outgoing WSS setting back to UsrtokenSignEncrypt and verify that the request succeeds (this is important for future labs). __30. If your configuration is working properly, you can click the Save Config link in the upper right part of the DataPower banner. This will save your configuration to the flash memory. 4.7 Summary In this lab, you saw how you can further secure your services with DataPower’s access control framework. You learned: ● Access Control Policies, also known as AAA policies, are a powerful and flexible way to prevent unauthorized access to your services. Through the point-and-click WebGUI, you can easily configure access policies to contact external authentication and policy servers. ● AAA policies can also do security mediation, such as converting between HTTP Basic Authentication and Kerberos/SPNEGO. AAA policies can also create a SAML assertion based on authenticated credentials extracted from the message. Page 72 WebSphere Lab Jam
Appendix A. Notices This information was developed for products and services offered in the U.S.A. IBM Software IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have Appendix Page 129
- Page 21 and 22: 1.13 Logging IBM Software WebSphere
- Page 23 and 24: ● Trigger a set of actions to occ
- Page 25 and 26: 1.13.4 Appliance management IBM Sof
- Page 27 and 28: 1.13.8 Configuration Comparison, Ch
- Page 29 and 30: Lab 2 Working with XML Prerequisite
- Page 31 and 32: 2.1.5 WebSphere DataPower Configura
- Page 33 and 34: IBM Software It’s also possible t
- Page 35 and 36: Match Rule - evaluate statements us
- Page 37 and 38: IBM Software __18. In the Configure
- Page 39 and 40: IBM Software __2. Expand the policy
- Page 41 and 42: IBM Software __12. In soapUI, click
- Page 43 and 44: IBM Software __3. Click the green s
- Page 45 and 46: The SQL statement would become: SEL
- Page 47 and 48: __2. Click and drag a transform act
- Page 49 and 50: 2.7 Stylesheet Caching IBM Software
- Page 51 and 52: 2.8.3 Virus Scanning IBM Software V
- Page 53 and 54: Lab 3 Securing XML Message Content
- Page 55 and 56: 3.2.2 Create the Crypto Key and Cer
- Page 57 and 58: 3.2.7 Verifying the request signatu
- Page 59 and 60: __8. Click the Close Window link to
- Page 61 and 62: __12. Click on the small [+] to sho
- Page 63 and 64: IBM Software __3. Click on the last
- Page 65 and 66: IBM Software __6. In the list of co
- Page 67 and 68: __11. Click the Done button in the
- Page 69 and 70: Lab 4 Access Control Framework Prer
- Page 71: __3. Double click the yellow outlin
- Page 75 and 76: Appendix B. Trademarks and copyrigh
- Page 77 and 78: NOTES
<strong>IBM</strong> Software<br />
__21. In the policy editor, click the Apply Policy button.<br />
__22. Click the Close Window link to close the policy editor.<br />
__23. Click the Apply button in the Multi-Protocol Gateway configuration page.<br />
__24. In the soapUI, click the green submit button to submit the request to your service. The request<br />
should now fail with an error message of “Rejected by policy.” To resolve this, you need to tell<br />
soapUI to include the WS-Security Usernametoken.<br />
__25. In soapUI, make sure the request tab is selected then click the Aut button to show the<br />
authentication settings.<br />
__26. Change the Outgoing WSS dropdown to be UsrtokenSignEncrypt.<br />
__27. Click the Aut button to close the authentication settings.<br />
__28. Click the green submit button to submit another request to the service. This time, the request<br />
should succeed. If you want to see the WS-Security UsernameToken that soapUI injected into<br />
the message, you can use the probe to inspect the transaction.<br />
__29. If you want to see the AAA policy reject a bad password, follow these steps:<br />
__a. In the soapUI request tab, click on the Aut button to show the authentication settings.<br />
__b. Select BadPassword_UNT from the Outgoing WSS dropdown – the password is incorrect<br />
for user david.<br />
__c. Click the Aut button to hide the authentication settings.<br />
__d. Click the green submit button to submit the request. The request should fail with the<br />
“Rejected by policy” message.<br />
__e. Restore the Outgoing WSS setting back to UsrtokenSignEncrypt and verify that the<br />
request succeeds (this is important for future labs).<br />
__30. If your configuration is working properly, you can click the Save Config link in the upper right part<br />
of the DataPower banner. This will save your configuration to the flash memory.<br />
4.7 Summary<br />
In this lab, you saw how you can further secure your services with DataPower’s access control<br />
framework. You learned:<br />
● Access Control Policies, also known as AAA policies, are a powerful and flexible way to<br />
prevent unauthorized access to your services. Through the point-and-click WebGUI, you<br />
can easily configure access policies to contact external authentication and policy servers.<br />
● AAA policies can also do security mediation, such as converting between HTTP Basic<br />
Authentication and Kerberos/SPNEGO. AAA policies can also create a SAML assertion<br />
based on authenticated credentials extracted from the message.<br />
Page 72 WebSphere Lab Jam