Integrating NonStop JDBC Type 4 Driver With IBM WebSphere Applications

Figure 2

Enabling security

In the Duke’s Bank Application, most of the URLs are restricted to the security role BankCustomer. The

application requires users to identify themselves via the form-based login mechanism. When a

customer tries to access a Web client URL, and has not been authenticated, the Web container

displays the form-based login URL/logon mapped to the logon.jsp page. This page contains a form

that requires a customer to enter an identifier and password. The Web container retrieves this

information, maps it to a security role, and verifies that the role matches that specified in the security

constraint. You will thus need to configure the WebSphere Application Server environment to provide

authentication for your application.

To keep things simple, you will implement a file-based security system to work with the Duke’s Bank

Application. The following subsections provide detailed information on how to enable security in the

WebSphere Application Server environment:

1. Because security is not enabled, you will be prompted for only a user ID (see figure 3). Once

you enable your security to use the custom registry, you will need to use one of the user IDs

defined in the users file. In the meantime, keep the user ID blank and select OK.

Figure 3