Digipass Plug-In for SBR Administrator Reference - Vasco

Digipass Plug-In for SBR Administrator Reference Error and Status Codes
Status
Code
Message Notes
Challenge that cannot be handled a RADIUS Server and the RADIUS Server responds with an
Access-Challenge. An Access-Challenge can only be
handled when the SBR Plug-In forwards the password
unmodified to the RADIUS Server. If the SBR Plug-In
verifies an OTP and forwards the static password to the
RADIUS Server, it is not possible to handle an Access-
Challenge from the RADIUS Server.
It can also occur if you use RADIUS Back-End
Authentication for an IIS Module. In that case, Access-
Challenge is not supported from the RADIUS Server.
1041 No Digipass was found for the given
Serial Number
During a Self-Assignment attempt, the Serial Number
provided by the User was not found in the data store. This
mainly occurs when the Serial Number is entered
incorrectly. It can also occur because the Digipass record is
not in the User's Domain or Organizational Unit.
3001 A Digipass Challenge was returned This status code is the standard code when a challenge is
issued and does not indicate any kind of error.
3002 No challenge was identified for the
authentication
3003 Back-end authentication returned a
Challenge
5001 The user failed the Windows Group
Check
5002 Neither local nor back-end
authentication was done due to policy
and/or user settings
A response to a challenge was given, but no challenge
could be found. The most likely reason for this to occur is
that the challenge is too old and has been removed from
the challenge cache. It can also occur if no 'challenge key'
was supplied with which to look up the challenge.
This occurs when a RADIUS Server responds with an
Access-Challenge, in a case where the SBR Plug-In can
handle it.
The SBR Plug-In decided not to handle an authentication
request due to the Windows Group Check failing. This
can occur when the effective Windows Group Check option
is Pass requests for users not in listed groups back to host
system.
Note that the 'effective' setting is the effective setting of
the Policy, unless the Digipass User Account overrides the
Policy.
The SBR Plug-In decided not to handle an authentication
request because the effective Local Authentication and
Back-End Authentication settings were both None.
Note that the 'effective' settings are the effective settings
of the Policy, unless the Digipass User Account overrides
the Policy.
© 2006 VASCO Data Security Inc. 184