13.07.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS
  • No tags were found...

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

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

[8/22/02 7:42:44:163 CDT] 277a2e5c WebCollaborat >SetUnauthenticatedCredIfNeeded[8/22/02 7:42:44:163 CDT] 277a2e5c WebCollaborat d Invoked and receivedCredential are null, setting it anonymous/unauthenticated.[8/22/02 7:42:44:163 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 > WebAccessContextIn this example, the first portion shows a snapshot of the HTTP header of therequest received by <strong>WebSphere</strong> from WebSEAL. Here, we need to look at ivfields being passed to <strong>WebSphere</strong> from WebSEAL. In our example, we used the-c all junction option in WebSEAL. This means that we should see all of the ivheader fields being passed to <strong>WebSphere</strong> from WebSEAL. In our example, youcan in fact see that the iv fields were passed. For iv-user, we have manager,which is our Access Manager/<strong>WebSphere</strong> user id, and is the id with which wewant to use in our itsobank application. In addition, you can see that iv-creds andiv-groups were also passed. If, when looking at the HTTP header trace entry, youdo not see the iv field which you have configured TAI to use in <strong>WebSphere</strong>, thenthe problem is probably in the creation of your WebSEAL junction. In this case,you should go back and redefine your WebSEAL junction, using the correctparameter that you require with the -c option.The next set of trace entries show the invocation of TAI to obtain the usercredentials passed by WebSEAL, and the authentication of the WebSEALserver. Note that only the relevant portions are presented.Example 12-5 WebSEAL Trust Association trace8/22/02 7:42:45:223 CDT] 277a2e5c WebAuthentica d A cookie was received. Thename 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: headername=authorization404 <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!