CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

10.3.2 HTTP Server and basic authentication testing
274 CICS Transaction Gateway V5
Next, we decided to route our requests to port 99 on which our HTTP Server was
listening. To enable the HTTP Server to forward requests to the WebSphere
plugin, we added the following service statement to httpd.conf:
Service /CTGTester*/*
/usr/lpp/WebSphere/WebServerPlugIn/bin/was400plugin.so:service_exit
Since we did not have a matching rooturi in our WebSphere plugin configuration
file (was.conf), the request was automatically routed over to the J2EE Server,
where it was processed just like the previous requests handled by the HTTP
Transport Handler.
We also modified our httpd.conf file to turn on turn on HTTP basic authentication
for our Web applications. This meant our Web applications were now protected
and the HTTP Server would allow access only if a valid user ID and password
were supplied. The statements we added are as follows:
Protection CTGTesterWeb {
ServerID CTGTester
UserID %%CLIENT%%
AuthType Basic
PasswdFile %%SAF%%
Mask All
}
Protect /CTGTester*/* CTGTesterWeb
Results with ECIRequest/servlet application
We invoked our servlet application, CTGTesterECI Web application, using the
following URL:
http://wtsc66oe.itso.ibm.com:99/CTGTesterECIweb
This caused the basic authentication challenge window to be presented to the
Web client, as shown in Figure 10-24.
Figure 10-24 Basic authentication prompt