000021941 - Troubleshooting RSA SecurID problems with Lucent NavisRadius

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

Article Content

Article Number000021941
Applies ToLucent NavisRadius 4.4.4
Sun Solaris 2.8
IssueTroubleshooting RSA SecurID problems with Lucent NavisRadius
CauseLucent NavisRADIUS 4.4.4 is a Java application that interfaces into RSA SecurID using a command line executable called "securidClient"
ResolutionThis executable can be run in total isolation from the rest of the Lucent NavisRADIUS system; doing so can assist in identifying which part of the system is actually at fault, as it excludes anything related to RADIUS. The following steps show how the executable can be run at the command line (run in a bourne shell  /bin/sh):

##
## Change directory to where the executable resides
##
cd /opt/Lucent/NavisRadius/lib/SunOS-sparc
##
## Set the variables needed by our ACE/Agent code to
## find sdconf.rec and the node secret file (securid)
## and other config files used by the agent code
##
. /etc/sdace.txt
export VAR_ACE
##
## Set the variable for the required libraries
LD_LIBRARY_PATH=/opt/Lucent/NavisRadius/lib/SunOS-sparc
export LD_LIBRARY_PATH
##
## Now (optionally set RSA debugging)
##
RSATRACELEVEL=15
export RSATRACELEVEL
##
## Optionally send the debug to file (otherwise it will appear
## on the screen)
##
RSATRACEDEST=aceclient.log
export RSATRACEDEST
##
## Now do an interactive test
##
./securidClient -d


At this point you should get an interactive series of prompts such as the following:

configuration read
socket initialized
user: testuser
password: 1234
user: testuser, password: 1234
2 0 ""

This example shows a success the last line shows the various result codes.
Legacy Article IDa25801

Attachments

    Outcomes