Why and when to perform this task
Tivoli Access Manager plug-in for Web servers can be used as a security gateway for your protected WebSphere Application resources. With such an arrangement the plug-in authorizes all user requests before passing the credentials of the authorized user to WebSphere Application Server in the form of an iv-creds header. Trust between the plug-in and WebSphere Application Server is established through use of basic authentication headers containing the single signon (SSO) user password.In the following example Tivoli Access Manager plug-in for Web Servers Version 5.1 configuration shows IV headers configured for post-authorization processing and basic authentication configured as the authentication mechanism and for post-authorization processing. After a request has been authorized the basic authentication header is removed from the request (strip-hdr = always) and a new one added (add-hdr = supply). Included in this new header is the password set when the SSO user was created in Creating a trusted user account in Tivoli Access Manager. This password needs to be specified in the supply-password parameter and is passed in the newly created header. This basic authentication header enables trust between WebSphere Application Server and the plug-in.
An iv-creds header is also added (generate = iv-creds) which contains the credential information of the user passed onto WebSphere Application Server. Note also that session cookies are used to maintain session state.
Example
[common-modules]
authentication = BA
session = session-cookie
post-authzn = BA
post-authzn = iv-headers
[iv-headers]
accept = all
generate = iv-creds
[BA]
strip-hdr = always
add-hdr = supply
supply-password = sso_user_password
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