-
Título
TPAM Hotfix 9172v2 for Solution 227184 - Adds a "status" page for the Cache server -
Descrição
This hotfix includes the changes outlined in the following sections. One Identity may generate additional hotfixes for future releases of the product.
This hotfix addresses cache servers.
Note: The difference between hotfix 9172, which was released on March 14, 2017, and hotfix 9172v2 is that version 2 allows for compatibility with newer versions of Java.
The minimum version for installing this hotfix is TPAM 2.5.913.
Resolved Issues:
When this hotfix is applied to 2.5.913-2.5.914, the Cache server will be updated to PCA-2.0.9.
When this hotfix is applied to 2.5.915, the Cache server will be updated to PCA-2.1.4.
When this hotfix is applied to 2.5.916-2.5.918, the Cache server will be updated to PCA-2.4.2.
This hotfix adds a "status" page for the Cache server. The "status" page is available at https://CacheServerAddress/status/index.html. The possible values on the status page are:
NotReady
- J2EE server just started and the initialization request has not been sent.
- New certificates or trusted root certificates have been sent by TPAM, and J2EE server is getting ready to be bounced to place those certificates in the appropriate certificate store.
InitRequested
- Cache server has asked the primary TPAM appliance to send all data.
Initializing
- Cache server is receiving the data from the primary TPAM appliance.
Ready
- Cache server has received all data and is ready to process password requests. -
Resolução
Please download the TPAM Hotfix 9172v2 for KB 227184 by clicking here.
Resolved IssuesThe following is a list of issues resolved in this hotfix.
Resolved Issue Issue ID This hotfix adds a "status" page for the Cache server. The "status" page is available at https://CacheServerAddress/status/index.html.
When this hotfix is applied to 2.5.913-2.5.914, the Cache server will be updated to PCA-2.0.9.
When this hotfix is applied to 2.5.915, the Cache server will be updated to PCA-2.1.4.
When this hotfix is applied to 2.5.916-2.5.918, the Cache server will be updated to PCA-2.4.2.BFER 9172 Applicability of this hotfix
Products affected by this hotfix;
Product Name Version TPAM 2.5.913 - 2.5.918 Installing this hotfix
To install the hotfix:1. Take a backup of the TPAM appliance.
2. Copy the supplied .zip file to your local computer.
3. Log in to the TPAM /admin interface.
4. Select Maint | Apply a Patch from the menu.
5. Click the Select File button.
6. Click the Browse button. Select the patch file that you saved locally.
7. Click the Upload button.
8. Type p3vVPN0gzy in the Key box.
9. Type /genkey in the Options box.
10. By default, if you are applying a patch to a primary member of a cluster, the replicas in the cluster will be listed and highlighted in the Target Replicas list. If any of the replicas are deselected, the patch will not be applied to it. The replica can be patched at a later date by logging on directly to the /admin interface of the replica. If the software version numbers (excluding the build number) of the primary and the replica still match them the primary will still be able to send data to the replica. We recommend that you contact Technical Support before deciding to deselect any of the replicas on this list.
11. Click the Apply Patch button.
12. After patch is finished applying either disable/enable cache servers, or reboot them.
Verifying successful installationTo determine if this hotfix is installed:
1. Click the Patch Log tab.
2. To set the log refresh interval, select Refresh Results every X seconds.
3. Once the hotfix has been applied there will be a message in the patch log stating “Patch successfully
applied to system”.
Removing this hotfixTo remove this hotfix:
1. To remove this hotfix the TPAM appliance can be restored using the backup taken prior to applying the
hotfix. We recommend discussing this with Technical Support prior to completing the restore. -
Solicitação de alteração
9172