Access Manager 4.5 Service Pack 1 Hotfix 2 Release Notes

September 2020

Access Manager 4.5 Service Pack 1 Hotfix 2 (4.5.1.2) supersedes Access Manager 4.5 Service Pack 1 Hotfix 1.

For the list of software fixes and enhancements in the previous release, see Access Manager 4.5 Service Pack 1 Hotfix 1 Release Notes.

For information about Access Manager support lifecycle, see the Product Support Lifecycle page.

If you have suggestions for documentation improvements, click comment on this topic at the top or bottom of the specific page in the HTML version of the documentation posted at the Documentation page.

1.0 Software Fixes

This release includes the following software fixes:

Component

Bug ID

Issue

Access Gateway

273170

When the SameSite cookie is enabled in Access Gateway, and two or more cookies are available with the same name, Access Gateway changes the sequence of the cookies in the response header to the browser.

Therefore, when the browser sends cookies to the web server, it sends in the reverse order. This, in turn, impacts the processing of the request at the web server.

Access Gateway

277154

Apache processes a request multiple times, causing duplicate transactions at the backend web server.

2.0 Verifying Version Numbers Before Upgrading to 4.5.1.2

To ensure that you have the Access Manager 4.5 files before upgrading to Access Manager 4.5.1.2, verify the existing Access Manager version by clicking Troubleshooting > Version.

3.0 Upgrading to Access Manager 4.5.1.2

IMPORTANT:In a cluster setup, ensure that you install the hotfix on each node of the Access Manager setup.

3.1 Downloading the Hotfix

The hotfix helps in upgrading to the latest Access Manager with ease.

If you have multiple components installed on the same system, the hotfix installation process takes care of updating all the binaries of these components. For example, if you have both Identity Server and Administration Console installed on a system, installing the hotfix takes care of updating the binaries of Identity Server and Administration Console.

IMPORTANT:Ensure that you are currently on Access Manager 4.5.1 before upgrading to Access Manager 4.5.1.2.

To download Access Manager 4.5.1.2, perform the following steps:

  1. Go to NetIQ Downloads Page.

  2. Under Patches, click Search Patches.

  3. Specify AM_4512.zip in the search box and download the file.

  4. Save the hotfix file to the server running Access Manager. If you have multiple servers in your set up, ensure that you copy this zip file to all the servers.

    NOTE:This hotfix is not required for Analytics Server.

3.2 Upgrading to Access Manager 4.5.1.2 on Linux

You can upgrade to Access Manager 4.5.1.2 by using the proceeding steps. This requires few manual interventions to continue the upgrade process. If you do not require any manual intervention while upgrading to the hotfix, see Silent Hotfix Upgrade on Linux.

NOTE:This installation is not applicable for Analytics Server.

  1. Extract the hotfix file by using the unzip AM_4512.zip command.

    After extraction, the following files and folders are created in the AM_4512 folder:

    Table 1 Files and folders created in the AM_4512 folder after extracting the hotfix installer ZIP file

    File/Folder Name

    Description

    rpm

    Contains rpm files for the hotfix to run on a Linux server.

    installPtool.sh

    Script to install the hotfix and the hotfix tool on a Linux server.

    installPatch.sh

    Script to install the hotfix tool and the updated binaries on a Linux server.

  2. Log in as the root user.

  3. (Conditional) To automate the hotfix installation, perform the steps mentioned in Silent Hotfix Upgrade on Linux, else continue with Step 4.

  4. Go to the location where you have extracted the hotfix files.

  5. Run the installPatch.sh command.

    This command installs the hotfix and the bundled binaries.

    NOTE:To manage the Access Manager hotfix file, refer to Managing Hotfix.

If the hotfix is already installed, the installer exits with a message.

3.3 Upgrading to Access Manager 4.5.1.2 on Windows

If you do not require any manual intervention while upgrading to the hotfix, see Silent Hotfix Upgrade on Windows.

Perform the following steps to install the hotfix on Windows manually:

  1. Extract the files from AM_4512.zip.

  2. Run command prompt as an administrator.

  3. Run the installPtool.cmd command.

    This installs the hotfix binaries on the Windows system.

NOTE:To manage the Access Manager hotfix file, refer to Managing Hotfix.

3.4 Silent Hotfix Upgrade on Linux

