03.05.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Testing the junctions<br />

The following tests will help to make sure that the junctions are set correctly. The<br />

first tests will be performed on the appsrv02 server.<br />

1. Point a browser to http://appsrv02/itsobank and the ITSOBank welcome<br />

window is displayed. Click any of the functions of the application, they are<br />

available without challenge for identity.<br />

2. Point a new browser session to https://wsl01/junction2/itsobank/ and<br />

after the normal certificate warnings (accept the certificate), a Basic<br />

Authentication challenge is presented which can be answered with any of the<br />

users created earlier to show the ITSOBank Welcome window. All<br />

functionality is again available as it is only the junction which is protected.<br />

The next two steps will access the application on the appsrv01 server.<br />

1. Point a browser to http://appsrv01/itsobank and you are again presented<br />

with the welcome window. However, attempting to use either function requires<br />

a valid Access Manager identity to be authorized.<br />

2. Point a new browser to http://wsl01/junction1/itsobank; this results in a Basic<br />

Authentication challenge before the ITSOBank welcome window is shown. It<br />

is not until you attempt to access one of the protected funtions that you are<br />

challenged again for a valid identity. The welcome window which is not<br />

protected by the application is in effect a static resource which can be<br />

independently protected by WebSEAL.<br />

Protecting <strong>WebSphere</strong> URIs<br />

Access Manager can secure <strong>WebSphere</strong> servlets and JSPs but not EJBs or<br />

individual methods, only URIs. If the application you wish to secure is of a simple<br />

enough design then this may be all you need.<br />

This sample will use the index.jsp page provided with the ITSOBank sample<br />

application. The index.jsp is available for everyone, the resource is not protected,<br />

access is granted for the Everyone special subject to be exact. This sample will<br />

use Tivoli Access Manager WebSEAL to protect this resource and only give<br />

access to the user accountant01 in the accountantgrp group. You can try to<br />

access the index.jsp at http:///itsobank/index.jsp.<br />

1. Start the pdadmin tool to administer Tivoli Access Manager, and login with the<br />

sec_master user.<br />

2. Create a junction to the Web space.<br />

pdadmin> server task Webseald-wsl01 create -f -t tcp -h appsrv01 -p 9080<br />

/itsobankURItest<br />

3. Create a new ACL for the index.jsp resource.<br />

acl create itsobankURItestACL<br />

428 <strong>IBM</strong> <strong>WebSphere</strong> <strong>V5.0</strong> <strong>Security</strong> Handbook

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!