Digipass Plug-In for SBR Administrator Reference - Vasco

More documents

Recommendations

Info

Digipass Plug-In for SBR Administrator Reference Field Listings 7 Field Listings 7.1 User Property Sheet Table 30: User Fields Field Name in Administration Interfaces New Password Confirm Password Description These fields are used to modify the static password that is stored in the Digipass User account. If they are left blank, no modification is made. Local Authentication Specifies whether authentication requests for the User account will be handled by the SBR Plug-In using Local Authentication (see the Authenticating Users section in the Product Guide for more details on Local Authentication and Back-End Authentication). Normally, this field will be Default, meaning that the Policy applicable to the authentication request determines the setting. This field on the Digipass User account is used to override the Policy setting for special cases. When Local Authentication is used, there are two factors that determine whether Digipass authentication is used – any Policy restrictions on Digipass Types and/or Applications that can be used and whether the Digipass User account has any assigned Digipass that meet the restrictions. For example, if the Policy requires a DP300 and the User just has a DP700, they cannot use Digipass authentication under that Policy. Options: Back-End Authentication Default Use the setting of the effective Policy. None The SBR Plug-In will not carry out Local Authentication for this User account. They may be handled using Back-End Authentication, or not handled at all by the SBR Plug-In. Digipass/Password The SBR Plug-In will always carry out Local Authentication for this User, using Digipass authentication if possible, otherwise the static password. Back-End Authentication may also be utilized. Digipass Only The SBR Plug-In will always carry out Local Authentication for this User, using Digipass authentication. If Digipass authentication is not possible, the user cannot log in. Back-End Authentication may also be utilized. Specifies whether authentication requests for the User account will be handled by the SBR Plug-In using Back-End Authentication (see the Authenticating Users section in the Product Guide for more details on Local Authentication and Back-End Authentication). Normally, this field will be Default, meaning that the Policy applicable to the authentication request determines the setting. This field on the Digipass User account is used to override the Policy setting for special cases. Options: Default Use the setting of the effective Policy. None Back-End Authentication will not be used. If Needed The SBR Plug-In will utilize Back-End Authentication but only in certain cases: Dynamic User Registration Self-Assignment Password Autolearn Requesting a Challenge or Virtual Digipass OTP, when the Request Method includes a Password Static password authentication, when verifying a Virtual Digipass password-OTP combination or during the Grace Period Always The SBR Plug-In will utilize Back-End Authentication for every authentication request. Disabled Specifies whether a Digipass User account is enabled or disabled. If disabled, authentication © 2006 VASCO Data Security Inc. 82
Digipass Plug-In for SBR Administrator Reference Field Listings Field Name in Administration Interfaces Description for the User will be rejected by the SBR Plug-In. Active Directory only: This attribute will be set to disabled and made read-only if the Active Directory User account is disabled or expired. Otherwise, this attribute will be editable. Locked Specifies whether a Digipass User account is locked or not. If locked, authentication for the User will be rejected by the SBR Plug-In. The Locked indicator is normally set automatically when the User exceeds a certain number of failed authentication attempts. The User Lock Threshold is set in the Policy. Linked User Account It is possible to share Digipass between different User accounts, by linking User accounts together. This feature is intended for the case where one person, such as an administrator, has multiple User accounts. If their accounts are linked, there is no need to give more than one Digipass to that person. This feature is used by assigning the Digipass to one User account, then linking all the other User accounts for the person to the one that has the Digipass. Read-only. Active Directory only: If a User is linked to another User, their Linked User Account field will show the Active Directory format DN (Distinguished Name) of the linked User. The DN shows the full address within Active Directory of the linked User, for example: CN=Test User,OU=Admin,OU=Europe,DC=vasco,DC=com In this example, the linked User is called Test User and they are located in an Organizational Unit Admin, which is inside another Organizational Unit Europe in the vasco.com domain. ODBC Database only: If a User is linked to another User, their Linked User Account field will show the UserId and Domain of the linked User, for example: testuser [vasco.com] Created On The date and time that the Digipass User account was created. Read-only. Last Modified On The date and time that the Digipass User account was last modified. Read-only. Domain ODBC Database only: The Domain to which the User belongs. Read only. Organizational Unit ODBC Database only: The Organizational Unit in which the User is located. This is optional as the User does not have to be located in an Organizational Unit. Read only. The Move command must be used from the User list menu to change this. User Name ODBC Database only: The full name of the User. Email Address ODBC Database only: The email address of the User. Phone No. ODBC Database only: The telephone number of the User. Mobile No. ODBC Database only: The mobile phone number of the User. This will be used for Virtual Digipass logins. Description ODBC Database only: Any descriptive text or notes. Assigned Digipass list This lists all Digipass that are assigned to the User. For each Digipass, the list of active Applications is given with the Application Type indicated in brackets(). For example: 0058384426 RESP_ONLY(RO), CHALLENGE(CR) In this example line, the Digipass with Serial Number 0058384426 has two active Applications: one Response Only Application RESP_ONLY and one Challenge/Response Application CHALLENGE. If the User does not have any Digipass assigned directly, but is linked to another User to use © 2006 VASCO Data Security Inc. 83
Page 1 and 2:
Modify these field values (right-cl
Page 3 and 4:
Digipass Plug-In for SBR Administra
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32: Digipass Plug-In for SBR Administra
Page 81: Digipass Plug-In for SBR Administra
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185:
show all

Digipass Plug-In for SBR Administrator Reference - Vasco

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?