Perform the following steps to automate the installation of the hotfix:

  1. Go to /opt/novell/nam/patching/bin/ and add the following in the patch file:

    -Dcom.netiq.nam.patching.enableautomation=true

    This updates the patch file as following:

    /opt/novell/java/bin/java -cp ../lib/*: \
    -Dcom.netiq.nam.patching.enableautomation=true -Djava.util.logging.config.file=logging.properties com.netiq.nam.patching.PatchInstaller $@
  2. Run the following command at /opt/novell/nam/patching/bin/:

    ./patch -i /<path where you extracted the hotfix>/AM_4512/AM_4512-6.patch

3.5 Silent Hotfix Upgrade on Windows

Perform the following steps on the command prompt to automate the installation of the hotfix:

  1. Go to C:\Program Files\Novell\patching\bin and add the following in the patch file:

    -Dcom.netiq.nam.patching.enableautomation=true

    This updates the patch file as following:

    -Dcom.netiq.nam.patching.enableautomation=true -Djava.util.logging.config.file=logging.properties com.netiq.nam.patching.PatchInstaller $@
  2. Run the following command at C:\Program Files\Novell\patching\bin:

    patch.cmd -i /<path where you extracted the hotfix>/AM_4512/AM_4512-6.patch

3.6 Managing Hotfix

  1. After the hotfix is installed, go to the following folder:

    • For Linux: /opt/novell/nam/patching/bin

    • For Windows: C:\Program Files\Novell\patching\bin

  2. Use the following options to manage the Access Manager hotfix file:

Option

Description

Command on Linux server

Command on Windows server

-qa

Lists all installed hotfixes.

patch -qa

patch.cmd -qa

-q

Lists details of an installed hotfix.

patch –q

Example: patch –q HF2-6

patch.cmd –q

Example: patch.cmd –q HF2-6

-i

Installs a hotfix. During installation of a hotfix, all running services are stopped temporarily. After a hotfix is installed, all services are restarted and details of the operation are written to log files.

patch –i <location and hotfix name>

Example: patch –i /opt/novell/nam/Patches/AM_4512/AM_4512-6.patch

patch.cmd –i <location and hotfix name>

Example: patch.cmd –i C:/Patches/AM_4512/AM_4512-6.patch

-e

Removes an installed hotfix. The hotfix maintains content relationship among hotfixes. So, if you have installed hotfix 1 and hotfix 2, hotfix 1 cannot be removed without removing hotfix 2. This is because hotfix 2 contains details of hotfix 1 as well.During the hotfix process, all the running services are stopped temporarily.

patch –e <hotfix name>

Example: patch –e HF2-6

patch.cmd –e <hotfix name>

Example: patch.cmd –e HF2-6

-qpl

Lists details of a hotfix that is not installed. If you want to view the changes that are included in the hotfix file without installing it on your server, use this option

patch –qpl <location and hotfix name>

Example: patch –qpl /opt/novell/nam/Patches/AM_4512/ AM_4512-6.patch

patch.cmd –qpl <location and hotfix name>

Example: patch.cmd –qpl C:/Patches/AM_4512/ AM_4512-6.patch

-v

Verifies integrity of a hotfix.

patch –v <location and hotfix name>

Example: patch –v /opt/novell/nam/Patches/AM_4512/ AM_4512-6.patch

patch.cmd –v <location and hotfix name>

Example: patch.cmd –v C:/Patches/AM_4512/ AM_4512-6.patch

-t

Verifies if services can be restored by the installer. Use this option to stop/start all services after the installation of hotfix.

patch –t <location and hotfix name>

Example: patch –t /opt/novell/nam/Patches/AM_4512/ AM_4512-6.patch

patch.cmd –t <location and hotfix name>

Example: patch.cmd –t C:/Patches/AM_4512/ AM_4512-6.patch

4.0 Verifying Version Numbers After Upgrading to 4.5.1.2

After upgrading to Access Manager 4.5.1.2, verify that the version number of the component is indicated as 4.5.1.2-6. To verify the version number, perform the following steps:

  1. In Administration Console Dashboard, click Troubleshooting > Version.

  2. Verify that the Version field displays 4.5.1.2-6.

5.0 Known Issues

Access Manager 4.5.1.2 has no known issues.

6.0 Contact Information

Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.

For detailed contact information, see the Support Contact Information website.

For general corporate and product information, see the NetIQ Corporate website.

For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.

7.0 Legal Notice

For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see https://www.netiq.com/company/legal/.

Copyright © 2020 NetIQ Corporation, a Micro Focus company. All Rights Reserved.