Configure eTrust SiteMinder
WebSphere Portal supports the use of Computer Associates eTrust SiteMinder for authentication and authorization. Before configuring eTrust SiteMinder for authentication and/or authorization, complete the following tasks:
- Configure WebSphere Portal, including databases and LDAP user registry.
- Install Computer Associate's Policy Server.
- Install the eTrust SiteMinder Software Development Kit on the same machine as WebSphere Portal if you plan to use eTrust SiteMinder for both authentication and authorization. Refer to the eTrust SiteMinder documentation for more information.
- Install the eTrust SiteMinder Trust Association Interceptor (TAI), following the instructions in the eTrust SiteMinder documentation.
Copy the smagent.properties file from the eTrust SiteMinder appserver agent installation directory to the following directory:
Table 1. Directory to copy the smagent.properties file
Operating system Directory Windows located in the profile_root/ConfigEngine\properties directory UNIX located in the profile_root/ConfigEngine/properties directory By default, the Netegrity Application Server Agent installation enables agents other than the one used for authentication. These agents have not been tested with WebSphere Portal and should be disabled. Modify the following files under the eTrust SiteMinder installation directory to set EnableWebAgent=no:
- Asa-Agent-az.conf
- Asa-Agent-auth.conf
- If you plan to use eTrust SiteMinder for both authentication and authorization, ensure that the eTrust SiteMinder Software Development Kit smjavasdk2.jar is in the WAS lib/ext directory.
If the directory is missing the jar file, copy the smjavasdk2.jar from the eTrust SiteMinder SDK /java directory.
- Create and specify the following eTrust SiteMinder Domain objects if you plan to use eTrust SiteMinder for both authentication and authorization. Refer to the eTrust SiteMinder Policy Design documentation for information about how to create these objects:
- User Directory:
The LDAP server and suffix
- Authentication Scheme:
Associates with the eTrust SiteMinder realms that WebSphere Portal creates.
An eTrust SiteMinder realm is different from an LDAP realm or a basic authentication realm. Within the eTrust SiteMinder administrative console, a realm is an administrative object representing a protected URL root. An example is /wps/myportal. eTrust SiteMinder realms in combination with eTrust SiteMinder policies determine which users and groups are allowed to navigate to the protected URL root and its children URLs.
- Agent:
An eTrust SiteMinder WebAgent that is configured to support 4.x agents or a custom eTrust SiteMinder agent. The agent must have a static shared secret to allow communication with the eTrust SiteMinder Policy Server.
To configure eTrust SiteMinder:
- Configure eTrust SiteMinder for authentication and authorization
You can configure Computer Associates eTrust SiteMinder to perform both authentication and authorization for WebSphere Portal. Using eTrust SiteMinder to perform only authorization is not supported at this time.
- Configure eTrust SiteMinder to perform authentication
WebSphere Portal includes a configuration task called enable-sm-tai. This task interacts with IBM WAS security configuration to enable the eTrust SiteMinder TAI and to create it as one of the interceptors. You can configure eTrust SiteMinder to provide authentication independently from configuring it to provide authorization.
Using it to perform authorization only is not supported at this time.
- Configure eTrust SiteMinder to perform authorization
You can configure Computer Associates eTrust SiteMinder to perform authorization independently from configuring it to perform authentication. However, if you use eTrust SiteMinder to perform authorization for WebSphere Portal, you should also use it to perform authentication. Using eTrust SiteMinder to perform only authorization is not supported at this time.
- Removing eTrust SiteMinder
After you have installed and used Computer Associates eTrust SiteMinder, you may find that you no longer require its use. You can then remove it from the WebSphere Portal environment and restore authentication capabilities to IBM WAS and authorization capabilities to WebSphere Portal.
Parent topic:
External security managers