Access Manager Appliance 5.0 Service Pack 2 Patch 1 Release Notes

Access Manager Appliance 5.0 Service Pack 2 Patch 1 (5.0.2.1) supersedes Access Manager Appliance 5.0.2.

For the list of software fixes and enhancements in the previous release, see Access Manager Appliance 5.0.2 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 on the Documentation page.

1.0 Resolved Issues

This release includes the following software fixes:

Component

Bug ID

Issue

OAuth

507001

OAuth clients' authorization code requests fail after upgrading to Access Manager 5.0.2.

Administration Console

509001

After upgrading to 5.0.2, Administration Console does not contain node details of Identity Server and Access Gateway and displays the HTTP 400 Bad Request error.

2.0 Verifying Version Number Before Upgrading to 5.0.2.1

Before upgrading, click Troubleshooting > Version in Administration Console, and ensure that the version of Access Manager is 5.0.2.

3.0 Upgrading to Access Manager 5.0.2.1

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

3.1 Downloading the Patch

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

NOTE:This patch update is not required for Analytics Server.

IMPORTANT:Ensure that you are currently on Access Manager 5.0.2 before upgrading to Access Manager 5.0.2.1.

You need to procure the license key from the Software License and Download portal to register to 5.0.2. For information about how to download the product from this portal, watch the following video:

3.2 Upgrading to Access Manager 5.0.2.1

You can upgrade to Access Manager 5.0.2.1 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 patch, see Silent Patch Upgrade.

  1. Extract the patch file by using the unzip AM_5021.zip command.

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

    Table 1 Files and folders created in the AM_5021 folder after extracting the patch installer ZIP file

    File/Folder Name

    Description

    rpm

    Contains rpm files for the patch.

    installPtool.sh

    Script to install the patch and the patch tool.

    installPatch.sh

    Script to install the patch tool and the updated binaries.

  2. Log in as the root user.

  3. (Conditional) To automate the patch installation, perform the steps mentioned in Silent Patch Upgrade, else continue with Step 4.

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

  5. Run the installPatch.sh command.

    This command installs the patch and the bundled binaries.

    NOTE:To manage the Access Manager patch file, refer to Managing the Patch.

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

3.3 Silent Patch Upgrade

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

  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 patch>/AM_5021/AM_5021-10.patch

3.4 Managing the Patch

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

    /opt/novell/nam/patching/bin

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

Option

Description

Command on Linux server

-qa

Lists all installed patches.

patch -qa

-q

Lists details of an installed patch.

patch –q

Example: patch –q P1-10

-i

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

patch –i <location and patch name>

Example: patch –i /opt/novell/nam/Patches/AM_5021/AM_5021-10.patch

-e

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

patch –e <patch name>

Example: patch –e P1-10

-qpl

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

patch –qpl <location and patch name>

Example: patch –qpl /opt/novell/nam/Patches/AM_5021/ AM_5021-10.patch

-v

Verifies integrity of a patch.

patch –v <location and patch name>

Example: patch –v /opt/novell/nam/Patches/AM_5021/ AM_5021-10.patch

-t

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

patch –t <location and patch name>

Example: patch –t /opt/novell/nam/Patches/AM_5021/ AM_5021-10.patch

4.0 Verifying Version Number After Upgrading to 5.0.2.1

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

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

  2. Verify that the Version field lists 5.0.2.1-10.

5.0 Known Issues

The following issue is currently being researched for Access Manager 5.0.2.1.

Micro Focus strives to ensure that our products provide quality solutions for your enterprise software needs. If you need assistance with any issue, visit Micro Focus Support, then select the appropriate product category.

5.1 Administration Console Dashboard Does Not Display the Latest Version After Applying the Patch

Workaround: Navigate to Troubleshooting > Version to find the correct version.

6.0 Contacting Micro Focus

For specific product issues, contact Micro Focus Support at https://www.microfocus.com/support-and-services/.

Additional technical information or advice is available from several sources: