A junction must be created between WebSEAL and WebSphere Application Server. This junction will carry the iv-creds (for TAI++) or iv-user (for TAI) and the HTTP basic authentication headers with the request. While WebSEAL can be configured to pass the end user identity in other ways, the iv-creds header is the only one supported by the TAI++ and iv-user the only one supported by TAI.
We recommend that communications over the junction use SSL for increased security. Setting up SSL across this junction requires that you configure the HTTP Server used by WebSphere Application Server, and WebSphere Application Server itself, to accept inbound SSL traffic and route it correctly to WebSphere Application Server. This requires importing the necessary signing certificates into the WebSEAL certificate keystore, and possibly also the HTTP Server certificate keystore. Create the junction between WebSEAL and the WebSphere Application Server using the -c iv-creds option for TAI++ and -c iv-user for TAI. For example (commands are entered as one line):
TAI++
server task webseald-server create -t ssl -b supply -c iv-creds
-h host_name -p websphere_app_port_number junction_name
TAI
server task webseald-server create -t ssl -b supply -c iv-user
-h host_name -p websphere_app_port_number junction_name
Notes:
For single signon to WebSphere Application Server the SSO password must be set in WebSEAL. To set the password, complete the following steps:
Related concepts
Single signon using WebSEAL or the Tivoli Access Manager plug-in for Web servers
Related tasks
Creating a trusted user account in Tivoli Access Manager