This document describes known issues in RSA Authentication Manager 8.3. If a workaround or fix is available, it is noted or referenced in detail. Many of the workarounds require administrative privileges. If you do not have the required privileges, contact your administrator.
Hyper-V virtual appliance VHD files not found
Tracking Number: AM-31852
Problem: When deploying the version 8.3 Hyper-V virtual appliance, the VHD files cannot be found. The Hyper-V virtual appliance file contains a create_vm.ps1 script that refers to version 8.2 SP1 VHD files.
Workaround: Edit the create_vm.ps1 script to replace 8.2.1 with 8.3.0 in the VHD filenames. The updated lines are as follows:
[string]$VHD1_NAME = "RSA_Authentication_Manager.x86_64-8.3.0-disk1.vhd",
[string]$VHD2_NAME = "RSA_Authentication_Manager.x86_64-8.3.0-disk2.vhd",
After saving the changes, you can deploy the Hyper-V virtual appliance.
Authentication (REST-based RSA SecurID Authentication API)
The minLength and maxLength properties are not returned for SECURID and SECURID_NEXT_TOKENCODE methods
Tracking Number: AM-30791
Problem: When a user attempts authentication with the SECURID or SECURID_NEXT_TOKENCODE methods, the RSA SecurID Authentication API does not return the minLength and maxLength properties. Other methods, such as SECURID_NEWPIN and SECURID_SYSTEM_GENERATED_PIN, return numbers.
Workaround: For SECURID and SECURID_NEXT_TOKENCODE, the server should return a minimum length of 4 and a maximum length of 16.
Date and time when an authentication attempt expires shows the local time and an offset for UTC time
Tracking Number: AM-30797
Problem: The attemptExpires value, which is the date and time when a REST-based authentication attempt will expire, shows the local time for the Authentication Manager instance together with a time zone offset for UTC time. The time zone offset is expressed in hours and minutes, with +hh.mm indicating that the server is ahead of UTC time and -hh.mm indicating that the server is behind UTC time.
Workaround: By design, the Authentication API bases the attemptExpires value upon https://www.w3.org/TR/NOTE-datetime, which defines a profile for ISO-8601, the International Standard for representing dates and times.
Certain REST-based authentication failures are not logged to the Authentication Activity Monitor
Tracking Number: AM-30864
Problem: If you build and deploy authentication agents that use the Authentication API, the following authentication failures are not logged in the Authentication Activity Monitor:
- Authentication fails because an incorrect challenge method name is given.
- Authentication fails because an invalid collected input name is given.
Workaround: Configure the imsTrace.log file to display “Errors.” Do the following:
- In the Security Console, select Setup > System Settings.
- Click Logging.
- Select an instance, and click Next.
- From the Trace Log drop-down list, select Error.
- Click Save.
After an error occurs, you can use SSH to log on to the appliance operating system. View the details in the imsTrace.log file in the /opt/rsa/am/server/logs directory.
AMI deployment procedure should state that m4.large or better instance types are supported on Amazon Web Services (AWS)
Tracking Number: AM-31773
Problem: The AMI deployment procedure says to select an m4.large instance type.
Workaround: As stated in the documented requirements, an administrator can select m4.large or better.
Forward and back arrow buttons do not work when you open Help topics through a direct link
Tracking Number: AM-30700
Problem: After you open a Help topic through the Help on this page menu, the forward and back arrow buttons do not work. If you click Help > All Help Topics, you can use these buttons to display Help topics in the order listed in the Contents frame.
Workaround: After opening a topic through the Help on this page menu, you can search for additional topics or select additional topics through the Contents frame. Selecting a second Help topic enables the forward and back arrow buttons.
Restrict port 7050 for read-only database users to prevent OpenSSL denial of service vulnerabilities
Tracking Number: AM-30811
Problem: Adding read-only database users opens port 7050, which accepts packets from any IP address.
Workaround: To prevent the OpenSSL denial of service vulnerabilities described in https://www.openssl.org/news/secadv/20160922.txt, you must configure the appliance internal firewall to open port 7050 only for the IP addresses that are specified for read-only database users. Do the following:
- Log on to the appliance using an SSH client.
- Enter the following command:
- Change directories:
- Type the following, and then press ENTER:
./configureFirewall.sh close postgres inet,tcp,7050
- Enter the following command, and then press ENTER:
./configureFirewall.sh open-4ip postgres inet,tcp,7050, IP Address
Where IP Address is the IP address through which read-only database users remotely connect to the database.
- Repeat step 5 for each IP address that requires database access.
Appliance internal firewall lists port 7050 as open for a deleted read-only database user’s IP address
Tracking Number: AM-30909
Problem: After you delete a read-only database user, port 7050 is listed as open for the deleted user’s IP address. The deleted user cannot connect with the deleted User ID. Port 7050 can accept packets from the IP address, but no credentials exist to complete the connection.
Workaround: Close port 7050 for the deleted user’s IP address. Deploy the appliance in a subnet that also has an external firewall to segregate it from the rest of the network.
Appliance internal firewall creates more than one ACCEPT rule and DROP rule for the same IP address
Tracking Number: AM-30911
Problem: The appliance has an internal firewall creates an ACCEPT rule and a DROP rule for each user’s IP address in the Authentication Manager internal database. When more than one user has the same IP address, the firewall creates multiple ACCEPT and DROP rules.
Workaround: No additional actions are necessary. The duplicate rules are successfully applied.
Promotion for Maintenance
After promoting a replica instance to primary, attempting to promote the former primary instance back to primary status fails.
Tracking Number: AM-30394, AM-30564
Problem: Promoting a replica instance to primary succeeds, but subsequent attempts to promote the former primary instance back to primary status fail, triggering the message “Promotion was unsuccessful. Unable to extract logs from original primary.”
- Log on to the appliance using an SSH client.
- Change directories:
- Type the following, then press ENTER to update TLS 1.2 Mode properties:
/rsautil store -a enable_min_protocol_tlsv1_2 <setting> restart
- Where <setting> is true if you want to enforce strict TLS 1.2 Mode, or false if you do not.
No information displayed on the primary instance Progress Monitor during a promotion for maintenance
Tracking Number: AM-30839
Problem: If you log onto the Operation Console for the replica instance and promote the replica instance, and then log onto the Operation Console for the current primary instance during the promotion, the primary instance Progress Monitor does not show any information.
Workaround: Log back or remain logged onto the Operation Console of the replica instance during the promotion to view the Progress Monitor information. When the promotion is complete, the Operation Console confirms the promotion to a primary instance with next steps.
Only the administrator running the pre-promotion check on a replica instance can see the status
Tracking Number: AM-30849
Problem: Before promoting a replica instance, you must run the pre-promotion check. Another administrator cannot view the status or results of this task in the Progress Monitor.
Workaround: This functionality is intentional. The pre-promotion check allows the administrator who is promoting the replica instance to identify and correct any issues. When the promotion for maintenance begins, any administrator can view the Progress Monitor on the replica instance that is being promoted.
The first Quick Setup task on a Hyper-V virtual appliance displays a later start time than the second task
Tracking Number: AM-28393
Problem: If you select a Network Time Protocol (NTP) server for RSA Authentication Manager that the Hyper-V host machine does not use, the first Quick Setup task might display a later start time than the second Quick Setup task.
Workaround: This time display issue does not affect deployment or RSA SecurID authentication.
Quick Setup on Amazon Web Services (AWS) does not display the time and date after synchronizing to the physical hardware
Tracking Number: AM-31727
Problem: The AWS virtual appliance requires you to obtain the correct time and date by selecting an NTP server or by synchronizing with the physical hardware hosting the virtual appliance. During Quick Setup on AWS, the time and date is not displayed for the physical hardware option.
Workaround: This issue only affects Quick Setup. The correct time and date is displayed in the Operations Console.
Cannot create IPv4 addresses for IPv6 RADIUS clients after removing IPv6 network settings
Tracking Number: AM-29485
Problem: If you disable IPv6 network settings in the Operations Console, you cannot update existing IPv6 RADIUS clients to use IPv4 addresses.
Workaround: Re-enable IPv6 network settings, update the IPv6 RADIUS clients to use IPv4 addresses, and then disable the IPv6 network settings again. Delete any IPv6 RADIUS clients that are no longer needed.
Authentication Manager does not track which IPv6 RADIUS Clients are sending authentication requests
Tracking Number: AM-29509
Problem: If the <ANY> client is not selected, Authentication Manager should track which IPv6 RADIUS clients are sending authentication requests. Instead, authentication requests using the shared secret specified for the <ANY> client are processed regardless of the originating client’s IPv6 address.
Workaround: This feature works for IPv4 RADIUS clients. This issue is being resolved in a future RSA Authentication Manager 8.2 patch.
RSA SecurID Authenticate Tokencodes
Authentication Manager Bulk Administration (AMBA) utility does not support RSA SecurID Authenticate Tokencodes
Tracking Number: AM-30858
Problem: The RSA Authentication Manager 8.3 Bulk Administration (AMBA) utility does not support the RSA SecurID Authenticate app. For example, you cannot use the unassign or replace token commands for RSA SecurID Authenticate Tokencodes.
Workaround: Use the Security Console to manage Authenticate Tokencodes. For more information, see the Authentication Manager Help topic “RSA SecurID Authenticate Tokencodes.”
No entries for the RSA SecurID Authenticate app on the SecurID Token Statistics page
Tracking Number: AM-30915
Problem: On the SecurID Token statistics page, no information is displayed for the RSA SecurID Authenticate app.
Workaround: All custom reports that display RSA SecurID hardware and software tokens include the RSA SecurID Authenticate app, except for the “Token Expiration Report.” For more information, see “Reports” on RSA Link: https://community.rsa.com/docs/DOC-77230.
RSA Token Management Snap-in (MMC)
RSA Token Management snap-in for Active Directory does not allow administrators to edit certain properties for undistributed software tokens
Tracking Number: AM-30916
Problem: The RSA Token Management snap-in for Active Directory does not allow administrators to edit the Notes field or choose whether to require a PIN for software tokens that have not yet been distributed.
You can change other Authentication Settings, such as clearing an existing PIN, requiring a PIN change on the next logon, and disabling the token.
Workaround: Do one of the following:
- Distribute the software tokens. After the tokens are distributed, you can edit these fields with the RSA Token Management snap-in.
- Use the Security Console to manage all tokens.
Do not promote a version 8.2 SP1 replica instance if there is a version 8.3 primary instance
Tracking Number: AM-29322
Problem: After the primary instance has been upgraded to RSA Authentication Manager 8.3, promoting a version 8.2 SP1 replica instance for disaster recovery creates a second primary instance. The same issue occurs in earlier releases, for example, if you upgrade a primary instance from version 8.2 to version 8.2 SP1 and then promote a version 8.2 replica instance.
Workaround: If the Authentication Manager upgrade does not succeed, you must restore from a backup file, a VMware snapshot, or a Hyper-V checkpoint. Always upgrade the primary instance before upgrading the replica instances in your version 8.1 SP1 deployment.
Web-Tier Installer License Agreement screen includes clickable links that do not open external websites
Tracking Number: AM-30162
Problem: The Web-Tier Installer includes a License Agreement screen that allows you to click the links for external websites. The links redirect you to the top of the license agreement.
Workaround: To visit the external websites, copy each link from the License Agreement screen, and paste it into a browser.
Hardened RSA Authentication Manager 8.3 machine without a Network Time Protocol (NTP) server not restarting after an upgrade
Tracking Number: AM-30172
Problem: If an RSA Authentication Manager 8.2 SP1 machine that was hardened with the ADG Security Control file does not have access to an NTP server, it will not restart after a successful upgrade to RSA Authentication Manager 8.3. The same issue can occur after upgrading a hardened version 8.1 SP1 machine to version 8.2 or a hardened version 8.2 machine to version 8.2 SP1.
Workaround: Before upgrading a hardened machine, select an NTP server as a time source. Go to Administration > Date & Time, and follow the instructions in “Update System Date and Time Settings” on RSA Link: https://community.rsa.com/docs/DOC-76927.
Updating the web tier on Linux creates empty rsa-install folders in the /tmp directory
Tracking Number: AM-30868
Problem: After installing the version 8.2 SP1 web tier on Linux, any updates, such as adding a custom logo, causes the /tmp directory to have empty folders with the prefix “rsa-install.”
Workaround: In the /tmp directory, delete the empty rsa-install folders.
VMware virtual appliance does not include a DVD/CD drive
Tracking Number: AM-28663
Problem: The VMware virtual appliance does not include a DVD/CD drive for applying updates.
Workaround: Use the VMware vSphere Client to shut down the virtual machine and add a DVD/CD drive. For more information, see the Help topic “VMware DVD/CD or ISO Image Mounting Guidelines” on RSA Link at https://community.rsa.com/docs/DOC-77220.
In addition, you can apply Authentication Manager updates through your local browser, or you can scan for stored updates in an NFS share or a Windows shared folder.
Operations Console shows intermittent replication failure on the primary instance
Tracking Number: AM-30373
Problem: The Operations Console displays intermittent reports that replication has failed on the primary instance. Actual replication of data between instances works properly, but the replication status error interferes with all Authentication Manager functions that rely on a system health check.
Workaround: Modify objects (such as users or tokens) using the Security Console, or perform authentication to trigger replication and reset the replication status indicator.
Cannot delete a replica instance while it is being synchronized
Tracking Number: AM-31481
Problem: If you manually synchronize a replica instance with data from the primary instance, you cannot delete the replica instance while it is being synchronized.
Workaround: Wait until synchronization is complete to delete the replica instance.
Changing the User ID clears recent authentication activity from the User Dashboard
Tracking Number: AM-31701
Problem: If you change a User ID, then the User Dashboard will display the time and date of the user’s last successful authentication, but does not display other recent authentication activity. The Recent Authentication Activity component normally displays information from the past seven days.
Workaround: Use another approach to display authentication activity for the original user ID:
- View the Authentication Activity Monitor. For more information, see "Real-Time Monitoring Using Activity Monitors" on RSA Link at https://community.rsa.com/docs/DOC-77411.
- Run a report. For more information, see "Reports" on RSA Link at https://community.rsa.com/docs/DOC-77230.
- Search the Runtime Audit log, if it has been configured to record all authentication activity. For more information, see "Log Messages" on RSA Link at https://community.rsa.com/docs/DOC-77115.