Preparing security for remote search service in a single-signon domain
For remote search service
on a single-signon installation, you need to prepare portal security. To prepare
portal security for remote search service on a single portal installation,
proceed by the following steps:
- Make the key file available to all servers in the Single-SignOn
(SSO) domain. To do this, perform the following steps on one of the
servers that you plan to be part of the SSO domain:
- Open the administrative console.
- Select .
- Enter a Key File Name and click the button Export Keys.
The keys are written to the file was_profile_root/Key
File Name.
- Import the key file to all other servers of the SSO domain. To
do this, perform the following steps on all other servers that you
plan to be part of this same SSO domain:
- Copy the key file that you exported in step 1 above to the server
into the directory AppServer.
- Open the WebSphere
Application Server Administrative
Console.
- Select .
- Enter a Key File Name and click the button Import Keys.
The keys are propagated to all servers of the SSO domain.
- Restart all WebSphere
Application Server profiles
on this server.
For more details about exporting the LTPA token, refer to the WebSphere
Application Server information
center under Administering
> Security > Managing security > Configuring authentication mechanisms > Configuring
Lightweight Third Party Authentication > Lightweight Third Party Authentication
settings. You can also locate this topic by opening the search
feature of the WebSphere
Application Server information
center and searching for ltpa
key export.
If you work with EJB on a secure server,
you need to set the search user ID. For details about how to do this, refer
to Set the search user ID
Parent topic: Using remote search service
Related tasks
SOAP.">Preparing for remote search service
Set the search user ID
Configuring Portal Search for remote search service
Changing between local and remote search services
|
|
|