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.

[8/22/02 7:41:32:036 CDT] 7822e45 WebSealTrustA d WebSeal Login ID = null<br />

[8/22/02 7:41:32:045 CDT] 7822e45 WebSealTrustA > addASource<br />

[8/22/02 7:41:32:045 CDT] 7822e45 WebSealTrustA d WebTAInterceptor: Added<br />

source = wsl01:443<br />

[8/22/02 7:41:32:045 CDT] 7822e45 WebSealTrustA < Exiting addASource<br />

[8/22/02 7:41:32:045 CDT] 7822e45 WebSealTrustA < Exiting initialization:<br />

SUCCESS<br />

[8/22/02 7:41:32:045 CDT] 7822e45 TrustAssociat A SECJ0122I: Trust Association<br />

Init Interceptor signature: WebSeal Interceptor Version 1.1<br />

[8/22/02 7:41:32:064 CDT] 7822e45 TrustAssociat A SECJ0120I: Trust Association<br />

Init loaded 1 interceptor(s)<br />

[8/22/02 7:41:32:076 CDT] 7822e45 TrustAssociat < initialize<br />

Here we see TAI being initialized. We need to look at the Trust Properties line in<br />

the trace to verify that the property values being used are the ones we think we<br />

set. If we see an error here with one of the properties, then we need to go back to<br />

our property definition, either in the properties file, or our custom property entries<br />

in TAI, and provide the correct values. If the property values are correct, and we<br />

see, as above, that the WebSealTrustAssociation is being initialized properly,<br />

then we know that we have properly configured TAI. In this case, we now need to<br />

access our WebSEAL junction from a browser, and login to WebSEAL. The next<br />

example shows what should appear in the trace file if all is well.<br />

Example 12-4 Trace file http header from WebSEAL<br />

[8/22/02 7:42:44:163 CDT] 277a2e5c EJSWebCollabo d Http Header names and<br />

values:<br />

authorization=[Basic d2Vic2VhbHM6cGFzc3dvcmQx]<br />

iv-groups=["managergrp"]<br />

via=[HTTP/1.1 wsl01:443]<br />

user-agent=[Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)]<br />

host=[seccli.itso.ral.ibm.ibm.com:9443]<br />

accept=[image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*]<br />

connection=[close]<br />

accept-language=[en-us]<br />

iv-user=[manager]<br />

iv-creds=[Version=1,<br />

BAKs3DCCA-YMADCCA-AwggPsAgIDkDBsMCkwHgIE48b7FgIDAKe5AgIR1gICAKUCASQEBgBAqsIqTAw<br />

...<br />

0YTFCUlowRkJRVUU5BAA=]<br />

referer=[https://wsl01.itso.ral.ibm.com/tai/itsobank/]<br />

accept-encoding=[gzip, deflate]<br />

cookie=[msp=2; IV_JCT=/tai]<br />

[8/22/02 7:42:44:163 CDT] 277a2e5c EJSWebCollabo d VirtualHost is :<br />

default_host<br />

[8/22/02 7:42:44:163 CDT] 277a2e5c Web<strong>Security</strong>Co > WebAccessContext<br />

[8/22/02 7:42:44:163 CDT] 277a2e5c Web<strong>Security</strong>Co < WebAccessContext<br />

Chapter 12. Tivoli Access Manager 403

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

Saved successfully!

Ooh no, something went wrong!