000011838 - How to enable debug on SecurID Token for Desktop on Macintosh or Windows ?

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000011838
Applies ToRSA SecurID Token 4.1 for Desktop
DEBUG
Macintosh
Windows
IssueHow to enable debug on SecurID token for desktop?
Resolution

Setting the Logging Level for RSA Software Token for Desktop

You can control the amount of information logged by the SecurID Token desktop application
by setting a registry key (Windows) or creating a plist (Mac OS X) in the following
location:

On Macintosh:
? /Library/Preferences/com.rsa.SoftwareTokenLibrary.plist/LogLevel

Value           Meaning
DEBUG        Logs messages that are useful for debugging purposes.
INFO            Logs important application information, in addition to errors (Default).
ERROR        Logs only application errors.
OFF             No information is logged.

Windows Registry Key

XP-32, Win7_32 
\HKLM\SOFTWARE\RSA\Software Token\Library       
Windows Registry Key XP, Win7_64
HKEY_LOCAL_MACHINE\Software\Wow6432Node\RSA\Software Token\LibraryOn Windows:

Note the Doc that shows a location of: 
HKLM/RSA/Software Token/Library/LogLevel 
is incorrect

On Macintosh:

Option 1: Launch  Finder go to the Library\Preferences and edit the file com.rsa.SoftwareTokenLibrary.plist

 

From the doc:

Location of Log Output Files
The logger is configured programmatically to output a rolling file named
RSA_Software_Token_Log.txt in the following location:
? Drive:\ProgramData\RSA (Windows)
? ~/Library/Logs/RSA (OS X , where ~ is the current user's home directory)
The maximum size of the log file is set to 1 MB. When this size limit is reached, a
backup log file named filename.1 (for example, ?RSA_Software_token_log.txt.1?) is
created, and messages are once again logged to the original log file. When the log file
again reaches its size limit, the backup log file is replaced.


Option 2: Convert the plist into xml file. Open the terminal

 

sudo plutil -convert xml1 com.rsa.Software\ Token\\Library.plist

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

        <key>DatabasePath</key>

        <string>~/.RSA/RSA/RSA SecurID Software Token Library/</string>

        <key>InstallDir</key>

        <string>/Library/Frameworks/stauto32.framework/Versions/4/</string>

        <key>LogLevel</key>

        <string>DEBUG</string>

        <key>Plugins.{d0955a53-569b-4ecc-9cf7-6c2a59d4e775}.path</key>

        <string>/Applications/SecurID.app/Contents/Resources/libtokenstoreplugin.dylib</string>

</dict>

</plist>

Log file will appear on console. You can copy the text into a text editor and save it as a file.

Verify if the admin user has correct permissions, get the output of the following commands:

cd /Users/<user name>/.RSA

 ls -alR

 

ls -l /Applications/SecurID.app/Contents/Resources

Admin user should have the write permissions to the above directory.

NotesSee A49266 for more information
Legacy Article IDa49278

Attachments

    Outcomes