RSA Authentication Manager 8.2 Troubleshooting Guide
RSA Authentication Manager 8.2 Troubleshooting Guide
2
Troubleshooting Guide
Contact Information
RSA Link at https://community.rsa.com contains a knowledgebase that answers common questions and provides solutions
to known problems, product documentation, community discussions, and case management.
Trademarks
RSA, the RSA Logo and EMC are either registered trademarks or trademarks of EMC Corporation in the United States and/or
other countries. All other trademarks used herein are the property of their respective owners. For a list of RSA trademarks, go
to www.emc.com/legal/emc-corporation-trademarks.htm#rsa.
License Agreement
This software and the associated documentation are proprietary and confidential to EMC, are furnished under license, and
may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice
below. This software and the documentation, and any copies thereof, may not be provided or otherwise made available to any
other person.
No title to or ownership of the software or documentation or any intellectual property rights thereto is hereby transferred. Any
unauthorized use or reproduction of this software and the documentation may be subject to civil and/or criminal liability.
This software is subject to change without notice and should not be construed as a commitment by EMC.
Third-Party Licenses
This product may include software developed by parties other than RSA. The text of the license agreements applicable to
third-party software in this product may be viewed on the product documentation page on RSA Link. By using this product, a
user of this product agrees to be fully bound by terms of the license agreements.
Note on Encryption Technologies
This product may contain encryption technology. Many countries prohibit or restrict the use, import, or export of encryption
technologies, and current use, import, and export regulations should be followed when using, importing or exporting this
product.
Distribution
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS
PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
Copyright © 1994-2016 EMC Corporation. All Rights Reserved. Published in the U.S.A.
June 2016
RSA Authentication Manager 8.2 Troubleshooting Guide
Contents
Preface................................................................................................................................... 5
About This Guide................................................................................................................ 5
RSA Authentication Manager 8.2 Documentation.............................................................. 5
Support and Service ............................................................................................................ 7
Before You Call Customer Support............................................................................. 7
............................................................................................................................................. 7
3
RSA Authentication Manager 8.2 Troubleshooting Guide
4
RSA Authentication Manager 8.2 Troubleshooting Guide
Preface
Title Purpose
Configuration
Hardware Appliance Getting Started Describes how to deploy a hardware appliance and perform
the Authentication Manager Quick Setup process.
Virtual Appliance Getting Started Describes how to deploy a virtual appliance and perform the
Authentication Manager Quick Setup process.
Setup and Configuration Guide Describes how to set up and configure Authentication
Manager, and how to upgrade from version 8.1 Service Pack
1 to version 8.2.
Administration
Preface 5
RSA Authentication Manager 8.2 Troubleshooting Guide
Title Purpose
Help Desk Administrator’s Guide Provides instructions for the most common tasks that a Help
Desk Administrator performs.
RSA RADIUS Reference Guide Describes the usage and settings for the initialization files,
dictionary files, and configuration files used by RSA
RADIUS.
AMBA Custom Application Guide Describes how the RSA Authentication Manager Bulk
Administration (AMBA) command-line utility simplifies the
bulk administration of users, tokens, agents, and so on.
Requires a standalone AMBA license or an Enterprise
license.
Online Help
Operations Console Help Describes configuration and setup tasks performed in the
Operations Console.
Self-Service Console Help Describes how to use the Self-Service Console. To view the
Help, on the Help tab in the Self-Service Console, click
Self-Service Console Help.
6 Preface
RSA Authentication Manager 8.2 Troubleshooting Guide
Title Purpose
RSA Token Management Snap-In for the Describes how to use software that works with the Microsoft
Microsoft Management Console Help Management Console (MMC) for deployments that have an
Active Directory identity source. Using this snap-in, you can
enable or disable a token, assign a token, or perform other
token-related tasks without logging on to the Security
Console.
Preface 7
RSA Authentication Manager 8.2 Troubleshooting Guide
13003 - AUTHN_LOCKOUT_EVENT
Message: Users “{0}” from security domain “{1}” in identity source “{2}” is locked
out
Description: Principal lockout
Problem: Authentication Manager has locked a user out of the system.
16044 - ACCESS_DATABASE
Message: Database access attempted by system
Description: Database access
Problem: An unexpected error occurred when a database access was attempted using
utilities that are different from those used by the Operations Console or Security
Console.
Resolution: Verify if the database is operating correctly and if sufficient storage space
is available.
16075 - INITIALIZE_PERMISSIONS
Message: System attempted to load permission types from the database
Description: Initialize permissions
Problem: An unexpected error has occurred when loading administrative role
permissions from the database.
Resolution: Verify if the database is operating correctly and if sufficient storage space
is available.
16089 - DENIAL_OF_SERVICE
Message: Denial-of-service attack detected. Server received “{4}” failed
authentications from user “{3}”
Description: Denial-of-service attack detected
Problem: Authentication Manager has detected a series of unsuccessful
authentication attempts from a remote administrative SDK application, suggesting
that an unauthorized individual is attempting to authenticate. The SDK application
might not have the correct WebLogic command client username and password, which
would cause authentication attempts to fail.
16112 - REMOVE_ORPHANED_PRINCIPALS
Message: Administrator “{0}” attempted to clean up unresolvable users
Description: Clean up unresolvable users
Problem: Authentication Manager cannot connect to the LDAP directory server.
Resolution: Confirm that the LDAP directory server(s) identified in the identity
source connection information are running and can be connected from the server.
16262 - BATCH_CLEANUP_ORPHANED_PRINCIPALS_LIMIT_HIT
Message: Cleanup of unresolvable users was not possible. Found {3} users ; which
exceeded the automated cleanup limit of {4} users.
Description: Clean up unresolvable users and groups
Problem: The Cleanup Limit canceled an automated cleanup job because more than
the specified number of unresolvable users were found in the database.
16264 - MARK_FIND_PRINCIPAL_ACROSS_IDENTITYSOURCE_FAI
LURE
Message: User cannot be found across identity sources. User “{3}” will not be
allowed to authenticate for the next 60 minutes..
Description: System cannot process this authentication request
Problem: The user who attempted to authenticate cannot be found in any identity
source.
16265 - DETERMINE_RELATED_IDENTITY_SOURCE
Message: System cannot determine whether identity source “{3}” and identity source
“{4}” are connecting to the same directory server.
Description: Attempting to determine whether the given identity sources connect to
the same directory server.
Problem: A connectivity problem exists between the identity source and the LDAP
directory server. This problem can occur for any of the following reasons:
• Incorrectly configured firewall
• Invalid or expired LDAP credentials
• Certificate expiration
16294 - IDENTITY_SOURCE_GET_CONNECTION_FAILED
Message: Cannot process requests that need access to identity source “{3}”. The
identity source is currently unreachable.
Description: Failed to connect to identity source.
Problem: Authentication Manager cannot connect to the identity source. This
problem can occur for any of the following reasons:
• Incorrectly configured firewall
• Invalid or expired LDAP credentials
• Certificate expiration
• Incorrectly configured or altered LDAP filters
• Network issues
16296 - TRACK_USER_MOVE_IN_REPLICA_FAILED
Message: The user’s distinguished name has changed. Either the primary could not
update the user or the primary cannot be contacted. Authentication requests from
“{3}” to this instance will not be successful until primary updates the user.
Description: System cannot process this authentication request
Problem: A connectivity problem exists between the primary and replica instances.
16297 - BUILD_RELATED_IDENTITY_SOURCE_CACHE_FAILED
Message: System cannot initialize related identity sources for identity source “{3}”
Description: System cannot initialize related identity source cache.
Problem: Authentication Manager cannot connect to the identity source. This error
can occur under the following circumstances:
• The firewall is configured incorrectly.
• LDAP credentials are invalid or expired.
• A certificate has expired.
• LDAP filters are configured incorrectly or altered.
• Network issues exist.
16329 - READ_ACTIVE_USERS
Message: System failed to read the licensed number of active users from the system
configuration
Description: Unable to read active users from the system configuration
Problem: Authentication Manager licensing is incorrect.
Resolution: Confirm that Authentication Manager has a valid license file. In the
Security Console Help, see the topic “Check License Status.”
20056 - INSUFFICIENT_PRIVILEGE
Message: Administrator “{0}” attempted an action having insufficient privileges.
Description: Insufficient Privilege
Problem: The administrator has insufficient privileges to perform the attempted
action.
20063 - AUTHMGR_AGENT_CLEAR_NODESECRET
Message: Administrator “{0}” attempted to clear node secret for agent “{4}”
managed in security domain “{5}”
Description: Clear Agent Node Secret
Problem: The node secret has been cleared. No troubleshooting is required.
20214 - AM_CONFIGURATION_UPDATE_FAILED
Message: Administrator “{0}” failed to update AM configuration
Description: Failed to update AM configuration
20239 - EXPORT_DATA_TO_FILE
Message: Administrator “{0}” attempted to export data to the file “{11}”.
Description: Export Data to file
Problem: The administrator attempted to export user and token data to a file. No
troubleshooting is required.
20240 - GENERATE_EXPORT_SECURITY_PACKAGE
Message: Administrator “{0}” attempted to generate and download export security
package.
Description: Generate Export Security Package
Problem: The administrator attempted to generate and download the export security
package. No troubleshooting is required.
23002 - AUTH_UNSUPPORTED_PROTOCOL
Message: Received unsupported request from agent “{3}” with IP address “{4}” in
security domain “{5}”. Request type: “{18}”
Description: Received unsupported request.
Problem: The device is unsupported because there is no server interface to handle this
type of network packet.
23005 - AUTH_NODE_VERIFICATION
Message: Verifying node secret for the agent “{3}” with IP address “{4}” in security
domain “{5}”
Description: Node secret verification
Problem: There is a problem with the node secret.
Resolution: Clear the node secret in both the Authentication Manager server and
agent. See the Security Console Help topic “Manage the Node Secret.”
23008 - AUTH_PRINCIPAL_RESOLUTION
Message: Attempting to resolve user by userid or alias “{0}”. Request originated
from agent “{3}” with IP address “{4}” in security domain “{5}”
Description: Resolve principal by userid/alias
Problem: Authentication Manager cannot identify the user through the User ID or
alias. It is possible that multiple users have the same alias. When an administrator
associates an agent and a group, all of the user’s aliases associated with the group are
now searched.
This error can occur under the following circumstances:
• An agent is associated with many groups and two people in different groups have
the same alias.
• An administrator recently associated an agent with a group.
23017 - OA_DATA_DOWNLOAD_FAILED
Message: Offline authentication data download requested by user “{0}” from agent
“{3}” using token “{8}” failed with error message “{9}”
Description: Offline Authentication Data Download Failed
Problem: A user’s attempt to download offline authentication data failed. This
message can occur when the offline authentication policy settings for the user do not
match the settings for the agent. This can also occur if port 5580/tcp is inaccessible.
23021 - AUTHMGR_NEXT_TOKENCODE_ACTIVATED
Message: Next tokencode mode activated for token serial number “{16}” assigned to
user “{0}” in security domains “{1}” from “{2}” identity source.
Description: Next tokencode mode activated for token
Problem: A user has failed to authenticate with a specific token more times than the
token policy allows. In next tokencode mode, the user has one chance to enter the
tokencode correctly before authentication fails.
Note: Incorrectly or unnecessarily changing the system time may cause a total
authentication outage. If you are not confident of the cause of the problem, contact
RSA Customer Support. Do not attempt to correct clock drift if it is more than plus or
minus one minute.
23026 - AUTOREG_VERIFY_NODESECRET
Message: Verifying node secret for the agent “{3}” with IP address “{4}” in Security
Domain “{5}”
Description: Agent node secret verification
Problem: This message indicates that there is a problem with the node secret.
Resolution: Clear the node secret in both the Authentication Manager server and
agent. See the Security Console Help topic “Manage the Node Secret.”
23036 - AUTOREG_VERIFY_NODESECRET
Message: Verifying node secret for the agent “{3}” with IP address “{4}” in Security
Domain “{5}”
Description: Agent node secret verification
Problem: There is a problem with the node secret.
Resolution: Clear the node secret in both the Authentication Manager server and
agent. See the Security Console Help topic “Manage the Node Secret.”
23038 - AUTOREG_DHCP_ERROR
Message: While registering an agent “{3}” ; found another agent “{8}” with the same
alias IP address “{4}”. Could not un-assign IP from “{8}”
Description: While registering an agent found another agent with the same alias IP
address.
Problem: During agent registration, another agent was found to have the same alias IP
address.
Port Function
5. Clear the node secret files on the agent. For instructions, see the authentication
agent documentation.
6. Re-install the authentication agent. Choose custom installation, and select
auto-registration during the install process. See your agent documentation for
instructions.
23039 - AUTOREG_CLEAR_NODESECRET
Message: Cleared node secret for the agent “{3}” in Security Domain “{5}”
Description: Agent node secret has been cleared
Problem: The administrator has manually cleared, generated, and reloaded the node
secret. No troubleshooting is required.
23071 - AUTH_FAILED_BAD_TOKENCODE_GOOD_PIN
Message: Bad tokencode ; but good PIN detected for token serial number “{16}”
assigned to user “{0}” in security domain “{1}” from “{2}” identity source
Description: Authentication attempted.
Problem: The user could not successfully authenticate. It is possible that the user has
forgotten the PIN, or is using the wrong token.
23072 - AUTH_FAILED_BAD_PIN_GOOD_TOKENCODE
Message: Bad PIN ; but good tokencode detected for token serial number “{16}”
assigned to user “{0}” in security domain “{1}” from “{2}” identity source
Description: Authentication attempted
Problem: The user who is assigned the token may no longer possess it because the
passcodes are being guessed.
23073 - AUTH_FAILED_BAD_PIN_PREVIOUS_TOKENCODE
Message: Bad PIN ; but previous tokencode detected for token serial number “{16}”
assigned to user “{0}” in security domain “{1}” from “{2}” identity source
Description: Authentication attempted
Problem: This error occurred due to any of the following circumstances:
• The user forgot his or her PIN or is using a PIN that is correct for a different token.
• Replication has failed, and the user’s PIN is not updated in the replica instance.
• An unauthorized person possesses the token and is guessing PINs.
23080 - AUTH_AGENT_DOESNT_ACCEPT_SECURID
Message: Received a SecurID credential ; which the agent is configured to not
accept. Agent “{3}” with IP address “{4}” in security domain “{5}”
Description: SecurID credential type not accepted
Problem: An agent attempted to submit a SecurID passcode. The agent is configured
to handle users who are enrolled in risk-based authentication (RBA), but it is not
configured to authenticate a SecurID passcode.
23089 - TR_R_VIA_PRINCIPAL_NOT_DISCOVERED
Message: The user “{0}” could not be discovered in the RSA Via Access trusted
realm
Description: Discover the user
Problem: The RSA Via Access user was not found. This message can indicate that
more than one RSA Via Access user has the same User ID in the RSA Via Access
trusted realm. The message might indicate a network or system-level issue, with an
unexpected return code, such as HTTP status code 404 “Page Not Found” or HTTP
status code 500 “Internal Server Error.”
23090 - TR_R_VIA_OTP_VERIFICATION_FAIL
Message: RSA Via Tokencode verification failed for the user “{0}”
Description: Verify RSA Via Tokencode
Problem: RSA Via Tokencode could not be verified in the RSA Via Access trusted
realm. The message might indicate a network or system-level issue, with an
unexpected return code, such as HTTP status code 404 “Page Not Found” or HTTP
status code 500 “Internal Server Error.”
23091 - TR_R_VIA_OTP_NODE_SECRET_UNAVAILABLE
Message: Verifying the node secret for the agent “{3}” with IP address “{4}” in
security domain “{5}”
Description: Agent node secret verification
Problem: The node secret is not set for this agent. A new agent might not have a node
secret, or the node secret might have been cleared on both the agent and the RSA
Authentication Manager instance.
26011 - PROCESS_REFERENTIAL_INTEGRITY_MESSAGES
Message: Administrator “{0}” attempted to process referential integrity message
Description: Process Referential Integrity Message
Problem: An error occurred while promoting a replica instance to a primary instance.
Resolution: Confirm that the replica promotion has completed successfully. Do not
start the severs before this process is complete. In the Operations Console Help, see
the topic “Promote a Replica Instance.”
26041 - ADJUDICATOR_CLOCK_SETBACK
Message: Detected clock setback ; current:“{3}” expected:“{4}”
Description: Clock Setback Detected
Problem: If the time difference is less than plus or minus one minute, the
Authentication Manager system clock may not be synchronized with the Network
Time Protocol (NTP) Server. If the time difference is more than plus or minus one
minute, contact RSA Customer Support.