Expiration of a keystore password may cause Information Server product outage on April 26, 2012

Content

How to determine if your environment is impacted

If you are not using a front-end HTTP server with the WebSphere Application server, then your installation cannot be impacted. Typically, only an application server cluster will use a front end web server.

If you are using a front-end http server, but you do not have it configured to use HTTPS (secure transport) then you cannot be impacted.

Verify your configuration with your system administrator before proceeding.

If you are using a front-end HTTPS web server

To determine if you are impacted by this issue, take the following steps:

1. Check the front-end HTTP server httpd.conf to find the WebSpherePluginConfig location
2. Check the location specified by the WebSpherePluginConfig and review the paths to the plugin-key.kdb file being used.
3. Verify that any referenced plugin-key.kdb files have a "zero" expiration as described in WebSphere Application Server plugin-key.kdb expiration.

If your environment is impacted

You must follow the steps in the WebSphere Application Server plugin-key.kdb expiration to address the problem. If you take no action, Information Server will become non-functional on or after April 26, 2012 until you take corrective action.