5.4 Configuring SSPR

The following sections provide information about configuring SSPR. Before configuring the components, review the information from Understanding the Configuration Parameters.

NOTE:Ensure that the following containers and user objects are present in the Identity Vault before configuring SSPR:

  • User Search Container

  • Admin Search Container

  • Identity Applications Administrator User

5.4.1 Performing an Interactive Configuration

  1. Navigate to the location where you mounted the Identity_Manager_4.8_Linux.iso.

  2. Navigate to the sspr directory.

  3. Execute the following command:

    ./configure.sh

  4. Configure the settings.

5.4.2 Performing a Silent Configuration

Before starting the configuration, ensure that sspr_silentinstall.properties (<iso mounted path>/sspr/) file is copied to a writable directory. For example, copy the file to /tmp directory.

  1. Navigate to the location where you mounted the Identity_Manager_4.8_Linux.iso.

  2. Navigate to the sspr directory.

  3. Execute the following command:

    ./configure.sh -s -f <location of the silent properties file>

    For example,

    ./configure.sh -s -f /tmp/sspr_silentinstall.properties, where /tmp/sspr_silentinstall.properties is the location where you stored the silent properties file.

  4. Configure the settings.

5.4.3 Modifying the Single Sign-on Access Settings on the OSP Server

If SSPR and OSP are installed on separate servers (SSPR is installed on a different server than Identity Applications or Identity Reporting), you must configure the single sign-on access settings on the OSP server. This section helps you ensure that the settings work for your environment.

  1. Launch the RBPM Configuration update utility on the server where OSP is installed.

  2. Navigate to SSO Clients > Self Service Password Reset.

  3. Specify the SSPR server details in the OSP OAuth Redirect URL field. For example, https://<SSPR Hostname IP>:port/sspr/public/oauth.

  4. Click OK to save your changes, then close the configuration utility.

  5. Restart Tomcat for the changes to take effect.