IBM Support

IBM Security Access Manager for Enterprise Single Sign-On IMS Server fix pack 8.2.1-ISS-SAMESSO-IMS-FP0005

Download


Abstract

Fix pack for IBM Security Access Manager for Enterprise Single Sign-On IMS Server, Version 8.2.1.

Download Description

IBM Security Access Manager for Enterprise Single Sign-On IMS Server, Version 8.2.1, Fix Pack 5 offers new features and currency support.

New in this fix pack


IBM Security Access Manager for Enterprise Single Sign-On REST Web API
You can create, read, or update an application credential with the IBM Security Access Manager for Enterprise Single Sign-On REST Web API.

With the RESTful API based on HTTPS, you can use any client, operating system, or programming language that can submit an HTTP request.

The IBM Security Access Manager for Enterprise Single Sign-On REST Web API replaces the Web API for Credential Management which was accessed through IBM Tivoli Federated Identity Manager Security Token Service (STS). Configure the enterprise directory to Active Directory or Tivoli Directory Server to use the REST Web API.

See the IBM Security Access Manager for Enterprise Single Sign-On 8.2.1 technote.

This fix pack corrects the following issues that are found in IBM Security Access Manager for Enterprise Single Sign-On IMS Server, Version 8.2.1 release:
  • APAR IV53284
    Symptom: In an Active Directory password synchronization enabled configuration, password reset via AccessAssistant fails when passwords are out of sync.
  • APAR IV66155
    Symptom: AuthenticationFailedException while contacting the SMTP server
  • APAR IV66154
    Symptom: When an ESSO user is deleted, the name of the deleted user does not show in the "Delete User" TCR report.
  • Defect
    Symptom: When an ESSO user is deleted, the name of the deleted user does not show in the AccessAdmin "Delete User" audit logs.

The following enhancement was included by interim fix 8.2.1-ISS-SAMESSO-IMS-IF0004
  • Enhancement
    WebAPI (SOAP services)- option to obtain application credentials in clear over Secure Sockets Layer
This fix pack contains:
  • 8.2.1-ISS-SAMESSO-IMS-FP0005.pak
    This .PAK file is the Update Installer maintenance package for IMS Server.
  • etc-ISS-SAMESSO-8.2.1.zip
  • Update_view
    This folder contains the file that is required by the post installation special configuration for APAR IV66154.

Related links
For more information about the IBM Security Access Manager for Enterprise Single Sign-On, Version 8.2.1, see the following links:

Prerequisites

Before you install the fix pack, ensure that you have the following dependencies:

  • IMS Server 8.2.1.0.66 (GA)
  • IBM WebSphere Application Server Update Installer, Version 7.0.0.1 or later (also applicable when using WebSphere Application Server Version 8.5)

Installation Instructions

Before you begin

Copy the IMS Server installation folder to a backup directory.


Installing the fix pack automatically

You can install the fix pack automatically if IMS Server is already installed and deployed in the WebSphere Application Server. This procedure is applicable for WebSphere Application Server Version 7.0 only.



Ensure that you have a copy of 8.2.1-ISS-SAMESSO-IMS-FP0005.zip file. Ensure that the following servers are installed and running:
  • WebSphere Application Server Version 7.0
  • IBM HTTP Server

Note: Do not remap the ISAMESSOIMSConfig module. Otherwise, you cannot access the IMS Configuration Wizard or IMS Configuration Utility.

Procedure

1. Download the 8.2.1-ISS-SAMESSO-IMS-FP0005.zip file from Fix Central.

2. Extract the contents of the 8.2.1-ISS-SAMESSO-IMS-FP0005.zip file onto your local computer.

3. Extract the etc-ISS-SAMESSO-8.2.1.zip file into your selected directory.

4. Copy the extracted etc folder into the root of the <IMS Server installation directory>. For example: C:\Program Files\IBM\ISAM ESSO\IMS Server\etc

5. From the <IMS Server installation directory>\etc\ folder, open the tamesso.ims.appserver.properties file with a text editor and edit the values of the following variables:


