RSA Authentication Manager Log Messages (23001-23091)

Processing authentication packet from agent “{3}” with IP address “{4}” in security domain “{5}”

Received unsupported request from agent “{3}” with IP address “{4}” in security domain “{5}”. Request type: “{18}”

Log request received from agent “{3}” with IP address “{4}” in security domain “{5}”

Verifying user “{0}” in security domain “{1}” from identity source “{2}” is allowed access to agent “{3}” with IP address “{4}” in security domain “{5}”

Verifying node secret for the agent “{3}” with IP address “{4}” in security domain “{5}”

Node secret sent to agent “{3}” with IP address “{4}” in security domain “{5}”

Unable to process secondary segments for request from agent “{3}” with IP address “{4}” in security domain “{5}”. Secondary segment request will be ignored

Attempting to resolve user by userid or alias “{0}”. Request originated from agent “{3}” with IP address “{4}” in security domain “{5}”

Session operation failure processing request from agent “{3}” with IP address “{4}” in security domain “{5}”

New pin cancelled for user“{0}”. Request originated from agent “{3}” with IP address “{4}” in security domain “{5}”

Administrator “{0}” attempted to create token “{4}” stored in identity source “{6}” managed in security domain “{5}”

Administrator “{0}” attempted to update token “{4}” stored in identity source “{6}” managed in security domain “{5}”

Administrator “{0}” attempted to delete token “{4}” stored in identity source “{6}” managed in security domain “{5}”

Administrator “{0}” attempted to search for token statistics

Offline authentication attempted by user “{0}” on agent “{3}” using token with serial number “{8}” at “{10}”

Offline authentication data download requested by user “{0}” from agent “{3}” using token “{8}”

Offline authentication data download requested by user “{0}” from agent “{3}” using token “{8}” failed with error message “{9}”

Windows password updated for user “{0}”

Domain secret updated for agent “{3}”

New pin mode activated for token serial number “{16}” assigned to user “{0}” in security domain “{1}” from “{2}” identity source

Next tokencode mode activated for token serial number “{16}” assigned to user “{0}” in security domain “{1}” from “{2}” identity source

original token deleted

original token unassigned

Passcode reuse or previous token code detected for user “{0}” in security domain “{1}” from “{2}” identity source. Request originated from agent “{3}” with IP address “{4}” in security domain “{5}” with protocol version “{2}”. Authentication method: “{6}” ; Authentication policy exp: “{7}”

SID method

User “{0}” in security domain “{1}” from identity source “{2}” attempted to change pin for token serial number “{16}”

Administrator “{0}” attempted to change fixed passcode

Lookup authentication agent by IP address “{4}”

Received an agent auto-registration request from IP address “{4}”

New authentication agent “{3}” with primary IP address “{4}” was registered with Authentication Manager in Security Domain “{5}”

Getting Security Domain for agent “{3}” with primary IP address “{4}” for auto-registration. Agent Security Domain is “{5}”

Found another agent “{8}” with the same IP address “{4}” while trying to auto-register agent “{3}”

Updated agent “{3}” with the new IP address “{4}” in Security Domain “{5}”

found another agent with the same IP address. Unassigning IP address

Registering new agent “{3}” in Security Domain “{5}”. Found agent with the same name and IP address “{4}”

Verifying node secret for the agent “{3}” with IP address “{4}” in Security Domain “{5}”

but it does not exist

found another agent with the same alias IP address

Cleared node secret for the agent “{3}” in Security Domain “{5}”

User “{0}” in security domain “{1}” from identity source “{2}” in trusted realm “{13}” attempted to change pin for token serial number “{16}”

Passcode reuse or previous token code detected for user “{0}” in security domain “{1}” from “{2}” identity source. Request originated from trusted realm “{13}” with agent “{3}” with IP address “{4}” in security domain “{5}” with protocol version “{2}”. Authentication method: “{6}” ; Authentication policy exp: “{7}”

User “{0}” attempted to authenticate using authenticator “{6}” from Trusted Realm “{13}”. The user belongs to Security Domain “{1}”

Trusted user “{0}” attempted to authenticate using authenticator “{8}” at trusted realm “{9}”. The user belongs to Security Domain “{1}”

Next tokencode mode activated for token serial number “{11}” assigned to user “{0}” in security domain “{1}” from the trusted realm “{8}”.

User “{0}” in security domain “{1}” from the trusted realm “{9}” created new pin for token serial number “{10}”.

New pin mode activated for token serial number “{16}” assigned to user “{0}” in security domain “{1}” from “{2}” identity source. Request received from trusted realm “{13}”

Next tokencode mode activated for token serial number “{16}” assigned to user “{0}” in security domain “{1}” from “{2}” identity source. Request received from trusted realm “{13}”

The trusted user “{0}” was discovered in the trusted realm “{9}”.

The user login “{0}” could not be discovered in the local realm or by searching configured trusted realms.

Token with serial number “{8}” does not have any more one time tokencodes associated with it.

Fixed emergency access tokencode associated with token with serial number “{8}” has expired.

One time emergency access tokencode set associated with token with serial number “{8}” has expired.

User “{0}” attempted to resume the existing EAP-32 Session.

Attempting to resolve trusted user by userid “{0}”. Request originated from agent “{3}” with IP address “{4}” in security domain “{5}”

AM61 Migrated log message. Original message: “{8}”.

The Trusted Realm “{9}” has rejected the connection.

The Trusted Realm “{9}” is disabled.

There is no NTLM mapping for “{8}”.

Could not lookup NTLM mapping for “{8}”.

User “{0}” attempted EAP-32 authentication

User “{0}” received new EAP-32 Pepper

Token serial number “{16}” assigned to user “{0}” in security domain “{1}” from identity source “{2}” is expired

User “{0}” in security domain “{1}” from identity source “{2}” attempted to change pin for On-Demand Tokencode Service

Passcode reuse or previous token code detected for user “{0}” in security domain “{1}” from “{2}” identity source. Request originated from agent “{3}” with IP address “{4}” in security domain “{5}” with protocol version “{2}”. Authentication method: “{6}” ; Authentication policy exp: “{7}”

New pin mode activated for On-Demand Tokencode Service for user “{0}” in security domain “{1}” from “{2}” identity source

Verifying trusted user “{0}” in security domain “{1}” from identity source “{2}” is allowed access to agent “{3}” with IP address “{4}” in security domain “{5}”

Auto-registration update for the agent “{3}” with IP address “{4}” in Security Domain “{5}”

Bad tokencode ; but good PIN detected for token serial number “{16}” assigned to user “{0}” in security domain “{1}” from “{2}” identity source

Bad PIN ; but good tokencode detected for token serial number “{16}” assigned to user “{0}” in security domain “{1}” from “{2}” identity source

Bad PIN ; but previous tokencode detected for token serial number “{16}” assigned to user “{0}” in security domain “{1}” from “{2}” identity source

Next tokencode mode accepted for token serial number “{11}” assigned to user “{0}” in security domain “{1}” from the trusted realm “{8}”.

Authentication artifact validation on agent “{3}” with IP address “{4}” in security domain “{5}” for user “{0}” in security domain “{1}” from “{2}” identity source

Received a SecurID credential ; which the agent is configured to not accept. Agent “{3}” with IP address “{4}” in security domain “{5}”.

Authentication artifact was generated for principal “{0}” stored in identity source “{2}” managed in security domain “{1}”

The user “{0}” could not be discovered in the RSA trusted realm

Authenticate Tokencode verification failed for the user “{0}”