XYGATE User Authentication Reference Manual

XYGATE
®
User Authentication
™
(XUA) 1.85 Reference Manual
Chapter 16. What-if Testing
XYPRO Technology Corporation 153 Proprietary and Confidential
Response? qa123
User : XYPRO.QA (222,031) on 2011-03-28 16:58:03.992948
User Expires : * None *
Password Expires : * None *
Password May Change : * None *
Password Must Change : * None *
Password Expiry Grace : 15 days
Last Logon : 2011-03-16 17:07:34.522623
Last Unsuccessful Lgn : 2011-03-16 17:07:25.992429
Fail count : * None *
Static fail count : 124
Frozen/Thawed : Thawed
Last Modification Time: 2011-03-16 17:07:34.485872
From User : 255,255 SUPER.SUPER
Requestor : $NONE $NONE.NONE.NONE
Ancestor : $NONE $NONE.NONE.NONE
To User : 222,031 XYPRO.QA
Port : $NONE $NONE.NONE.NONE
Dialog ID : 001 Tag=2 Dialog=On
State : 10 RAD authenticate w/pw
subproc check_for_impersonation:begin
Impersonation chars not in password field
Bypassing impersonation since current acl does not require it
Process state 10
Getting RADIUS password from structure.
Setting dialog state to 00010 RAD authenticate w/pw
Mapped UID from XYPRO.QA to qa
Sending Request to RADIUS proxy:
0024YN1U00000008qa+qa123
Received from RADIUS proxy:
0027NN5Y00000011000800a248,
State_RADIUS_AUTHENTICATE return value = 005;
Setting dialog state to 00005 Done
timegroup_check using TIMEGROUP values.
user not in any TIMEGROUP, logon allowed
password-expire field reset in user record
password-expire field reset in userax record
User : XYPRO.QA (222,031) on 2011-03-28 16:58:04.089642
User Expires : * None *
Password Expires : * None *
Password May Change : * None *
Password Must Change : * None *
Password Expiry Grace : 15 days
Last Logon : 2011-03-16 17:07:34.522623
Last Unsuccessful Lgn : 2011-03-16 17:07:25.992429
Fail count : * None *
Static fail count : 124
Frozen/Thawed : Thawed
Last Modification Time: 2011-03-16 17:07:34.485872
UAGROUP RADIUS_AUTHENTICATE Replying with access YES
UAGROUP RADIUS_AUTHENTICATE Outcome is LOGON
SEEP return 00000,00000,00000
Access result - YES using GROUP RADIUS_AUTHENTICATE
In the Example above, user XYPRO.QA was mapped to alias qa based on the
mapping configuration of the UAGROUP RADIUS_AUTHENTICATE. The status of the
user account was checked with the Safeguard. In this case, the mapping was used
and RADIUS authentication was allowed.