was.hostname=was_hostname
was.connector.port=was_connector_port
was.security.enabled=true
was.admin.user.id=was_admin_id
was.admin.user.pwd=was_admin_pw
was.truststore.file=truststore_file
was.truststore.pwd=truststore_pwd
was.keystore.file=
was.keystore.pwd=

a. Replace was_hostname with the name of your computer.

b. Replace was_connector_port with the SOAP connector port. For example: 8880.


You can retrieve the SOAP connector port value from: C:\Program Files\IBM\WebSphere\AppServer\profiles\<profile_name>\logs\AboutThisProfile.txt

Note: If you use WebSphere Application Server Network Deployment, <profile_name> is the deployment manager profile name.

c. Take one of the following actions:

  • If WebSphere Application Server security is enabled, replace was_admin_id and was_admin_pw with your WebSphere Application Server user name and password.
  • If WebSphere Application Server security is not enabled, set the value of was.security.enabled to false.

d. Set the truststore_file and truststore_pwd.


Note: Use any of these valid formats when you specify the path for the truststore file:
  • C:/.../...
  • C:\\...\\...

truststore_file
Replace truststore_file with the path where the truststore file is located.
Follow the format in the tamesso.ims.appserver.properties file.
  • For WebSphere Application Server stand-alone:
C:\Program Files\IBM\WebSphere\AppServer\profiles\<profile_name>\config\cells\<cell_name>\nodes\<node_name>\trust.p12

See the following example:

C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\ibmusvr1Node01Cell\nodes\ibmusvr1Node01\trust.p12

  • For WebSphere Application Server Network Deployment:
C:\Program Files\IBM\WebSphere\AppServer\profiles\<Dmgr_profilename>\config\cells\<cell_name>\trust.p12

See the following example:

C:\Program Files\IBM\WebSphere\AppServer\Profiles\Dmgr01\config\cells\ibm-svr1Cell01\trust.p12

truststore_pwd


Replace truststore_pwd with your WebSphere Application Server trust store password. The default password for WebSphere Application Server trust store is WebAS.

e. If two-way SSL is enabled, set the was.keystore.file and was.keystore.pwd.


Note: Use any of these valid formats when you specify the path for the keystore file:
  • C:/.../...
  • C:\\...\\...

was.keystore.file
Specify the path where the keystore file is located.

Follow the format indicated in the tamesso.ims.appserver.properties file.

  • For WebSphere Application Server stand-alone:
C:\Program Files\IBM\WebSphere\AppServer\profiles\<profile_name>\config\cells\<cell_name>\nodes\<node_name>\key.p12

See the following example:

C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\config\cells\ibmusvr1Node01Cell\nodes\ibmusvr1Node01\key.p12

  • For WebSphere Application Server Network Deployment:
C:\Program Files\IBM\WebSphere\AppServer\profiles\<Dmgr_profilename>\config\cells\<cell_name>\key.p12

See the following example:

C:\Program Files\IBM\WebSphere\AppServer\Profiles\Dmgr01\config\cells\ibm-svr1Cell01\key.p12

was.keystore.pwd


Specify the WebSphere Application Server keystore password.
Note: Remove the value after the installation to avoid compromising security.

f. Click Save and close the file.


6. Launch the IBM Update Installer for WebSphere Software.



a. On your Microsoft Windows Desktop, select Start > All Programs > IBM WebSphere > Update Installer for WebSphere Software. The IBM Update Installer for WebSphere Software wizard is displayed.
b. Click Next. The Product Selection page is displayed.
c. Click Browse to select the location of the <IMS Server installation directory> and click Open.
For example: C:\Program Files\IBM\ISAM ESSO\IMS Server
d. Click Next. The Maintenance Operation Selection page is displayed.
e. Select Install maintenance package.
f. Click Next. The Maintenance Package Directory Selection page is displayed.
g. Click Browse to select the location of the 8.2.1-ISS-SAMESSO-IMS-FP0005.pak file and click Open.
h. Click Next.
i. Select the 8.2.1-ISS-SAMESSO-IMS-FP0005.pak file.
j. Click Next. The Installation Summary page is displayed.
k. Click Next.Two possible messages can be displayed:
Success: The following maintenance package was successfully installed.
Displays if you provided the correct connection properties.

