Configuring WebSEAL to include OAuth decisions

To make an OAuth authorization decision, Tivoli Federated Identity Manager requires specific information regarding the request. The required data includes the following:

• Authorization data. This data is obtained from either the authorization header, the query string or the POST data.
• Resource information. This data is obtained from the HTTP request and is used to validate the OAuth signature.

WebSEAL uses the EAS plug-in to provide this required data and to use the OAuth functionality in Tivoli Federated Identity Manager. The EAS plug-in is installed with the Security Access Manager Web Security Runtime package.

To include OAuth decisions as part of the standard authorization on WebSEAL requests, you need to perform the following tasks:

1. Configure the required authorization decision data.
2. Configure the extra EAS specific data.

This configuration ensures that the correct data is passed to the EAS for each request.