IBM WebSphere V5.0 Security - CGISecurity

[8/22/02 7:42:44:163 CDT] 277a2e5c WebCollaborat >
SetUnauthenticatedCredIfNeeded
[8/22/02 7:42:44:163 CDT] 277a2e5c WebCollaborat d Invoked and received
Credential are null, setting it anonymous/unauthenticated.
[8/22/02 7:42:44:163 CDT] 277a2e5c WebCollaborat <
SetUnauthenticatedCredIfNeeded:true
[8/22/02 7:42:44:164 CDT] 277a2e5c EJSWebCollabo d Request Context
Path=/itsobank, Servlet Path=/, Path Info=transfer/branchtransfer.html
[8/22/02 7:42:44:164 CDT] 277a2e5c WebCollaborat > authorize
[8/22/02 7:42:44:164 CDT] 277a2e5c WebCollaborat d URI requested:
/transfer/branchtransfer.html
[8/22/02 7:42:44:164 CDT] 277a2e5c WebAppCache d Okay, I found the entry for
[default_host:/itsobank]
[8/22/02 7:42:44:164 CDT] 277a2e5c WebAccessCont > WebAccessContext
In this example, the first portion shows a snapshot of the HTTP header of the
request received by WebSphere from WebSEAL. Here, we need to look at iv
fields being passed to WebSphere from WebSEAL. In our example, we used the
-c all junction option in WebSEAL. This means that we should see all of the iv
header fields being passed to WebSphere from WebSEAL. In our example, you
can in fact see that the iv fields were passed. For iv-user, we have manager,
which is our Access Manager/WebSphere user id, and is the id with which we
want to use in our itsobank application. In addition, you can see that iv-creds and
iv-groups were also passed. If, when looking at the HTTP header trace entry, you
do not see the iv field which you have configured TAI to use in WebSphere, then
the problem is probably in the creation of your WebSEAL junction. In this case,
you should go back and redefine your WebSEAL junction, using the correct
parameter that you require with the -c option.
The next set of trace entries show the invocation of TAI to obtain the user
credentials passed by WebSEAL, and the authentication of the WebSEAL
server. Note that only the relevant portions are presented.
Example 12-5 WebSEAL Trust Association trace
8/22/02 7:42:45:223 CDT] 277a2e5c WebAuthentica d A cookie was received. The
name is LtpaToken and the value is NULL
[8/22/02 7:42:45:223 CDT] 277a2e5c WebAuthentica < handleSSO: (null)
[8/22/02 7:42:45:514 CDT] 277a2e5c WebAuthentica d handleTrustAssociation
[8/22/02 7:42:45:515 CDT] 277a2e5c WebAuthentica d TrustAssociation is enabled.
[8/22/02 7:42:45:586 CDT] 277a2e5c TrustAssociat > getInterceptor
[8/22/02 7:42:45:586 CDT] 277a2e5c TrustAssociat d Check if target interceptor
...
[8/22/02 7:42:46:397 CDT] 277a2e5c WebSealTrustA > getCheckID
[8/22/02 7:42:46:397 CDT] 277a2e5c WebSealTrustA < getCheckID
[8/22/02 7:42:46:397 CDT] 277a2e5c WebSealTrustA d isTargetInteceptor: header
name=authorization
404 IBM WebSphere V5.0 Security Handbook