Success: The following maintenance package was partially installed.


Displays if you provided the wrong connection properties. See Installing the fix pack manually procedure.

l. Click Finish. The IMS Server version is updated with the latest fix pack and deployed in the WebSphere Application Server.

7. Remapping the ISAMESSOIMS module.


Note: Do not remap the ISAMESSOIMSConfig module.

a. Log on to the IBM Integrated Solutions Console.
b. On the Integrated Solutions Console left navigation pane, select Applications > Application Types > WebSphere enterprise applications.
c. Click ISAMESSOIMS.
d. Under Modules, click Manage Modules.
e. Click Select All.
f. Select all entries in the Clusters and servers field.
g. Click Apply. The list is updated.
h. Click OK.
i. Click Save.
j. Restart the IBM HTTP Server.

What to do next

  • Do the post installation configurations.
  • Verify the IMS Server version.



Installing the fix pack manually
To install the fix pack manually, you must uninstall and reinstall the IMS Server in the WebSphere Application Server. This procedure is applicable when you use WebSphere Application Server version 7.0 and 8.5.

Ensure that you have a copy of 8.2.1-ISS-SAMESSO-IMS-FP0005.zip file. Ensure that the following servers are installed and running:
  • WebSphere Application Server version 7.0 and 8.5
  • IBM HTTP Server

Procedure

1. Download the 8.2.1-ISS-SAMESSO-IMS-FP0005.zip file from Fix Central.

2. Extract the contents of the 8.2.1-ISS-SAMESSO-IMS-FP0005.zip file onto your local computer.

3. Launch the IBM Update Installer for WebSphere Software.


a. On your Microsoft Windows Desktop, select Start > All Programs > IBM WebSphere > Update Installer for WebSphere Software. The IBM Update Installer for WebSphere Software wizard is displayed.
b. Click Next. The Product Selection page is displayed.
c. Click Browse to select the location of the <IMS Server installation directory> and click Open.
For example: C:\Program Files\IBM\ISAM ESSO\IMS Server
d. Click Next. The Maintenance Operation Selection page is displayed.
e. Select Install Maintenance package.
f. Click Next. The Maintenance Package Directory Selection page is displayed.
g. Click Browse to select the location of the 8.2.1-ISS-SAMESSO-IMS-FP0005.pak file and click Open.
h. Click Next.
i. Select the 8.2.1-ISS-SAMESSO-IMS-FP0005.pak file.
j. Click Next. The Installation Summary page is displayed.
k. Click Next. The message Success: The following maintenance package was partially installed is displayed.
l. Click Finish.

4. Log on to the IBM Integrated Solutions Console.



Uninstalling the IMS Server

1. On the Integrated Solutions Console left navigation pane, select Applications > Application Types > WebSphere enterprise applications.

2. Select the ISAMESSOIMS and ISAMESSOIMSConfig check box.

3. Click Uninstall.

4. Click OK.

5. Click Save.



Installing the ISAMESSOIMSConfig application

1. On the Start menu, click Run.

2. In Open, type cmd.

3. From the command prompt, browse to the <ims_home>\bin directory. For example: C:\Program Files\IBM\ISAM ESSO\IMS Server\bin.

4. Run deployIsamessoImsConfig.bat. For example:

 deployIsamessoImsConfig.bat <WAS Admin user ID> <password>



Installing the ISAMESSOIMS application

1. On the Integrated Solutions Console left navigation pane, select Applications > Application Types > WebSphere enterprise applications.

2. Click Install.

3. Under Path to the new application, select between Local file system and Remote file system.

4. Under Path, click Browse. The com.ibm.tamesso.ims-delhi.deploy.isamessoIms.ear file is located by default in C:\Program Files\IBM\ISAM ESSO\IMS Server\.

5. Click Next. The Preparing for the application installation page is displayed.

6. Select Fast Path - Prompt only when additional information is required.

7. Click Next. The Install New Application page is displayed.

