Configure WebSEAL for use with WAS

 

+

Search Tips   |   Advanced Search

 

Overview

A junction must be created between WebSEAL and WebSphere Application Server. This junction carries the iv-credentials (for TAI++) or iv-user (for TAI) and the HTTP basic authentication headers with the request. You can configure WebSEAL to pass the end user identity in other ways, the iv-credentials header is the only one supported by the TAI++ and the iv-user is the only one supported by TAI.

We recommend that communications over the junction use Secure Sockets Layer (SSL) for increased security. Setting up SSL across this junction requires that you configure the HTTP Server used by WebSphere Application Server, and WAS itself, to accept inbound SSL traffic and route it correctly to WAS. This activity 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 WAS using the -c iv_creds option for TAI++ and -c iv_user for TAI. Enter either of the following commands as one line using the variables that are appropriate for your environment:

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

If warning messages are displayed about the incorrect setup of certificates and key databases, delete the junction, correct problems with the key databases, and recreate the junction.

The junction can be created as -t tcp or -t ssl, depending on your requirements.

For single sign-on the password must be set in WebSEAL....

  1. Edit the WebSEAL configuration file...

    webseal_install_directory/etc/webseald-default.conf

    Set the following parameter:

    basicauth-dummy-passwd=webseal_userid_passwd

    ...where webseal_userid_passwd is the SSO password for the trusted user account set in Creating a trusted user account in Tivoli Access Manager.

  2. Restart WebSEAL.

 

Related tasks


Configure single sign-on using trust association interceptor ++
Creating a trusted user account in Tivoli Access Manager
Configure single sign-on capability with Tivoli Access Manager or WebSEAL
Tivoli Access Manager official documentation