8. Retain the default values under Select installation options.

9. Click Next.

10. Click Select All.

11. Select all entries in the Clusters and servers field.

12. Click Apply. The list is updated with the selected clusters and servers.

13. Click Next.

14. Click Finish. The installation is successful.

15. Click Save.

What to do next

  • Do the post installation configurations.
  • Verify the IMS Server version.

Post installation configuration

If you are using Web 2.0 and Mobile feature pack on WebSphere Application Server Version 7.0, map the ISAMESSOIMS application to the shared library

1. In the navigation pane, click Applications > Application Types > WebSphere enterprise applications.

2. In the Enterprise Applications page, click ISAMESSOIMS.

3. In the Configuration page, under References, click Shared library references.

4.Select ISAMESSOIMS.

5. Click Reference shared libraries.

6. In the Available list, select the jaxrslib library.

7. Move the jaxrslib library to the Selected list by clicking the >> button.

8. Click OK twice.


If you are using WebSphere Application Server Network Deployment, override session management.

1. In the WebSphere administrative console navigation pane, click Applications > Application types > WebSphere enterprise applications.

2. Click ISAMESSOIMS.

3. Under Web Module Properties, click Session management.

4. Under General Properties, select the Override session management check box.

5. Click Apply.

6. In the Messages box, click Save. The ISAMESSOIMS application is stopped.

7. Configure session management override for AccessAdmin.


a. In the Enterprise Applications page, click ISAMESSOIMS.
b. Under Modules, click Manage Modules.
c. Click the ISAM ESSO IMS Server AccessAdmin <version number> link.
d. Under Additional Properties, click Session management.
e. Select the Override session management check box.
f. Click OK.
g. Click Save.

8. Resynchronize the nodes.


a. Click System administration > Nodes.
b. Select the check box for each corresponding node.
c. Click Full Resynchronize.

9. Start the cluster.


If you are using WebSphere Application Server Stand-alone, start the IMS Server.

1. On the Integrated Solutions Console left navigation pane, select Applications > Application Types > WebSphere enterprise applications.

2. Select the ISAMESSOIMS check box.

3. Click Start.



To uninstall the fix pack, see Uninstalling the IMS Server fix pack.

Special Configurations

For APAR IV66154:
1. Unzip 8.2.1-ISS-SAMESSO-IMS-FP0005.zip on to your local computer.
2. Locate \update_view in unzipped content.
3. Apply SQL script corresponding to your database type to update your database:
  • DB2 - apply db2.sql
  • Microsoft SQL server - apply mssql.sql
  • Oracle DB - apply oracle.sql

Verifying the IMS Server version after fix pack installation
You can verify the IMS Server version to determine whether the fix pack installation was successful.

About this task
After you apply the fix pack, complete these steps to verify that the IMS Server version was updated. If the fix pack installation failed, manually uninstall the IMS Server and install the IMS Server in the WebSphere Application Server.

Procedure

1. Log on to AccessAdmin(https://<Web server name>/admin).

2. Select System > Status > IMS Server version.


If you successfully installed 8.2.1-ISS-SAMESSO-IMS-FP0005, the IMS Server version is updated to 8.2.1.0.204.

On
[{"DNLabel":"8.2.1-ISS-SAMESSO-IMS-FP0005","DNDate":"5 Dec 2014","DNLang":"English","DNSize":"254219862","DNPlat":{"label":"Windows","code":"PF033"},"DNURL":"http://www.ibm.com/support/fixcentral/swg/quickorder?product=ibm/Tivoli/Tivoli+Access+Manager+for+Enterprise+Single+Sign-On&release=All&platform=All&function=fixId&fixids=8.2.1-ISS-SAMESSO-IMS-FP0005&includeRequisites=1&includeSupersedes=0","DNURL_FTP":" ","DDURL":null}]
[{"Product":{"code":"SS9JLE","label":"IBM Security Access Manager for Enterprise Single Sign-On"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"IMS Server","Platform":[{"code":"PF033","label":"Windows"}],"Version":"8.2.1","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
15 June 2018

UID

swg24038930