VASCO IDENTIKEY Appliance Administrator Reference
IDENTIKEY Appliance is a device used for secure authentication and authorization. This device helps to protect your network and systems from unauthorized access by verifying the identity of users before they are granted access.
Advertisement
Advertisement
IDENTIKEY
®
Appliance
Administrator Reference
3.11.12
Disclaimer of Warranties and Limitations of Liabilities
Intellectual Property
VASCO Software, documents and related materials (“Materials”) made available on the Site contain proprietary and confidential information. All title, rights and interest in VASCO Software and Materials, updates and upgrades thereof, including software rights, copyrights, patent rights, trade secret rights, sui generis database rights, and all other intellectual and industrial property rights, vest exclusively in
VASCO or its licensors. No VASCO Software or Materials published in this Site may be downloaded, copied, transferred, disclosed, reproduced, redistributed, or transmitted in any form or by any means, electronic, mechanical or otherwise, for any commercial or production purpose, except as otherwise marked or when expressly permitted by VASCO in writing.
Disclaimer
VASCO accepts no liability for the accuracy, completeness, or timeliness of Site content, or for the reliability of links to and content of external or third party websites.
VASCO shall have no liability under any circumstances for any loss, damage, or expense incurred by you, your company, or any third party arising from the use or inability to use VASCO Software or Materials, or any third party material available or downloadable from the Site. VASCO will not be liable in relation to any loss/damage caused by modification of these Legal Notices or Site content.
Reservation
VASCO reserves the right to modify these Notices and the content at any time. VASCO likewise reserves the right to withdraw or revoke consent or otherwise prohibit use of the VASCO Software or Materials if such use does not conform to the terms of any written agreement between VASCO and you, or other applicable terms that VASCO publishes from time to time.
Copyright
Copyright © 2008–2016 VASCO Data Security, Inc., VASCO Data Security International GmbH. All rights reserved.
Trademarks
VASCO
®
, VACMAN
®
, IDENTIKEY
®
, aXsGuard
®
, DIGIPASS
®
, CertiID
®
, CRONTO™, MYDIGIPASS.COM™, the MYDIGIPASS.COM MD Lock logo, the DP+ logo, the VASCO ‘V’ logo, and the CRONTO logo are registered or unregistered trademarks of VASCO Data Security, Inc. and/or VASCO Data Security International GmbH in the U.S. and other countries.
VASCO reserves all rights to the trademarks, service marks and logos of VASCO and its subsidiaries.
Date last modified: 12/2/2016
Table of Contents
1.1. IDENTIKEY Appliance Documentation Set
2. Configuration Tool: Field Listings
2.3. IDENTIKEY Authentication Server Settings
3.1. Default Security Levels for SSL Cipher Suites
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
5.4. Administrative Privileges
5.12. Back-End Server Properties
5.13. Organizational Unit Property Sheet
5.15. Servers – Global Configuration
IDENTIKEY Appliance 3.11.12 - Administrator Reference
Table of Contents
iii
5.17. LDAP Back-End Authentication
7. Importing Users with Comma-Separated Value Files
10.2. Login Permutations Tables
11. Open Port Numbers on Firewall
13.1. IDENTIKEY Appliance Error Codes
13.2. DIGIPASS Authentication for Windows Logon Error Messages
13.3. VACMAN Controller Error Codes
13.4. Console Wizard Error Codes
IDENTIKEY Appliance 3.11.12 - Administrator Reference
Table of Contents
iv
Table of Contents
IDENTIKEY Appliance 3.11.12 - Administrator Reference
v
Table Index
Table 1: Backup and Restore Fields
Table 3: Authentication Fields
Table 7: Notification Settings Fields
Table 8: Notification Filter Fields
Table 9: Notification Target Fields
Table 12: IDENTIKEY Authentication Server General Settings Fields
Table 13: IDENTIKEY Authentication Server SEAL Configuration Fields
Table 14: IDENTIKEY Authentication Server SOAP Configuration Fields
Table 15: IDENTIKEY Authentication Server RADIUS Configuration Fields
Table 16: IDENTIKEY Authentication Server Back-End Settings Fields
Table 17: IDENTIKEY Authentication Server Discovery Fields
Table 18: IDENTIKEY Authentication Server Audit Fields
Table 19: IDENTIKEY Authentication Server Tracing Fields
Table 20: IDENTIKEY Authentication Server Performance Monitoring Fields
Table 21: System Monitoring Settings Fields
Table 22: System Monitoring Target Fields
Table 23: System Monitoring Filter Fields
Table 24: Message Delivery Component Fields
IDENTIKEY Appliance 3.11.12 - Administrator Reference
Table of Contents
vi
Table 29: IDENTIKEY Authentication Server LDAP User Synchronization: General Fields
Table 30: IDENTIKEY Authentication Server LDAP User Synchronization: Attribute Filter Fields
Table 31: IDENTIKEY Authentication Server LDAP User Synchronization: Attribute Mapping Fields
Table 32: Cryptographic Protocols Supported in Different Cipher Suite Security Levels
Table 33: Default SSL Cipher Suite Security Levels for Communication Interfaces
Table 34: Overview of Cipher Suites in the Web Administration Service
Table 37: User - Policy Overrides
Table 38: User - Offline Authentication
Table 39: User - Recent Activity
Table 40: User - Further User Fields
Table 41: User Attribute Fields
Table 43: Administrative Privileges – ODBC Data Store
Table 44: Find/Manage DIGIPASS Criteria
Table 46: DIGIPASS – License Information
Table 47: DIGIPASS – Activation Information (Standard Activation and Licensing)
Table 48: DIGIPASS – Activation Information (Multi-Device Activation and Multi-Device Licensing)
Table 49: DIGIPASS – Recent Activity
Table 50: DIGIPASS Application Fields
Table 52: Policy Properties - Policy
Table 53: Policy Properties - User
Table 54: Policy Properties – DIGIPASS
Table 55: Challenge Policy Fields
Table 56: Secure Channel Policy Fields
Table 57: Virtual DIGIPASS Policy Fields
IDENTIKEY Appliance 3.11.12 - Administrator Reference
Table of Contents
vii
Table 58: DIGIPASS Control Parameters
Table 59: Offline Authentication
Table 60: Password Randomization
Table 61: Dynamic Component Registration
Table 68: RADIUS Back-End Server Fields
Table 69: Microsoft Active Directory Back-End Server Fields
Table 70: NetIQ eDirectory Back-End Server Fields
Table 71: Back-End Server Settings Fields
Table 72: Organizational Unit Fields
Table 74: Global Configuration – Auditing
Table 75: Global Configuration – MDC Virtual DIGIPASS Message Settings
Table 76: Global Configuration – MDC Virtual Signature Message Settings
Table 77: Global Configuration – MDC Offline Activation Data Message Settings
Table 78: Global Configuration – MDC DP Activation Delayed
Table 79: Global Configuration – MDC DP Activation Completed
Table 80: Message Template Placeholders
Table 81: Server List – Summary
Table 82: Supported User Logon Format for Microsoft Active Directory
Table 83: Supported User Logon Format for NetIQ eDirectory
IDENTIKEY Appliance 3.11.12 - Administrator Reference
Table of Contents
viii
Table 87: Performance Monitoring CSV output file format
Table 88: SNMP Traps - Parameters
Table 90: Login Permutations - Response-OnlyCleartext Separate
Table 91: Login Permutations - Response-Only Separate
Table 92: Login Permutations - Response-Only CHAP/MSCHAP/MSCHAP2
Table 93: Login Permutations – 2-Step Challenge/Response Cleartext Separate
Table 94: Login Permutations – Virtual DIGIPASS
Table 95: Incoming Ports used by IDENTIKEY Appliance
Table 96: Outgoing Ports used by IDENTIKEY Authentication Server
Table 99: Audit Messages (specific to IDENTIKEY Applianceonly)
Table 101: DIGIPASS Authentication for Windows Logon Error Messages
Table 102: VACMAN Controller Error Codes – Authentication and Administration
Table 103: VACMAN Controller Error Codes - DIGIPASS record import
Table 104: Console Wizard Error Codes
Table 106: Tracing Message Types
Table 107: Tracing Message Levels
Table 108: Tracing Message Contents
Table of Contents
IDENTIKEY Appliance 3.11.12 - Administrator Reference
ix
1. Introduction
1. Introduction
IDENTIKEY Appliance Administrator Reference is part of the documentation set about IDENTIKEY Appliance . It provides field explanations and other organized reference material for technical experts using IDENTIKEY Appliance and is intended for reference only.
If not stated otherwise, the information in this guide also applies to IDENTIKEY Virtual Appliance.
1.1. IDENTIKEY Appliance Documentation Set
The following IDENTIKEY Appliance guides are available: n n n n n n n n
IDENTIKEY Appliance Administrator Guide . Explains the steps needed for administration tasks, including monitoring and troubleshooting.
IDENTIKEY Appliance Administrator Reference . Provides field explanations and other organized reference material for technical experts using IDENTIKEY Appliance intended for reference only.
IDENTIKEY Appliance Installation and Maintenance Guide . Explains the steps required to connect the
IDENTIKEY Appliance to your network, first-time configuration and maintenance procedures, such as updating and re-licensing.
IDENTIKEY Appliance Product Guide . Describes the structure of the product, the concepts underpinning authentication and how IDENTIKEY Appliance can support authentication within an existing infrastructure.
IDENTIKEY Authentication Server SDK Programmer Guide . Provides in-depth information required for development work using the SDK. This document is relevant to SOAP Authentication, electronic signatures and provisioning using the IDENTIKEY Appliance.
Documents about DIGIPASS Authentication for Windows Logon. Provide information about the concepts, installation and configuration, setup, and procedures to test DIGIPASS Authentication for Windows Logon.
Two Password Synchronization Manager guides for installation and usage information.
Filter guides for each available filter for installation and usage information.
Access to the IDENTIKEY Appliance documentation is provided via the IDENTIKEY Appliance Configuration Tool.
Manuals for IDENTIKEY Appliance add-ons are provided on the CD-ROM delivered with the appliance.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
10
2. Configuration Tool: Field Listings
2. Configuration Tool: Field Listings
2.1. System
2.1.1. Backup & Restore
Table 1: Backup and Restore Fields
Field Name Description
Backup Encryption
Use Custom
Encryption Pass
Phrase
Check this option to provide a password for backups. All backups are encrypted, and can be restored using the administrator's default credentials. However, with this option you can provide a different password specifically for restoring backups.
Backup encryption passwords are applied to both automated and scripted backups.
Use this field to supply a custom password to decrypt encrypted backups.
Custom Encryption Pass Phrase
Confirm Confirmation of the above password.
Automatic Backups
IDENTIKEY Appliance 3.11.12 - Administrator Reference
11
2. Configuration Tool: Field Listings
Table 1: Backup and Restore Fields (continued)
Field Name Description
Protocol For the backup server, two protocols, FTP or SFTP, are available. Select the check box of the relevant protocol to be used on the backup server. The fields to adjust the settings of the selected protocol are displayed after the protocol was selected.
FTP Authentication Settings
FTP server
FTP directory
Username
Password
SFTP Authentication Settings
SFTP server
SSH Server RSA Fingerprint
The FQDN or IP address of the FTP server
The directory of the SFTP / FTP server in which to place the backup files.
The FTP server user name
The FTP server password
SFTP directory
Authentication Method
Username
Public Key
The FQDN or IP address of the SFTP server
Enter the address of the SSH server fingerprint manually; the fingerprint should be generated by the RSA algorithm. Alternatively, you can click the
Fetch Fingerprint button (after the SFTP server has been filled in) to supply the SSH server RSA fingerprint.
The directory of the SFTP / FTP server in which to place the backup files.
Public Key: Select this method to authenticate with the public key of the SFTP user.
Password: Select this option to authenticate with a classic user name / password pair.
The SFTP server user name
The public key of the IDENTIKEY Appliance, which has to be downloaded for public key authentication when the Public Key authentication method is selected.
Generic settings
Test Settings
Schedule
Click this link to test your configuration
Set the desired schedule for the automatic backups.
Scripted Backups
Enabled Check this option to enable scripted backups. A scripted backup is intended for advanced administrators who prefer to use their own scripts to create IDENTIKEY Appliance backups. The backups can only be retrieved via HTTPS (use wget in your backup scripts).
More information is available in the IDENTIKEY Appliance Install and configuration guide.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
12
2. Configuration Tool: Field Listings
Table 1: Backup and Restore Fields (continued)
Field Name Description
Username
Password
Confirm
The user who is allowed to take scripted backups
The password of the above user
Confirm the password
Allowed Networks The networks from which the user may fetch IDENTIKEY Appliance backups. Use the CIDR notation.
Test Backup Click on this link to test the currently saved configuration. If you performed any recent configuration changes, save them first before clicking the link.
2.2. Settings
2.2.1. System
Table 2: System Fields
Field Name
Settings
Hostname
Description
This is the internal name of IDENTIKEY Appliance and is used: n n to uniquely identify log lines when sent to a remote syslog server. For more information refer to the IDENTIKEY ApplianceProduct Guide , Section "Logging".
to identify an IDENTIKEY Appliance in a replication setup
Time
Time zone
NTP Servers
Each log line and audit event in the IDENTIKEY Appliance is generated with a time stamp. This time zone field determines the time-offset of the time stamp. We recommend setting the time zone to 'UTC' (= Greenwich Mean Time) for an efficient support service.
List of NTP servers used in the company network. The Network Time Protocol (NTP) is designed to synchronize the clocks of computers over a network. If multiple servers are specified, the NTP service will attempt to synchronize allservers. To provide redundancy, it is good practice to configure multiple servers. In general, best accuracy is obtained by using servers that have a low network latency.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
13
2. Configuration Tool: Field Listings
2.2.2. Authentication Settings
Table 3: Authentication Fields
Field Name Description
Sysadmin User
Enabled
Password
Clear to disable the sysadmin user.
Change the password of the sysadmin user
IDENTIKEY Authentication Server Web Administration
Share IAS Web Administration
Session
Select this option to enable session sharing between the Configuration Tool and Administration
Web Interface. If enabled, users with the Appliance Administration privilege can log in once, either to the Configuration Tool or the Administration Web Interface, to access both applications.
Selecting / clearing this option takes effect only for new sessions and does not affect existing sessions.
Rescue Users
Number of Additional Logins
Required
Rescue Users
Use this field to specify the number of credential sets required in addition to the rescue log in.
This is to protect the rescue facility, and enable only a certain set of administrators to use the features it provides. By default, the rescue login does not have a password.
Click Add Rescue User and enter the user name and password. Click Save . The number of users defined here must correspond to the number of additional logins required field above.
2.2.3. Network Settings
Table 4: Network Fields
Field Name
Address and Routing
IP Address
Description
Default Gateway
List of the IP addresses of the IDENTIKEY Appliance used to communicate within the company network. The Classless Inter Domain Routing (CIDR) notation is used, for instance 192.168.0.100/24.
The default gateway is a server in your network, which routes the traffic from the
IDENTIKEY Appliance to the outside network. Enter the default gateway for your network.
DNS Settings
IDENTIKEY Appliance 3.11.12 - Administrator Reference
14
2. Configuration Tool: Field Listings
Table 4: Network Fields (continued)
Field Name
DNS Suffixes
DNS Servers
Description
List of domain suffixes. The DNS search path or DNS suffix is used to complete a partial DNS name whenever a DNS lookup is performed, for example 'intranet' is completed to 'intranet.mycompany.com'. Enter the domain used within your company in this field. A partial DNS name is completed with each domain starting from the top of the list until a valid DNS name is found.
List of DNS servers used in your network. A DNS server is used to convert human readable DNS names into IP addresses used in the network. The first entry in the list is used to perform DNS resolving. A subsequent server in the list is used if the previous DNS server in the list is unavailable.
Proxy Server
A proxy server is used in larger companies and organizations to improve network operations and security. It can be used to prevent direct communication between two or more networks. A proxy server forwards all allowed data requests to remote servers.
The use of a proxy server is optional. Proxy authentication works for basic authentication and DIGEST authentication, but not for form-based authentication.
Use Proxy Server for HTTP(S) Click the check box to enable/disable use of a proxy server.
Proxy Server
Port
Enable Authentication
Enter the IP address of the proxy server used in your network.
Enter the IP port used to contact your proxy server.
Click the check box to enforce authentication for HTTP(S) access through the proxy server.
User Name
Password
Enter the user name to authenticate towards the proxy server in your network before a connection is allowed.
Enter the password for the supplied user name to authenticate towards the proxy server in your network before a connection is allowed.
2.2.4. SNMP
These settings allow you to define SNMP traps, SMS and email warnings for critical system OS events. For more details about system monitoring, refer to Chapter
Table 5: SNMP Fields
Field Name Description
SNMP
IDENTIKEY Appliance 3.11.12 - Administrator Reference
15
2. Configuration Tool: Field Listings
Table 5: SNMP Fields (continued)
Field Name Description
Enable SNMP v2c
Enable SNMP v3
Check to enable the Simple Network Management Protocol (SNMP) v2c. This allows you to use an SNMP client to manage and monitor the IDENTIKEY Appliance. SNMP v2c: SNMPv2 (RFC
1441–RFC 1452) includes improvements in the areas of performance, security, confidentiality, and manager-to-manager communications.
Note : SNMP v1 is also supported by selecting the v2c option
With this option enabled, the following options will also need to be configured: n n
Read community . Defines the relationship between the IDENTIKEY Appliance SNMP server and the client system. The community string acts as a password to control the clients' access to the server
Allow query from . Specifies the sources from which the IDENTIKEY Appliance SNMP server can be consulted. You can specify an IP address or range of IP addresses; netmask is required.
Check to enable the Simple Network Management Protocol (SNMP) v3. This allows you to use an
SNMP client to manage and monitor the IDENTIKEY Appliance. SNMP v3 is defined per RFC
3411–RFC 3418 (also known as 'STD0062'). SNMP v3 primarily added security and remote configuration enhancements to SNMP, such as authentication and message integrity.
With this option enabled, the following options will also need to be configured in order to enable connection to the IDENTIKEY Appliance SNMP server: n n n n n
Authentication user name (ie. Security Name)
Authentication password
Authentication type ( MD5 or SHA )
Privacy password – secret key used by privacy protocol for encrypting/decrypting messages
Privacy type – indicates which privacy protocol to use ( AES or DES )
Settings
Contact
Location
Download VASCO MIB files
The contact information of the IDENTIKEY Appliance administrator
The location of the IDENTIKEY Appliance
The Download link beside this downloads the MIB files provided by VASCO for use with SNMP.
For more information about MIB files, refer to Section
SNMP Traps
IDENTIKEY Appliance 3.11.12 - Administrator Reference
16
2. Configuration Tool: Field Listings
Table 5: SNMP Fields (continued)
Field Name Description
Enable v2 Traps
Enable v3 Traps
Enable SNMP v3 Inform
Requests
Enable SNMP v2 traps. With this option enabled, you will also need to configure a Community (ie. Security Name).
These options enable SNMP traps for Operating System Events. When enabling a trap, you will also need to configure a Target Host
(ie. The IP address of the SNMP host).
Enable SNMP v3 traps.
Enable SNMP v3 inform. With this trap, you will need to configure options identical to those for “Enable v3 traps”.
When enabling v3 traps or v3 inform, the following options will also need to be configured: n n n n n n
Authentication user name (ie.
Security name)
Authentication password
Authentication type ( None , MD5 , or
SHA )
Privacy password – secret key used by privacy protocol for encrypting/decrypting messages
Privacy type – indicates which privacy protocol to use ( None , AES , or
DES )
EngineID text – SNMP v3 requires an SNMP agent to define a unique
“engine ID” in order to respond to
SNMP v3 requests. The text in this field will be appended to the
IDENTIKEY Appliance engine ID in hex (e.g.
0x80001f8804TEXTINHEX).
2.2.5. Logging Settings
This interface allows you to specify level settings for system logging. It contains sections for both local and remote logging. With remote logging, log lines are forwarded to a remote syslog server. To enable this, you need to specify one or more syslog server(s).
The IDENTIKEY Appliance Configuration Tool generates information in the logging system. This logging system does not contain information from the IDENTIKEY Authentication Server component. For more information about the IDENTIKEY Appliance logging system, refer to the IDENTIKEY Appliance Product Guide , Section "Logging".
IDENTIKEY Appliance 3.11.12 - Administrator Reference
17
2. Configuration Tool: Field Listings
Table 6: Logging Fields
Field Name
Level
Description
Select the logging level.
The logging system can be configured to generate information at different priority levels.
When specifying a level, IDENTIKEY Appliance will log all messages at that priority level and higher; for example, when Error is the specified logging level, IDENTIKEY Appliance will log all
Error and Critical messages.
The following levels are available (in order of descending priority): n n n n n n
Critical: A system-critical warning that services may not be running.
Error: Action is required, although services may still be running.
Warning: Not an error, but an indication that an error may occur if action is not taken.
Notice: Events which are unusual but not error conditions. No immediate action required.
Info: Normal operational messages, may be collected for reporting etc. No action required.
Debug: Information useful to debug the application. Not useful during operations.
Remote Logging
Syslog Servers
Level
The IP address of the remote syslog server.
Select the level for remote logging.
2.2.6. Notifications
These settings allow you to define SNMP traps, SMS or email warnings for IDENTIKEY Appliance Configuration Tool events.
Table 7: Notification Settings Fields
Field Name Description
Enabled
Filters
If selected, notifications are enabled.
List of notification filters.Notification filters restrict the audit messages that are monitored.
Targets
Click Add filter to add a new filter (see Section
List of notification targets. Notification targets define where and how notifications are sent.
Click Add target to add a new target (see Section
).
IDENTIKEY Appliance 3.11.12 - Administrator Reference
18
2. Configuration Tool: Field Listings
2.2.6.1. Add Filter
Table 8: Notification Filter Fields
Field Name Description
Enabled
Name
Target
Filter
If selected, the filter is enabled.
The filter name used to distinguish between different filters.
A target as specified in the Targets section (see Section
Optional. List of audit filters. Filters restrict the audit messages that are monitored. A filter defines a match criteria that must be met in order to trigger a notification.
Severity
Click Add to define a new audit filter.
You can configure a notification to be sent to multiple recipients/channels by adding multiple targets to a single filter.
The severity settings allow you to select conditions to monitor. You can choose multiple condition types: n n n n n
Error
Success
Warning
Failure
Info
2.2.6.2. Add Target
Table 9: Notification Target Fields
Field Name Description
Type Notification target type.
n n n
SNMP
SMS
The target name used to distinguish between different notification targets.
Name
SNMP
Host
Type
The IP address of the SNMP host to which SNMP traps will be sent.
SNMP notification type.
User Name n n n
INFORM . This type expects an acknowledgement and will resend the message until it gets a response.
TRAP . This is an SNMP v3 trap. For this notification target, an engine ID field is displayed (read-only) which is required to configure the server.
TRAPv2c . This is an SNMPv2c trap.
The user name for SNMP v3.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
19
2. Configuration Tool: Field Listings
Table 9: Notification Target Fields (continued)
Field Name Description
Authentication Type Required, if SNMP Type is set to INFORM or TRAP . Specifies whether messages sent and received on behaof of this user can be authenticated, and if so, which authentication protocol to use.
Authentication Secret
Privacy Type
Privacy Secret n n
MD5
SHA
Required, if SNMP Type is set to INFORM or TRAP . Passphrase used to create the authentication key.
Available, if SNMP Type is set to INFORM or TRAP . Specifies whether messages sent and received on behalf this user can be encrypted, and if so, which encryption protocol to use.
n n n
AES
DES
None
Available, if SNMP Type is set to INFORM or TRAP . Passphrase used to create the encryption key.
Required, if SNMP Type is set to TRAPv2c .
Communitystring
From
Subject
To
SMS
Mobile
The sender's email address.
The message subject header field.
The recipient's email address.
The phone number to send the message to.
For more information about notification targets in general, refer to the IDENTIKEY Appliance Administrator Guide ; for more information on SNMP traps as notification targets and trap parameters, refer to Section
.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
20
2. Configuration Tool: Field Listings
2.2.7. Configtool Settings
Table 10: Configtool Fields
Field Name
Limit Access To Networks
Description
List of IP addresses of client computers that are allowed to access the Configuration Tool. The
Classless Inter-Domain Routing (CIDR) notation can be used to specify IP address blocks, e.g.
192.168.0.100/24. If this list is empty, any client computer can access the IDENTIKEY Appliance Configuration Tool.
Default setting: -
Note
If you inadvertently lock yourself out by setting this option to an incorrect value, you can reset it using the Rescue Tool.
Maximum Configtool Session
Length (minutes)
Configtool HTTPS Certificate
The time span a Configuration Tool session remains active before IDENTIKEY Appliance terminates it automatically. The value is given in minutes.
Default setting: 45
The certificate used to encrypt connections to the Configuration Tool. The list contains all valid certificates created/imported using the Certificate Management tab (see
A default certificate for the Configuration Tool is created automatically during setup. A new default certificate is automatically created whenever you change the hostname.
2.2.8. Certificate Management
This tab is used to manage all server and certification authority (CA) certificates used by all components of
IDENTIKEY Authentication Server and IDENTIKEY Appliance, respectively.
Table 11: Certificates Fields
Field Name Description
Server Certificates
Server certificates contain public and private keys and are usually used to secure connections to a server or a component using SSL, e.g.
SEAL communicator, SOAP communicator, Configuration Tool, etc.
Some server certificates are created by the built-in certification authority (CA) during installation.
Subject The entity associated with the public key stored in the certificate.
Description An optional description of the server certificate. Can be changed.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
21
2. Configuration Tool: Field Listings
Table 11: Certificates Fields (continued)
Field Name Description
Issued By
Expiry
In Use
Expiry
In Use
IDENTIKEY Appliance Root CA
The authority, which issued this certificate.
Shows how long the certificate is still valid. The value is given in days.
Shows how many components are currently using this server certificate.
Trusted Root Certificate Authorities
Trusted certification authority (CA) certificates are typically used to determine which client certificates to trust. Trusted CA certificates often come in bundles containing several different trusted root CA's.
Description
Content
An optional description of the trusted root CA certificate/bundle. Can be changed.
The entity associated with the public key stored in the certificate, or, if the item is a CA certificate bundle, the number of CAs in the bundle.
Shows how long the CA certificate/bundle is still valid. The value is given in days.
Shows how many components are currently using this CA certificate/bundle.
IDENTIKEY Appliance contains a built-in certification authority (CA) used to sign all automatically generated default certificates. This list contains the root CA certificate for the IDENTIKEY Appliance CA.
Description A description of the root CA certificate.
Content
Expiry
The entity associated with the public key stored in the certificate.
Shows how long the CA certificate is still valid. The value is given in days.
For more information about managing your certificates, refer to the IDENTIKEY Appliance Administrator Guide , Section "Managing Certificates".
2.3. IDENTIKEY Authentication Server Settings
2.3.1. Scenarios
Table 12: IDENTIKEY Authentication Server General Settings Fields
Field Name Description
Administration
Max. Concurrent Sessions
The maximum number of concurrent administration sessions permitted. If this is set to 0, concurrent sessions will be unlimited.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
22
2. Configuration Tool: Field Listings
Table 12: IDENTIKEY Authentication Server General Settings Fields (continued)
Field Name Description
Max. Session Time
(seconds)
Idle Timeout (seconds)
The maximum allowed length of an administration session. There is no way to extend a session beyond this limit.
The maximum length of time of inactivity allowed during a session, before the session is automatically terminated by the IDENTIKEY Authentication Server.
Authentication
Enabled Enable or disable processing of authentication requests. The IDENTIKEY Authentication Server license key must enable authentication for this setting to be applicable.
Provisioning
Enabled
Max. Reactivation
Attempts
Enable or disable processing provisioning requests. Note that the IDENTIKEY Authentication Server license key must enable provisioning for it to be enabled.
Min. Reactivation Interval The minimum length of time in minutes between activation attempts for a particular DIGIPASS.
Default value: 1440
The total number of activation attempts (successful or unsuccessful) per DIGIPASS.
Default value: 3
Max. Reactivation Locations
The maximum number of different locations at which a particular DIGIPASS can be activated.
This only applies where the location is specified as part of provisioning (DIGIPASS for Web).
Default value: 5
Online Provisioning Registration Identifier
Length
Character Set
The minimum length of the registration identifier for online provisioning for DIGIPASS for Mobile.
Default value: 8
The character set used for the registration identifier.
Possible values: n n
Alphanumeric
Numeric
Default value: Alphanumeric
IDENTIKEY Appliance 3.11.12 - Administrator Reference
23
2. Configuration Tool: Field Listings
Table 12: IDENTIKEY Authentication Server General Settings Fields (continued)
Field Name Description
Case
Online Provisioning Activation Password
Length The minimum lengths of the activation password for online provisioning for DIGIPASS for Mobile.
Default value: 8
Character Set
The letter case used for the character set for the registration identifier.
Possible values: n n n
Upper Case
Lower Case
Mixed Case
Default value: Mixed Case
Case
The character set used for the activation password.
Possible values: n n
Alphanumeric
Numeric
Default value: Alphanumeric
The letter case used for the character set for the activation password.
Possible values: n n n
Upper Case
Lower Case
Mixed Case
Default value: Mixed Case
Signature
Enabled Enable or disable the Signature scenario. Note that the IDENTIKEY Authentication Server license key must enable Signature for it to be enabled.
EMV-CAP
Enabled Enable or disable the EMV-CAP Hardware Security Module scenario.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
24
2. Configuration Tool: Field Listings
2.3.2. SEAL Configuration
Table 13: IDENTIKEY Authentication Server SEAL Configuration Fields
Field Name Description
SSL Cipher Suite Security Level
SSL Cipher Suite Security
Level
For more information, refer to Chapter
.
n n n
High Uses key lengths larger than 128 bits.
Medium Uses key equal to 128 bits.
Low Uses 64 or 56 bit encryption algorithms, excluding export cipher suites.
SEAL Certificate
Server Certificate The certificate used to encrypt connections using the SEAL protocol. The list contains all valid certificates created/imported using the Certificate Management tab (see
A default certificate for SEAL connections is created automatically during setup.
SEAL Client Certificate Verification
Require Client Certificate
CA Certificate Store
Re-verify On Re-Negotiation
Automatically Trust Certificates
Indicates whether the client certificate is required to during SSL processing.
The valid values are: n n n n
Never
Optional
Required
Required - Signed Address Only
For more information, refer to the IDENTIKEY Appliance Product Guide , Section "SSL".
The CA certificate used to authenticate the clients. The list contains all valid and trusted CA certificates imported using the Certificate Management tab (see
2.2.8. Certificate Management ).
If you select the default certificate for SEAL connections to use as Server Certificate , CA Certificate
Store will be the certificate of the IDENTIKEY Appliance root CA.
If enabled, the client certificate is re-verified.
For more information, refer to the IDENTIKEY Appliance Product Guide , Section "SSL".
Check to automatically trust certificates.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
25
2. Configuration Tool: Field Listings
2.3.3. SOAP Configuration
Table 14: IDENTIKEY Authentication Server SOAP Configuration Fields
Field Name Description
SSL CipherSuite Security Level
SSL Cipher Suite Security
Level
For more information, refer to Chapter
.
n n n
High Uses key lengths larger than 128 bits.
Medium Uses key equal to 128 bits.
Low Uses 64 or 56 bit encryption algorithms, excluding export cipher suites.
SOAP Certificate
Server Certificate The certificate used to encrypt connections using the SOAP protocol. The list contains all valid certificates created/imported using the Certificate Management tab (see
A default certificate for SOAP connections is created automatically during setup.
SOAP Client Certificate Verification
Require Client Certificate
CA Certificate Store
Re-verify On Re-Negotiation
Require Client Certificate indicates whether the client certificate is required to during SSL processing.
The valid values are: n n
Never
Required
For more information, refer to the IDENTIKEY Appliance Product Guide , Section "SSL".
The CA certificate used to authenticate the clients. The list contains all valid and trusted CA certificates imported using the Certificate Management tab (see
2.2.8. Certificate Management ).
If you select the default certificate for SOAP connections to use as Server Certificate , CA Certificate
Store will be the certificate of the IDENTIKEY Appliance root CA.
If enabled, the client certificate is re-verified.
For more information, refer to the IDENTIKEY Appliance Product Guide , Section "SSL".
IDENTIKEY Appliance 3.11.12 - Administrator Reference
26
2. Configuration Tool: Field Listings
2.3.4. RADIUS Configuration
Table 15: IDENTIKEY Authentication Server RADIUS Configuration Fields
Field Name Description
Click to enable/disable RADIUS communicator Enable RADIUS Communication
Authentication Port
Accounting Port
Server Certificate
SSL Security Level
The port number on which to listen for RADIUS access requests .
The port number on which to listen for RADIUS accounting requests .
Server Certificate
For more information, refer to Chapter
.
n n n n
Very High .
High . Uses key lengths larger than 128 bits.
Medium . Uses key equal to 128 bits.
Low . Uses 64 or 56 bit encryption algorithms, excluding export cipher suites.
The certificate used to encrypt connections using the RADIUS protocol. The list contains all valid certificates created/imported using the Certificate Management tab (see
2.2.8. Certificate Management ).
A default certificate for RADIUS connections is created automatically during setup.
RADIUS Dictionary File
Default Dictionary
Upload New Dictionary
Click the icon to download the default dictionary of RADIUS attributes.
Each dictionary file contains a list of RADIUS attributes and values, which the server uses to map between descriptive names and on-the-wire data. The names have no meaning outside of the RADIUS server itself, and are never exchanged between server and clients.
Use this function to upload your own set of RADIUS attributes. Once you have uploaded your own RADIUS attribute file, it will be marked as “current” (in use) and will be available for download.
For more information, refer to Chapter
.
2.3.5. Authentication Back-End Settings
Table 16: IDENTIKEY Authentication Server Back-End Settings Fields
Field Name Description
IBM Security Directory Server
Enabled Check this option to activate the IBM Security Directory Server LDAP back-end server type for the
IDENTIKEY Authentication Server.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
27
2. Configuration Tool: Field Listings
Table 16: IDENTIKEY Authentication Server Back-End Settings Fields (continued)
Field Name Description
IBM Directory
SSL Certificate
The certificate used to authenticate the IDENTIKEY Authentication Server to the IBM Security Directory
Server back-end server. The list contains all valid certificates created/imported using the Certificate
Management tab (see
2.2.8. Certificate Management ).
Microsoft Active Directory
Enabled
AD SSL Certificate
Enable this check box to activate the Microsoft Active Directory back-end server type for the
IDENTIKEY Authentication Server.
The certificate used to authenticate the IDENTIKEY Authentication Server to the Active Directory (AD) back-end server. The list contains all valid certificates created/imported using the Certificate Management tab (see
).
NetIQ eDirectory
Enabled Enable this check box to activate the NetIQ eDirectory back-end server type for the IDENTIKEY
Authentication Server. For more information about NetIQ eDirectory back-end servers, refer to
IDENTIKEY ApplianceProduct Guide .
RADIUS
Enabled Enable this check box to activate the RADIUS back-end server type for the IDENTIKEY Authentication
Server. For more information about RADIUS back-end servers, refer to IDENTIKEY ApplianceProduct
Guide .
2.3.6. Server Discovery
Table 17: IDENTIKEY Authentication Server Discovery Fields
Field Name Description
Enabled
DNS Server Address
Authentication Type
Shared Key File
DNS Domain
Enable this check box to activate server discovery for the IDENTIKEY Authentication Server. For no DNS service registration, the check box should not be enabled.
Enter the IP address of the DNS server.
None Use this for DNS service registration with a DNS server supporting dynamic DNS anonymously.
TSIG Use this for DNS service registration with a DNS server supporting dynamic DNS with TSIG authentication.
Browse to the TSIG key file, if TSIG authentication type is being used (see previous field).
Enter the domain name.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
28
2. Configuration Tool: Field Listings
Table 17: IDENTIKEY Authentication Server Discovery Fields (continued)
Field Name Description
Host Name
Priority
The FQDN of the machine hosting the IDENTIKEY Authentication Server. You may also enter an IP address in this field.
Primary This IDENTIKEY Authentication Server will be the first to which authentication requests are sent during Windows Logon, where more than one IDENTIKEY Authentication Server exists on the network.
Backup This IDENTIKEY Authentication Server will be the backup to which authentication requests are sent during Windows Logon, where more than one IDENTIKEY Authentication Server exists on the network, but the IDENTIKEY Authentication Server nominated as 'Primary'
(see above) is unavailable.
2.3.7. Audit Settings
Table 18: IDENTIKEY Authentication Server Audit Fields
Field Name Description
Send Audit Messages To Syslog
Syslog Message Type Select one or more of these options, to enable logging the respective types of audit messages. Available types are: n n n n n
Error
Warning
Info
Success
Failure
For more information, refer to Chapter
Remote Audit Viewer
Enable Remote Audit
Viewer
Maximum Connections
Authentication Timeout
If the option is enabled, you can use the IDENTIKEY Authentication Server Audit Viewer (client application).
The maximum number of Audit Viewer clients that can be connected to IDENTIKEY Authentication
Server at the same time. A high number of connections could impact performance. The default maximum number of connections is 3 .
Number of seconds until an authentication times out in case of inactivity. The default value is 60 seconds.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
29
2. Configuration Tool: Field Listings
Table 18: IDENTIKEY Authentication Server Audit Fields (continued)
Field Name Description
Audit message type Select one ore more of these options, to enable the respective types of audit messages. Available types are: n n n n n
Error
Warning
Info
Success
Failure
For more information, refer to Chapter
Audit Viewer SSL
Enable SSL Connections If you wish to secure the audit connection with SSL, select this check box.
SSL Cipher Suite Security Level
IDENTIKEY Appliance supports SSL Cipher Suites at Very High, High, Medium, and Low levels for
SSL cipher suites. For more information, refer to the IDENTIKEY Appliance Administrator Guide .
Server Certificate
Certificate Password
The certificate used to encrypt audit connections via SSL. The list contains all valid certificates created/imported using the Certificate Management tab (see
2.2.8. Certificate Management ).
A default certificate for SEAL connections is created automatically during setup.
The password for the certificate file.
Client Certificate Verification
Require Client Certificate You can set if selecting a Certificate Authority (CA) certificate file is required; if you do not require an
SSL client certificate, select Never from this drop-down list; if you select any other setting than Never , you will be required to select a CA certificate.
CA Certificate Store
Re-Verify On Re-Negotiation
The CA certificate used to authenticate the clients. The list contains all valid and trusted CA certificates imported using the Certificate Management tab (see
2.2.8. Certificate Management ).
If you select the default certificate for SEAL connections to use as Server Certificate , CA Certificate
Store will be the certificate of the IDENTIKEY Appliance root CA.
If you select this option, an SSL handshake is performed each time the audit viewer is re-connected to
IDENTIKEY Authentication Server, i.e. the connection is forced to be re-verified each time a connection is established.
Note that enabling the Re-Verify on Re-Negotiation option may incur a performance penalty; therefore this option should be enabled only if absolutely necessary.
Automatically Trust Certificates
When this option is enabled, your server will copy the certificate authority details from the destination server to an empty file that needs to be specified in the CA Certificate Store field. This option guarantees certificate verification by copying the necessary certificate details (during each connection).
IDENTIKEY Appliance 3.11.12 - Administrator Reference
30
2. Configuration Tool: Field Listings
2.3.8. Tracing Settings
Table 19: IDENTIKEY Authentication Server Tracing Fields
Field Name Description
Trace Level n n n n
None No tracing / disable tracing
Basic Show all logging information, except debugging information
Full Shows all logging information, debugging information included. This level is advised for troubleshooting.
Debug Shows all logging information, with more debugging information included. This setting is only for use when advised to do so by VASCO Customer Service.
Trace File Rotation
Number of Archived Logs The number of log files to be archived. Older logs are removed, and IDENTIKEY Appliance can keep a maximum of 10 logs; as such, the maximum accepted value for this field is also 10.
Rotate On Select whether logs should be rotated based on: n n
Days The number of days they exist.
Size The size in MB of the log file
2.3.9. Performance Monitoring
Table 20: IDENTIKEY Authentication Server Performance Monitoring Fields
Field Name Description
Enabled
CSV Plugin
Enable CSV Plugin
Enable Log Rotation
Enables/disables the performance monitoring system
Enable the CSV Plugin by clicking the Enable CSV Plugin field.
CSV log files can be rotated, with a new file being created after a specified elapsed time period, or when a specified size is reached. Check this box to enable CSV log file rotation.
Number of Archived Logs Specify the number of CSV log files to keep. The number of archived CSV log files will remain constant, but a new file will be added to the archive list, and the oldest file will be lost.
Rotate On Select the criteria to decide when to rotate the log file.
Size
Days
Compression n n
Size . Rotate when the log file exceeds a specified size limit.
Days . Rotate after a specified amount of time.
The file size limit for log file rotation. This value is given in KB.
Default setting: 10240
The time limit for log file rotation.
Default setting: 1
Check this to compress the kept CSV log files.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
31
2. Configuration Tool: Field Listings
Table 20: IDENTIKEY Authentication Server Performance Monitoring Fields (continued)
Field Name Description
Counter Plugin
Enabled Enable the Counter Plugin by clicking the Enable Counter Plugin field. The Counter Plugin will generate data relating to the number of times certain transactions have been performed, adding this data into the SNMP server. The Counter Plugin is only available if SNMP is enabled, and can only be viewed via SNMP.
Filters
Add Filter Filters allow the Performance Monitoring tool to restrict the amount of information that it monitors.
At least one filter must be provided.
The filter must consist of the name of a performance transaction.
The filter can contain the exact name of the performance transaction, or wildcards can be used to identify a group of transactions.
For more information about performance monitoring filters, refer to Chapter
.
2.3.10. System Monitoring Alerts
These settings allow you to define SNMP traps, SMS and email warnings for IDENTIKEY Authentication Server events. For more details about system monitoring, refer to Chapter
.
Table 21: System Monitoring Settings Fields
Field Name Description
Enabled
Targets
If selected, notifications are enabled.
List of notification targets. Notification targets define where and how notifications are sent.
Filters
Click Add target to add a new target (see Section
List of notification filters.Notification filters restrict the audit messages that are monitored.
Click Add filter to add a new filter (see Section
).
2.3.10.1. Add Target
Table 22: System Monitoring Target Fields
Field Name Description
Type Notification target type.
n n n
SNMP
SMS
IDENTIKEY Appliance 3.11.12 - Administrator Reference
32
2. Configuration Tool: Field Listings
Table 22: System Monitoring Target Fields (continued)
Field Name Description
The target name used to distinguish between different notification targets.
Name
SNMP
Host
Type
Security Name
Authentication Type
Authentication Secret
Privacy Type
Privacy Secret
The IP address of the SNMP host to which SNMP traps will be sent.
SNMP notification type.
n n n
INFORM . This type expects an acknowledgment and will resend the message until it gets a response.
TRAP .This is an SNMP v3 trap. For this notification target, an engine ID field is displayed (read-only) which is required to configure the server.
TRAPv2c . This is an SNMPv2c trap.
The user name for SNMP v3 or the community name for SNMPv2c.
Required, if SNMP Type is set to INFORM or TRAP . Specifies whether messages sent and received on behalf of this user can be authenticated, and if so, which authentication protocol to use.
n n
MD5
SHA
Required, if SNMP Type is set to INFORM or TRAP . Pass phrase used to create the authentication key.
Available, if SNMP Type is set to INFORM or TRAP . Specifies whether messages sent and received on behalf this user can be encrypted, and if so, which encryption protocol to use.
n n n
AES
DES
None
Available, if SNMP Type is set to INFORM or TRAP . Pass phrase used to create the encryption key.
Required, if SNMP Type is set to TRAPv2c .
Communitystring
From
Subject
To
SMS
Mobile
The sender's email address.
The message subject header field.
The recipient's email address.
The phone number to send the message to.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
33
2. Configuration Tool: Field Listings
2.3.10.2. Add Filter
Table 23: System Monitoring Filter Fields
Field Name Description
Enabled
Name
Target
Filter
If selected, the filter is enabled.
The filter name used to distinguish between different filters.
List of notification targets as specified in the Targets section (see Section
Optional. List of audit filters. Filters restrict the audit messages that are monitored. A filter defines a match criteria that must be met in order to trigger a notification.
Severity
Click Add to define a new audit filter.
You can configure a notification to be sent to multiple recipients/channels by adding multiple targets to a single filter.
The severity settings allow you to select conditions to monitor. You can choose multiple condition types: n n n n n
Error
Success
Warning
Failure
Info
2.3.11. Message Delivery Component
The Message Delivery Component (MDC) is used sending notifications and a one-time password (OTP) by SMS, email, or voice message when Virtual DIGIPASS is used.
For more information about setting up Virtual DIGIPASS, refer to the IDENTIKEY Appliance Administrator Guide .
Table 24: Message Delivery Component Fields
Field Name Description
Enable this check box to activate the Message Delivery Component.
Enabled
Tracing
Trace Level
Enable Log Rotation
Number of Archived Logs n n n
None No tracing / disable tracing
Basic Show all logging information, except debugging information
Full Shows all logging information, debugging information included. This level is advised for troubleshooting.
Check this option to enable log rotation. Log rotation specifies when new logs files are created, based on the number of days they exist (their age) or the log file size.
The number of log files to be archived. The oldest log file is removed.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
34
2. Configuration Tool: Field Listings
Table 24: Message Delivery Component Fields (continued)
Field Name Description
Rotate On Select whether logs should be rotated based on: n n
Days The number of days they exist.
Size The size in MB of the log file
Check this option to compress the archived logs to save disk space.
Compress Archived Logs
SMS Delivery
Gateways List of SMS gateways.
Click Add SMS Server to define a new HTTP/HTTPS SMS gateway. For more information, refer to
Section
Click Add SMPP Server to define a new SMPP gateway. For more information, refer to Section
.
E-Mail Delivery
Gateways List of email gateways.
Click Add SMTP Server to define a new SMTP gateway. For more information, refer to Section
.
Voice Delivery
Gateways List of voice gateways.
Click Add Voice Server to define a new voice gateway. For more information, refer to Section
.
2.3.11.1. Importing and Exporting Gateways
For each gateway option, an Import gateway and Export gateway button is available. These functions allow you to import and export a description file and easily apply gateway settings from different IDENTIKEY Appliance instances or to import gateway settings from IDENTIKEY Authentication Server into IDENTIKEY Appliance (and vice versa).
2.3.11.2. Add SMS Server
Table 25: SMS Server Fields
Field Name Description
Enabled
Profile
If selected, this gateway is enabled.
Name of the MDC profile; should not be confused with the profile's display name. The MDC profile name is nonunique and thus multiple MDC profiles with the same name may exist for this delivery method. The highestranked, enabled, and available MDC profile with the specified profile name will be used.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
35
2. Configuration Tool: Field Listings
Table 25: SMS Server Fields (continued)
Field Name Description
Name
Server Type
Display name of the MDC profile; ad-hoc field used primarily to describe and further identify the profile.
Specifies how the MDC performs load-balancing, failover, and/or fail-back.
n n
Primary
Backup
Connection Settings
URL The complete URL of the HTTP/HTTPS gateway, including the protocol, URI, and port.
<Protocol>://<Host>[:<Port>][/<Path>]
If the port is omitted, then standard values are assumed depending on the specified protocol, i.e. port 80 for
HTTP and port 443 for HTTPS..
Example http://myHost/myPath https://myHost:443/
Certificate The CA certificate used to verify encrypted connections to the gateway. Required, if the gateway uses HTTPS.
The list contains all valid and trusted CA certificates imported using the Certificate Management tab (see
If the list does not contain the correct certification authority (CA), you can select Add Authority from the list to upload a certificate file using the Upload Certificate wizard.
SMS Gateway Account Settings
User Name
Password
The user name needed to authenticate with the gateway
The password needed to authenticate with the gateway
Query & Result
IDENTIKEY Appliance 3.11.12 - Administrator Reference
36
2. Configuration Tool: Field Listings
Table 25: SMS Server Fields (continued)
Field Name Description
Query String This field defines the query string which is submitted to the HTTP server, either using POST or GET (as specified by the query method). This string must contain all the required variables that are expected by the HTTP gateway.
Example
<Query type=”string” data=”UN=[User name]&PW=[password]&TY=T&NB=[destination]&ME=[message]&FL=F&ON=FromVM&TM=Y”/>
Form Method
The following parameters can be included in the query string and are set by the MDC before submitting the query:
[acc_user] specifies the account name for the gateway used to submit the information
[acc_pwd]
[otp_msg] sets the password for the gateway account specified by the [Username] parameters specifies the part of the query string, where the OTP is substituted
[otp_dest] specifies the part of the query string, where the destination for the OTP (usually the mobile phone number) is substituted. The query string should also incorporate any other parameters which might be expected by the gateway.
This field designates either the GET or POST method for transferring account and message data to the
HTTP/HTTPS gateway.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
37
2. Configuration Tool: Field Listings
Table 25: SMS Server Fields (continued)
Field Name Description
Result Matching Rules
List of result matching rules. A result page is returned by the gateway service when a text message is submitted by the GET or POST methods. This page would normally be a HTML formatted page containing specific error codes and/or additional messages for success/failure.
Click Add Result to define a new result matching rule.
Message Delivery Component Result
Name
Messagetype
Matching Pattern
Audit Text
Test SMS
Send Test Message To
Phone number to send a message to test the configuration settings.
Click Test Settings to effectively send a test message.
Description used to distinguish between different result matching rules.
The category of the result message.
n n n
Information . Message has been delivered successfully.
Warning . The submission or delivery failed, but it is most likely a specific error only affecting this user.
Error . An error occurred while attempting delivery.
This field specifies the result page template to match the result page returned by the
HTTP service. If this template is matched, the corresponding audit message is composed and returned to the IDENTIKEY Appliance audit message.
This field specifies the audit message template for the message to be compiled and sent back to the IDENTIKEY Appliance.
Variables may be included in this field.
2.3.11.3. Add SMPP Server
Table 26: SMPP Server Fields
Field Name
Enabled
Description
If selected, this gateway is enabled.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
38
2. Configuration Tool: Field Listings
Table 26: SMPP Server Fields (continued)
Field Name
Profile
Name
Server Type
Connection Settings
IP Address
Port
Certificate
SSL Enabled
Certificate
SMS Gateway Account Settings
User Name
Password
SMPP System Settings
System Type
Description
Name of the MDC profile; should not be confused with the profile's display name. The MDC profile name is non-unique and thus multiple MDC profiles with the same name may exist for this delivery method. The highest-ranked, enabled, and available MDC profile with the specified profile name will be used.
Display name of the MDC profile; ad-hoc field used primarily to describe and further identify the profile.
Specifies how the MDC performs load-balancing, failover, and/or fail-back.
n n
Primary
Backup
The IP address of the SMPP server.
The server port used by the SMPP server.
Default setting: 2775
If selected, the SMPP server used encryption.
The CA certificate used to verify encrypted connections to the gateway. The list contains all valid and trusted CA certificates imported using the Certificate Management tab (see
2.2.8. Certificate Management ).
If the list does not contain the correct certification authority (CA), you can select Add Authority from the list to upload a certificate file using the Upload Certificate wizard.
The user name required to authenticate with the SMPP server
The password required to authenticate with the SMPP server
Name to identify the gateway.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
39
2. Configuration Tool: Field Listings
Table 26: SMPP Server Fields (continued)
Field Name
Message Mode
Priority Flag
Privacy Indicator
SMPP Source Address
Type of Number (TON)
Numbering Plan Indicator (NPI)
Number
SMPP Destination Address
Type of Number (TON)
Numbering Plan Indicator (NPI)
SMPP Timeout Settings
Description
Specifies how Message Delivery Component handles messages sent to the gateway.
n n
Datagram . When sending a message Message Delivery
Component expects a confirmation on whether the gateway received the message.
Transaction . When sending a message Message Delivery Component expects a confirmation on whether the gateway AND the intended recipient received the message.
The priority level of messages sent by Message Delivery Component. A higher number indicates a higher priority.
The privacy level of sent messages.
n n n n n
None
Not Restricted
Restricted
Confidential
Secret
The Type of Number (TON) of the addresses used for outgoing messages send by the gateway.
n n n n n n n
Unknown
International
National
Network Specific
Subscriber Number
Alphanumeric
Abbreviated
The Numbering Plan Indicator (NPI) as specified in the SMPP specification.
The phone number used as the sender's.
The Type of Number (TON) of the addresses of incoming messages served by the gateway.
The Numbering Plan Indicator (NPI) as specified in the SMPP specification.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
40
2. Configuration Tool: Field Listings
Table 26: SMPP Server Fields (continued)
Field Name
Transaction Timeout (sec)
Inactivity Timeout (sec)
Enquire Link Timeout (sec)
Test SMS
Send Test Message To
2.3.11.4. Add SMTP Server
Table 27: SMTP Server Fields
Field Name
Enabled
Profile
Description
The time span Message Delivery Component waits to receive a reply for a transaction request until the transaction fails. The value is given in seconds.
Default setting: 10
The time span a session remains active before Message Delivery
Component terminates it automatically. The value is given in seconds.
Default setting: 300
The time span between operations before Message Delivery Component sends an enquire_link request to the gateway to test whether the gateway has still an active session. The value is given in seconds.
Default setting: 10
Phone number to send a message to test the configuration settings.
Click Test Settings to effectively send a test message.
Name
Server Type
SMTP Host
SMTP Host
Description
If selected, this gateway is enabled.
Name of the MDC profile; should not be confused with the profile's display name.
The MDC profile name is non-unique and thus multiple MDC profiles with the same name may exist for this delivery method. The highest-ranked, enabled, and available MDC profile with the specified profile name will be used.
Display name of the MDC profile; ad-hoc field used primarily to describe and further identify the profile.
Specifies how the MDC performs load-balancing, failover, and/or fail-back.
n n
Primary
Backup
Enter the FQDN or IP address of the SMTP server used for audits and reporting.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
41
2. Configuration Tool: Field Listings
Table 27: SMTP Server Fields (continued)
Field Name Description
SMTP Port
Connection Security
Certificate
Enter the port number of the SMTP server (25 is the default)
Select the applicable encryption used on the SMTP server.
n n n
No SSL/TLS . No encryption is used (default setting)
SSL . The SMTP server uses SSL to encrypt mail traffic. A certificate file needs to be uploaded.
TSL . The SMTP server uses TLS to encrypt mail traffic. A certificate needs to be uploaded.
The CA certificate used to verify encrypted connections to the gateway. Required, if the gateway uses HTTPS. The list contains all valid and trusted CA certificates imported using the Certificate Management tab (see
2.2.8. Certificate Management ).
If the list does not contain the correct certification authority (CA), you can select Add
Authority from the list to upload a certificate file using the Upload Certificate wizard.
Authentication
Enable SMTP Authentication Allow the IDENTIKEY Appliance to log in to the SMTP automatically.
Username
Password
SMTP Options
From Address
The user name required to authenticate with the SMTP server
The password required to authenticate with the SMTP server
The email address which should appear in the From field when a notification is sent.
Test E-mail
Send Test Message To The email address to send a message to test the configuration settings.
Click Test Settings to effectively send a test message
2.3.11.5. Add Voice Server
Table 28: Voice Server Fields
Field Name Description
Enabled
Profile
Name
If selected, this gateway is enabled.
Name of the MDC profile; should not be confused with the profile's display name. The MDC profile name is nonunique and thus multiple MDC profiles with the same name may exist for this delivery method. The highestranked, enabled, and available MDC profile with the specified profile name will be used.
Display name of the MDC profile; ad-hoc field used primarily to describe and further identify the profile.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
42
2. Configuration Tool: Field Listings
Table 28: Voice Server Fields (continued)
Field Name Description
Server Type Specifies how the MDC performs load-balancing, failover, and/or fail-back.
n n
Primary
Backup
Connection Settings
URL The complete URL of the voice gateway, including the protocol, URI, and port.
<Protocol>://<Host>[:<Port>][/<Path>]
If the port is omitted, then standard values are assumed depending on the specified protocol, i.e. port 80 for
HTTP and port 443 for HTTPS.
Example http://myHost/myPath https://myHost:443/
Certificate The CA certificate used to verify encrypted connections to the gateway. Required, if the gateway uses HTTPS.
The list contains all valid and trusted CA certificates imported using the Certificate Management tab (see
If the list does not contain the correct certification authority (CA), you can select Add Authority from the list to upload a certificate file using the Upload Certificate wizard.
Voice Gateway Account Settings
User Name
Password
The user name needed to authenticate with the gateway
The password needed to authenticate with the gateway
Voice Settings
Phone Number
Prefix
Query & Result
A prefix that is automatically added to the beginning of the user's phone number when sending a voice message.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
43
2. Configuration Tool: Field Listings
Table 28: Voice Server Fields (continued)
Field Name Description
Query String This field defines the query string which is submitted to the HTTP server, either using POST or GET (as specified by the query method). This string must contain all the required variables that are expected by the HTTP gateway.
Example
<Query type=”string” data=”UN=[Username]&PW=[password]&TY=T&NB=[destination]&ME=[message]&FL=F&ON=FromVM&TM=Y”/>
Form Method
The following parameters can be included in the query string and are set by the MDC before submitting the query:
[acc_user] specifies the account name for the gateway used to submit the information
[acc_pwd]
[otp_msg] sets the password for the gateway account specified by the [Username] parameters specifies the part of the query string, where the OTP is substituted
[otp_dest] specifies the part of the query string, where the destination for the OTP (usually the mobile phone number) is substituted. The query string should also incorporate any other parameters which might be expected by the gateway.
This field designates either the GET or POST method for transferring account and message data to the
HTTP/HTTPS gateway.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
44
2. Configuration Tool: Field Listings
Table 28: Voice Server Fields (continued)
Field Name Description
Result Matching Rules
List of result matching rules. A result page is returned by the gateway service when a text message is submitted by the GET or POST methods. This page would normally be a HTML formatted page containing specific error codes and/or additional messages for success/failure.
Click Add Result to define a new result matching rule.
Message Delivery Component Result
Name
Messagetype
Matching Pattern
Audit Text
Test Voice
Send Test Message To
Phone number to send a message to test the configuration settings.
Click Test Settings to effectively send a test message.
Description used to distinguish between different result matching rules.
The category of the result message.
n n n
Information . Message has been delivered successfully.
Warning . The submission or delivery failed, but it is most likely a specific error only affecting this user.
Error . An error occurred while attempting delivery.
This field specifies the result page template to match the result page returned by the
HTTP service. If this template is matched, the corresponding audit message is composed and returned to the IDENTIKEY Appliance audit message.
This field specifies the audit message template for the message to be compiled and sent back to the IDENTIKEY Appliance.
Variables may be included in this field.
2.3.12. LDAP User Synchronization
LDAP user synchronization is server-specific and therefore requires configuring specifically for different LDAP servers. To set up synchronization requires configuring a synchronization profile. The tables below present: n n
General fields for a synchronization profile
Filter fields: records to be synchronized from the source LDAP server can be filtered by matching certain
IDENTIKEY Appliance 3.11.12 - Administrator Reference
45
2. Configuration Tool: Field Listings n attributes. All attributes listed must match for a user account to be synchronized.
Attribute Mapping fields: this is the mapping of LDAP server attributes to user account properties.
For example configurations, refer to the IDENTIKEY Appliance Administrator Guide .
For more information about LDAP user synchronization, refer to the IDENTIKEY Appliance Product Guide .
Table 29: IDENTIKEY Authentication Server LDAP User Synchronization: General Fields
Field Name Description
Tracing
Tracing n n n
None . No tracing / disable tracing
Basic . Show all logging information, except debugging information
Full . Shows all logging information, debugging information included. This level is advised for Troubleshooting.
Adding a Synchronization Profile
Enabled
Description
Start Time
Frequency
Create Users
Delete Users
Enable Created Users
Update Users
LDAP URI
Bind DN
This field must be checked to enable automatic synchronizations using this synchronization profile at the frequency defined in the Frequency field (see below).
The default value is disabled, i.e. unchecked, in which case the profile is not operational and no user accounts are updated or copied from the LDAP Server.
A description should be entered to help identify this synchronization profile.
The time that the first synchronization of a day is to start.
The frequency defines the interval at which automatic synchronization occurs, once the profile has been manually configured. Synchronization frequency can be configured from every 15 minutes to every 24 hours.
Check this box to allow users to be created during synchronizations.
If this option is checked, the LDAP Synchronization process will go through the users that it has created on IDENTIKEY Appliance, and will check to make sure that they still exist on the
LDAP side. If they don't, they will be deleted from IDENTIKEY Appliance. This function does not work if the Reporting Scenario is not enabled in IDENTIKEY Appliance.
If users are to be created during synchronizations, create them as enabled users.
Allow synchronizations to update existing users. Select from drop down list: n n n n
None – do not update existing users during synchronization
All – update all existing users during synchronization, if necessary
Created by LDAP Synchronization only – only update user records previously created by LDAP Synchronization
Not created by LDAP Synchronization – only update user records NOT previously created by LDAP Synchronization
This is the protocol and host of the source LDAP server.
This is the Distinguished Name to authenticate towards the LDAP server. This should be a string-represented DN as defined in RFC 1779. Entering the bind DN is optional.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
46
2. Configuration Tool: Field Listings
Table 29: IDENTIKEY Authentication Server LDAP User Synchronization: General Fields (continued)
Field Name Description
Bind Password
Search Base
Filter
Attribute Mapping
Destination
Create Missing OU's
Mirror OU Structure
Include LDAP Children
Return DIGIPASS to Parent
OU on Move/Delete
This is the bind password to authenticate towards the LDAP server. Entering the bind password is optional.
The search base is the starting point for searches in the LDAP server. This should be a stringrepresented DN as defined in RFC 1779.
This field serves to add LDAP attribute filter properties to the synchronization profile (refer to the Table
IDENTIKEY Authentication Server LDAP User Synchronization: Attribute Filter Fields
below for more details).
This field serves to add LDAP attribute mapping properties to the synchronization profile (refer to the Table
IDENTIKEY Authentication Server LDAP User Synchronization: Attribute Mapping
below for more details).
The Destination field defines the domain and optionally the organizational unit on the
IDENTIKEY Appliance where the user accounts will be created or updated. The Destination field therefore defines the root of the replicated organizational structure.
Checking this box will enable the synchronization process to create the same organizational structure on the destination data store as exists on the source LDAP data store. The synchronization will create the organizational structure on the destination data store if it does not already exist.
During synchronization the LDAP Synchronization Tool tries to reconcile the organizational structure of the source LDAP data store with the organizational structure of the destination data store.
If the structures are the same: The synchronization will proceed without creating any more organizational units.
If the structures differ:To create any missing organizational units with users in them, the option Create Missing OU's needs to be selected. With this option selected, users in organizational units will be created that already exist in IDENTIKEY Authentication Server.
Allow synchronization to create records derived from LDAP children. This option will replicate the organizational structure of the source LDAP data store onto the destination IDENTIKEY
Authentication Server data store, where the organizational structure will be created, should that not already exist. If the Mirror Organizational Unit Structure option is not selected, the
LDAP children will be synchronized, but on the destination IDENTIKEY Authentication Server data store they will be created straight under the root directory, without extra organizational units being created.
If, during synchronization, the LDAP Synchronization Tool detects that a user has been deleted, it will reassign the user's DIGIPASS to the organizational unit's administrator account.
The LDAP Synchronization Tool will interpret a moved user as being deleted from its original organizational unit. When the user is created in its new organizational unit by the LDAP Synchronization Tool, the original DIGIPASS will be re-assigned to the user.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
47
2. Configuration Tool: Field Listings
Table 30: IDENTIKEY Authentication Server LDAP User Synchronization: Attribute Filter Fields
Field Name Description
Attribute
Match
This must be the name of an LDAP server attribute. All attributes listed must match for a user account to be synchronized.
This is the value for the attribute defined in the previous field and must match for a user account to be retrieved for synchronization. Asterisks can be used as wild cards for the value, indicating zero or more characters.
Table 31: IDENTIKEY Authentication Server LDAP User Synchronization: Attribute Mapping Fields
Field Name Description
Type
Source Attribute/Value
Destination Property
This defines whether the mapping is n n for an LDAP attribute name (Type: ldap ) for a constant value (Type: constant ).
For type ldap , this entry should be an LDAP attribute name.
For type constant , this entry should be the value of the corresponding IDENTIKEY Authentication Server Property.
This is the property name in the IDENTIKEY Authentication Serverwhich corresponds to the
LDAP server attribute specified in the previous field.
For all possible values for these properties, see Section
.
IDENTIKEY Authentication Server properties available for attribute mapping are: n n n n n n n n n n n n n n n n n n n n
User ID
User Name
Description
Mobile Phone Number
Phone Number
Password
Assigned DIGIPASS
Linked User ID, Linked User's Domain n
Users can be linked to other users by supplying the Linked User's
Domain and the Linked User ID fields. Both fields must have values supplied, either by having an LDAP attribute mapped to them, or by supplying a fixed value.
Local Authentication (set to 'Default' if unspecified)
Back-End Authentication (set to 'Default' if unspecified)
Expiration time
Disabled
Lock Count
Locked (set to ' False' if unspecified)
Offline Authentication (set to 'Default' if unspecified)
Virtual DIGIPASS Delivery Method
Virtual DIGIPASS MDC Profile
Virtual Signature Delivery Method
Virtual Signature MDC Profile
IDENTIKEY Appliance 3.11.12 - Administrator Reference
48
2. Configuration Tool: Field Listings
Table 31: IDENTIKEY Authentication Server LDAP User Synchronization: Attribute Mapping Fields (continued)
Field Name Description
Destination This is the domain and (optionally) the organizational unit in the where user accounts will be copied to or updated. If the domain is changed after user accounts have already been copied, the user accounts are copied to the new domain but not deleted from the previous domain. If the organizational unit is changed to another one in the same domain, user accounts which have been created or updated by this synchronization profile are moved from the old to the new location.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
49
3. SSL Cipher Suites
3.
SSL Cipher Suites
SSL cipher suites can be used with SOAP and SEAL communicators. IDENTIKEY Appliance supports SSL cipher suites defined under the security level labels Very High, High, Medium, and Low.
n n n
SEAL will accept SSLv2 and SSLv3 connections.
SOAP will only accept SSLv3 and TLSv1 connections.
RADIUS/EAP protocols will accept SSLv2 and SSLv3 connections.
The security levels are applied to the following communication protocols: n n n
SOAP
SEAL
RADIUS (RADIUS / EAP-TTLS and RADIUS / PEAP only)
Table 32: Cryptographic Protocols Supported in Different Cipher Suite Security Levels
SSL Cipher Suite
Security Level
Cryptographic Protocol Support
SSLv2 SSLv3 TLSv1 TLSv1.1
Very High
High
Medium
Low
û
û
û
û
û
û
û
ü
ü
ü
ü
ü
ü
ü
ü
ü
TLSv1.2
ü
ü
ü
ü
3.1. Default Security Levels for SSL Cipher Suites
For each communication interface of IDENTIKEY Appliance, the SSL cipher suite security level is set by default. The following table lists these default level settings.
Table 33: Default SSL Cipher Suite Security Levels for Communication Interfaces
IDENTIKEY Authentication Server Communication Interface
IDENTIKEY Authentication Server SOAP Communicator
IDENTIKEY Authentication Server SEAL Communicator with SSL/TLS
IDENTIKEY Authentication Server RADIUS Communicator
IDENTIKEY Authentication Server Live Audit Connection (SEAL)
Default Security Level of
SSL Cipher Suite
Very High
Very High
Medium
Very High
You can configure a communicator that is enabled with SSL/TLS to use another than the default SSL cipher suite security level and select either Very High , High , Medium , or Low via the Configuration Tool. Navigate to Authentication Server and select the required communicator to configure the cipher suite security level.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
50
3. SSL Cipher Suites
3.1.1. Blocked Cipher Suites
The IDENTIKEY Authentication Server communication interfaces, when configured to use SSL/TLS, will actively block certain cipher suites. All IDENTIKEY Authentication Server components actively block the suites to which the criteria listed below apply. This also includes custom cipher suites, i.e. if the criteria also apply to custom-defined cipher suites, the IDENTIKEY Authentication Server components will also actively block these suites.
Criteria for cipher suites to be blocked: n n n n n n
All cipher suites which do not offer encryption
All cipher suites which do not offer authentication
All export encryption algorithms
Cipher suites defined by OpenSSL as low encryption
All cipher suites which use MD5 as hashing algorithm
All cipher suites that use pre-shared keys
3.1.2. Cipher Suites in IDENTIKEY Authentication Server Web Administration Service
The following cipher suites are accepted by the IDENTIKEY Authentication ServerWeb Administration Service :
Table 34: Overview of Cipher Suites in the Web Administration Service
Cipher Suite Cryptographic Key
Exchange
Protocol(s)
Authentication
Encryption MAC
ECDH
ECDH
RSA
ECDSA
Algorithm
AESGCM(128) AEAD
AESGCM(128) AEAD
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 * TLSv1.2
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_
SHA256 *
TLSv1.2
TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256 * TLSv1.2
TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256
*
TLSv1.2
TLS_RSA_WITH_AES_128_GCM_SHA256 *
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 *
°
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_
SHA384 * °
TLSv1.2
TLSv1.2
TLSv1.2
TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384 * ° TLSv1.2
TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384
* °
TLSv1.2
TLS_RSA_WITH_AES_256_GCM_SHA384 * ° TLSv1.2
ECDH/RSA ECDH
ECDH/ECDSA ECDH
RSA
ECDH
ECDH
RSA
RSA
ECDSA
ECDH/RSA ECDH
ECDH/ECDSA ECDH
RSA RSA
AESGCM(128) AEAD
AESGCM(128) AEAD
AESGCM(128) AEAD
AESGCM(256) AEAD
AESGCM(256) AEAD
AESGCM(256) AEAD
AESGCM(256) AEAD
AESGCM(256) AEAD
IDENTIKEY Appliance 3.11.12 - Administrator Reference
51
4. RADIUS Dictionary Format
4. RADIUS Dictionary Format
A custom RADIUS dictionary can be uploaded. This file contains dictionary translations for parsing requests and generating responses. This section describes the format and syntax of such a dictionary file. The format is derived from the RADIUS 5 spec, dated July 1996.
All transactions are composed of Attribute/Value Pairs. The value of each attribute is specified as one of these valid data types: n n n n n n n n n n n n n hexadecimal: Hexadecimal string hex1, hex4:1- or 4-byte hexadecimal number string: 0-254 octets (includes null terminator) stringnz: 0-254 octets (without null terminator) ipv6addr: 16 octets in network byte order (per RFC-3162) ipv6prefix: 2-18 octets in network byte order (per RFC-3162) ipv6interface: 8 octets in network byte order (per RFC-3162) ipaddr: 4 octets in network byte order ipaddr-pool: IP address selected from an IP address pool ipxaddr-pool: IPX network number selected from an IPX address pool integer: 32 bit value in big endian order (high byte first) int1, int4: 1- or 4-byte decimal number (integer is equivalent to int4) time: 32 bit value in big endian order seconds since 00:00:00 GMT, Jan. 1, 1970
All attribute names and value names in the supplied RADIUS dictionary file are derived from the Radius spec by replacing all non-alphanumeric characters with dashes ('-').
The following rules apply to the creation and use of dictionaries: n n n
All comments begin with a '#' character in column 0 OR appear on a attribute or value line with "<whitespace>#<white-space>" as the MANDATORY delimiter between dictionary data and comment text.This is a simple parser.
All attribute (and attribute value) names and numeric codes must be unique within this dictionary.
There are three meaningful line entry formats in the dictionary, one for vendor, one for attributes and one for attribute values :
VENDOR_KEY VENDOR_NAME VENDOR_CODE [COMMENT_DELIMITER COMMENT_TEXT]
ATTRIBUTE_KEY ATTRIBUTE_NAME ATTRIBUTE_CODE DATA_TYPE FLAGS [COMMENT_DELIMITER COMMENT_
TEXT]
VALUE_KEY ATTRIBUTE_NAME VALUE_NAME VALUE_CODE [COMMENT_DELIMITER COMMENT_TEXT] n
Legend for last column of an attribute entry n n n n n
'c': indicates a SINGLE valued attribute that is a candidate for inclusion in a user's check list
'C' : indicates a MULTI valued attribute that is a candidate for inclusion in a user's check list
'r': indicates a SINGLE valued attribute that is a candidate for inclusion in a user's reply list
'R': indicates a MULTI valued attribute that is a candidate for inclusion in a user's reply list
'o','O' : ordered attribute, some attributes (e.g. Reply-Message) may need to be presented in a particular order to make sense.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
52
4. RADIUS Dictionary Format
Note
- Absence of any of {C,c,R,r} flags indicates an item that is neither a reply nor check list item (e.g. State, Proxy-
State).
- All FLAG characters on a given attribute line must be clustered together to parse properly (i.e. no white space is allowed between individual characters).
Source: http://www.juniper.net/techpubs/en_ US/uac/topics/reference/general/uac- radius- dictionaryguidelines.html
IDENTIKEY Appliance 3.11.12 - Administrator Reference
53
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
5. IDENTIKEY Authentication Server Administration Web Interface
Field Listings
5.1. User Properties
5.1.1. Dashboard
Table 35: User - Dashboard
Field Name Description
Account Overview
This section provides an overview of the DIGIPASS user account. You can also obtain this information from the User Account tab.
For a detailed description of the user account fields, refer to Section
Last Authentication The date and time of the last authentication for this user.
Account Status
Expires
Static Password
Specifies whether a DIGIPASS user account is enabled or disabled. If disabled, all requests for the user will be rejected by IDENTIKEY Authentication Server.
The date on which the user account cannot longer be used for authentication.
Administration Privileges
Policy Overrides
The static password. This may be used for static password checking by the
IDENTIKEY Authentication Server or may be a record of a password in a back-end system.
Indicates if the user has administrative privileges set.
This section contains information about user-specific settings that override the settings in the applicable policy. You can also obtain this information from the Policy Overrides tab.
For a detailed description of the policy overrides settings, refer to Section
.
Local Authentication Indicates if there are policy overrides for the local authentication setting in the applicable policy.
Back-End Authentication
Offline Authentication
Indicates if there are policy overrides for the back-end authentication setting in the applicable policy.
Indicates if there are policy overrides for the offline authentication setting in the applicable policy.
Virtual DIGIPASS
Virtual Signature
Indicates if there are policy overrides for the Virtual DIGIPASS setting in the applicable policy.
Indicates if there are policy overrides for the Virtual Signature setting in the applicable policy.
User Info
IDENTIKEY Appliance 3.11.12 - Administrator Reference
54
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 35: User - Dashboard (continued)
Field Name Description
This section contains general user information. You can also obtain this information from the User Account tab.
For a detailed description of the user info fields, refer to Section
User Name The full name of the user; ODBC database only.
Phone
Mobile
The user's phone number; ODBC database only.
The user's mobile phone number; this may be used for Virtual DIGIPASS logins.
Email Address
ODBC database only.
The user's e-mail address; this may be used for Virtual DIGIPASS logins.
Description
ODBC database only.
Any descriptive text or notes; ODBC database only.
Assigned DIGIPASS
This section contains information about the five last used DIGIPASS authenticators assigned to this user. You can access the Assigned
DIGIPASS tab by selecting the corresponding hyperlink; for more information on this tab, refer to Section
Serial Number
DIGIPASS Type
Status
The serial numbers of the last five DIGIPASS authenticators assigned to the relevant user.
For instance DIGIPASS 300.
Active Applications
Virtual DIGIPASS (VDP)
Displays the expiration date of the authenticator or if it is already expired; this field can also display the grace period expiration date or if the end of the grace period has already been reached.
This field lists all active applications for the relevant authenticator.
Indicates which type of VDP the relevant authenticator is - possible values are
Primary and Backup .
Recent Activity
This section lists the five last activity records for a user. You can also obtain information on recent user activity from the Recent Activity tab.
For a more detailed description of the recent activity fields, refer to Section
.
Time The date and time when the user activity was recorded.
Category
Description
The category of the audit message.
The textual description of the audit message.
Used Clients
This section lists the five last client components used by the selected user. You can also obtain information on recently used clients from the
Recent Activity tab.
For a more detailed description of the recent activity fields, refer to Section
.
Time The time at which the last activity for the relevant used client was recorded.
Client Type States which type the used client is.
Click the client identifier to go to the Client Properties page for this client.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
55
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 35: User - Dashboard (continued)
Field Name
Policy ID The policy related to the used client.
Description
Click the policy ID to go to the Policy Properties page for this policy.
5.1.2. User Account
Table 36: User - User Account
Field Name
User ID
Organizational Unit
Last Authentication
Account Status
Expires
Lock Count
Static Password
Last Password Update
User Info
User Name
Phone
Description
ID of the selected user.
ODBC database only; lists 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 to change this.
The date and time of the last authentication for this user. This field is used to determine how many days an account has remained inactive. This field will be populated for the first time during the first authentication.
Specifies whether a DIGIPASS user account is enabled or disabled. If disabled, all requests for the user will be rejected by IDENTIKEY Authentication Server.
It is possible to set the date on which the user account cannot longer be used for authentication. This field is typically used for temporary users such as contractors or external auditors. IDENTIKEY Authentication Server does not automatically delete
"expired" users.
Specifies whether a DIGIPASS user account is locked or not. If locked, all requests for the user will be rejected by the IDENTIKEY Authentication Server.
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.
The static password. This may be used for static password checking by the
IDENTIKEY Authentication Server or may be a record of a password in a back-end system.
In view mode, the system will only show whether a password is set or not.
The Set Password and Reset Password commands are used to change this, although it can also be entered when creating the DIGIPASS user account.
Date and time of the user's last static password update.
The full name of the user; ODBC database only.
The user's phone number; ODBC database only.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
56
Email Address
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 36: User - User Account (continued)
Field Name
Mobile
Description
The user's mobile phone number; this may be used for Virtual DIGIPASS logins.
ODBC database only.
The user's e-mail address; this may be used for Virtual DIGIPASS logins.
ODBC database only.
Any descriptive text or notes; ODBC database only.
Description
Account Linking
Linked User ID It is possible to share a DIGIPASS authenticator 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 authenticator to that person.
This feature is used by assigning the DIGIPASS authenticator to one user account, then linking all the other user accounts for the person to the one that has the
DIGIPASS authenticator.
This field is read only.
ODBC Database only:
If a user is linked to another user, their Linked User Account field will show the user
ID and domain of the linked user, for example: testuser [vasco.com]
Update History
Created
Modified
The date and time that the DIGIPASS user account was created. Read-only.
The date and time that the DIGIPASS user account was last modified. Read-only.
5.1.3. Assigned DIGIPASS
In this tab, all authenticators assigned to the selected user are listed. For each DIGIPASS authenticator, 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 authenticator with serial number 0058384426 has two active applications: one response-only application RESP_ONLY and oneChallenge/Response application CHALLENGE.
If the user does not have any DIGIPASS authenticator assigned directly, but is linked to another user to use the
DIGIPASS authenticator (see Linked User Account ), the linked user's DIGIPASS authenticator list is shown with the serial numbers in square brackets (eg. [0058384426]).
When a DIGIPASS authenticator in the list is selected, the remainder of the property sheet tab indicates values from the corresponding DIGIPASS record.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
57
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Read-only.
5.1.4. Policy Overrides
Table 37: User - Policy Overrides
Field Name
Local Authentication
Description
Specifies whether authentication requests for the user account will be handled by the
IDENTIKEY Authentication Serverusing Local Authentication. For more information about local authentication and back-end authentication, refer to the IDENTIKEY Authentication Server
Product Guide , Section " Authenticating Users" .
Normally, this field will be Default , meaning that the policy applicable to the authentication request determines the setting. This field in 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 authenticator that meets the restrictions. For example, if the policy requires a DIGIPASS 300, but the user has a DIGIPASS 700, the user cannot use DIGIPASS authentication under that policy.
Possible values: n n n n n
Default . Use the setting of the parent policy.
None . IDENTIKEY Authentication Server will not use local authentication under this policy. They may be handled using back-end authentication or not handled at all by
IDENTIKEY Authentication Server.
Digipass Only . IDENTIKEY Authentication Server will always use local authentication under this policy, using DIGIPASS authentication. If DIGIPASS authentication is not possible, the user cannot log in. Back-end authentication may also be used.
DIGIPASS/Password during Grace Period . IDENTIKEY Authentication Server will always use local authentication under this policy; possibly using DIGIPASS Authentication for Windows Logon if applicable. The static password can only be used within a (configurable) grace period until a DIGIPASS authenticator is used the first time.
Back-end authentication may also be used.
DIGIPASS or Password . This authentication mode allows users to permanently use their static password or their DIGIPASS authenticator, even after the grace period has expired and/or they have previously already used their authenticator for authentication. Use of this authentication mode is subject to licensing.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
58
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 37: User - Policy Overrides (continued)
Field Name
Back-End Authentication
Description
Specifies whether authentication requests for the user account will be handled by the
IDENTIKEY Authentication Server using back-end authentication. For more information about local authentication and back-end authentication, refer to the IDENTIKEY Authentication Server
Product Guide , Section " Authenticating Users" .
Normally, this field will be Default , meaning that the policy applicable to the authentication request determines the setting (see
Table 52: Policy Properties - Policy ). This field in the
DIGIPASS user account is used to override the policy setting for special cases.
Possible values:
Default
None
If Needed
Always
Use the setting of the parent policy.
Back-end authentication will not be used.
IDENTIKEY Appliance will utilize back-end authentication but only in certain cases: n n n n n
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, during the grace period, or if the local authentication mode is set to DIGIPASS or Password .
Provisioning registration n
IDENTIKEY Appliance will use back-end authentication for every authentication and provisioning registration request.
This setting is required, if you want to use offline authentication for DIGIPASS Authentication for Windows Logon.
To enforce static password verification during offline authentications via DIGIPASS Authentication for
Windows Logon, you need to disable Stored Password Proxy and set Back-End Authentication to
Always .
IDENTIKEY Appliance 3.11.12 - Administrator Reference
59
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 37: User - Policy Overrides (continued)
Field Name
Offline Authentication
Description
Indicates whether offline Authentication has been enabled for this user for Windows Logon.
When offline authentication is disabled for a user, be aware of the following: n n
Disabling offline authentication for a user means that IDENTIKEY Authentication
Server will not send any new encrypted offline logon data to the client PC .
Disabling offline authentication for a user means that the user will still be able to use offline authentication from the time that it is disabled until the encrypted offline logon data has expired OR until the user performs their next online authentication.
The options are: n n n
Default - the settings for offline authentication are dependent on the prevailing policy settings.
No - offline authentication is not enabled.
Yes - offline authentication is enabled
This function is only available if Windows Logon is enabled on your system.
Virtual DIGIPASS
Virtual DIGIPASS Delivery Method The method used to deliver the Virtual DIGIPASS to the selected user. The options are: n n n n
Default - Use the settings of the parent policy
Email - Deliver the OTP via email. Requires an email address to be set up for the user.
SMS - Deliver the OTP via SMS. The DIGIPASS user account must have a mobile phone number.
Voice - Deliver the OTP via voice channel (i.e. dictated over a phone line).
Virtual DIGIPASS MDC Profile
The DIGIPASS user account must have a mobile phone number. This field also allows you to specify a combination of delivery methods, specifically: n n n
Email and SMS
SMS and Voice
Email and Voice
The MDC profile whose settings should be used for this delivery method. An MDC profile defines a specific group of settings for a particular delivery method. If there is no specified
MDC profile in this field, then the highest-ranked, enabled, and available MDC profile for the specified delivery method/s will be used.
The MDC profile name should not be confused with the profile's display name. The display name is simply an ad-hoc field used primarily to describe and further identify the profile. The
MDC profile name is the name that appears in the Profile column of the MDC Configuration
GUI.
The MDC profile name is non-unique; as such, multiple MDC profiles with the same name may exist for this delivery method. The highest-ranked, enabled, and available MDC profile with the specified MDC profile name will be used.
Virtual Signature
IDENTIKEY Appliance 3.11.12 - Administrator Reference
60
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 37: User - Policy Overrides (continued)
Field Name
Virtual Signature Delivery Method
Description
The method used to deliver the virtual signature to the selected user. The options are:
Virtual Signature MDC Profile n n n n
Default - Use the settings of the parent policy
Email - Deliver the OTP via email. Requires an email address to be set up for the user.
SMS - Deliver the OTP via SMS. The DIGIPASS user account must have a mobile phone number.
Voice - Deliver the OTP via voice channel (i.e. dictated over a phone line). The
DIGIPASS user account must have a mobile phone number.
This field also allows you to specify a combination of delivery methods, specifically: n n n
Email and SMS
SMS and Voice
Email and Voice
The MDC profile whose settings should be used for this delivery method. An MDC profile defines a specific group of settings for a particular delivery method. If there is no specified
MDC profile in this field, then the highest-ranked, enabled, and available MDC profile for the specified delivery method/s will be used.
The MDC profile name should not be confused with the profile's display name. The display name is simply an ad-hoc field used primarily to describe and further identify the profile. The
MDC profile name is the name that appears in the Profile column of the MDC Configuration
GUI.
The MDC profile name is non-unique; as such, multiple MDC profiles with the same name may exist for this delivery method. The highest-ranked, enabled, and available MDC profile with the specified MDC profile name will be used.
5.1.5. User Attributes
Refer to Section
for the list of user attributes in this tab.
5.1.6. Admin Privileges
A list of all administrative privileges assigned to the selected user. Refer to Section
5.4. Administrative Privileges
for more information on administrative privileges.
5.1.7. Offline Authentication
Table 38: User - Offline Authentication
Field Name
Client
Description
The client to which the offline authentication data was sent for this user.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
61
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 38: User - Offline Authentication (continued)
Serial Number
DIGIPASS Type
Offline Data
Field Name Description
Serial number of the DIGIPASS authenticator used to generate the one-time password used for authentication.
Type of DIGIPASS used to generate the one-time password for authentication.
The date and time or the event block for which the offline authentication data was generated.
5.1.8. Recent Activity
Table 39: User - Recent Activity
Field Name
Time
Code
Description
Category
Client
DIGIPASS
Policy ID
Reason
Description
The date and time when the user activity was recorded.
The audit message code of the user activity.
If you click a particular code, the respective audit message record is displayed (see
The textual description of the audit message.
The category of the audit message.
The location of the client component that triggered the audit message.
If you click a particular client, the properties of the respective client component are displayed (see
The serial number of the DIGIPASS authenticator associated with the audit message.
If you click a particular policy, the properties of the respective DIGIPASS authenticator are displayed (see
The identifier of the policy handling the request.
If you click a particular policy, the properties of the respective policy are displayed (see
The textual description indicating the reason for a failure.
5.1.9. Reports
Refer to Section
for the list of reports available in this tab.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
62
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
5.1.10. Further User Fields
Table 40: User - Further User Fields
Field Name
New Password
Confirm Password
Domain
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.
The domain to which the user belongs; ODBC database only.
Read only. This cannot be changed.
5.2. User Attributes
Table 41: User Attribute Fields
Field Name Description
Attribute Group
Name
Attribute Groups provide a way to add different attributes to the user account for different client components.
Client Components – an SBR Plug-In, IIS Module, or custom SOAP applications – may request a specific attribute group during an authentication request. IDENTIKEY Appliance will return any custom user attributes set for that user in the specified attribute group.
RADIUS reply attributes may be returned to RADIUS clients. The attribute group(s) to be used are specified in the policy.
See the IDENTIKEY Appliance Product Guide , Section User Attributes for further information.
The name of the attribute.
Custom User attributes: This must match the name of an attribute expected by the client component. For the DIGIPASS Pack for IIS Basic Authentication, this would be either User-Name or
Password.
RADIUS attributes: This must match an entry in the RADIUS dictionary in use by the IDENTIKEY
Appliance. For relevant instructions, refer to the section on how to customize the RADIUS attributes dictionary in the IDENTIKEY Appliance Administrator Guide .
IDENTIKEY Appliance 3.11.12 - Administrator Reference
63
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 41: User Attribute Fields (continued)
Field Name Description
Usage
Value
Specifies the usage of the user attribute. This is an optional setting, not available for RADIUS attributes.
Options:
Basic Designates an attribute used by the DIGIPASS module for IIS Basic
Authentication.
Check
Profile
Used to specify a check attribute for SBR, where the SBR plug-in is in use. Refer to the DIGIPASS Authentication for Steel-Belted Radius
Server Administrator Guide for more information.
Used to specify the name of a RADIUS profile for SBR, where the SBR plug-in is in use.
Return Used to specify a return attribute for SBR, where the SBR plug-in is in use.
This value of the attribute. In the DIGIPASS module for IIS Basic Authentication example above, this would be a user ID or password.
5.3. User Reports
For generating a user-specific report from the Reports tab in the User Properties page, by default, the following reports are available:
Table 42: Default Reports
Report
Account Lock Trend
Administration Activity Summary
Authentication Activity by User
Authentication Trend
Detailed Activity Summary
Detailed Authentication
Detailed DIGIPASS Registration Digipass:User ID
Digipass:Domain
Default Fieldss
Detailed Provisioning
Detailed Signature Validation
IDENTIKEY Appliance 3.11.12 - Administrator Reference
64
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 42: Default Reports (continued)
Report
DIGIPASS About To Expire
Default Fieldss
DP Assignment Activity Summary
DP Last Authentication List
Expired DIGIPASS
Digipass:User ID
Digipass:Domain
Digipass:User ID
Digipass:Domain
Digipass:User ID
Digipass:Domain
Digipass:User ID
Digipass:Domain
Failed Operations Summary
Inactive DIGIPASS List Digipass:User ID
Digipass:Domain
Provisioning Activity by User
Provisioning Activity Trend
RADIUS User Activity Summary
RADIUS User Detailed Activity
Signature Validation History
Succeeded Operations Summary
Transaction Signing Activity by User
Transaction Signing Activity Trend
5.4. Administrative Privileges
Most administrative privileges rely on other privileges to work correctly.
The following information lists the available privileges and the privileges set by IDENTIKEY Authentication Server when each is assigned to a user via the Administration Web Interface.
Table 43: Administrative Privileges – ODBC Data Store
Privilege Name Depends On Notes
Access Data in All Domains Administrative Logon With this, an administrator can view and manage data in all domains, not just their own.
Only available if the user belongs to the master domain and not to an organizational unit.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
65
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 43: Administrative Privileges – ODBC Data Store (continued)
Privilege Name Depends On Notes
Access Domain Administrative Logon
Administrative Logon
IDENTIKEY Authentication
Server System Logon
Administrative Logon
When this permission is set, it allows generating reports for all orgunits in the entire domain of the administrator.
Required for all administrators.
Without this privilege, the user will not be able perform any administration because they will not be able to log on.
It could be removed as a temporary measure without removing all the user’s privileges.
This privilege controls the IDENTIKEY Authentication Server system logon. Without this privilege, the user will not be able to log on to the system administration interface of the IDENTIKEY Authentication
Server.
Assign DIGIPASS
Appliance Administration
Administrative Logon
View User
View DIGIPASS
View Domain
View Organizational Unit
Administrative Logon This privilege specifies whether the user is allowed to modify the
IDENTIKEY Appliance system administration settings using the
IDENTIKEY Appliance Configuration Tool.
Bind DIGIPASS
Cancel Task
Change Report File Ownership
Change Report Owner
Create Back-End Server
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Administrative Logon
View Task
Administrative Logon
View User
View Domain
View Organizational Unit
View Report File
Administrative Logon
View User
View Domain
View Organizational Unit
View Report Definition
Administrative Logon
View Back-End Server
IDENTIKEY Appliance 3.11.12 - Administrator Reference
66
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 43: Administrative Privileges – ODBC Data Store (continued)
Privilege Name Depends On Notes
Create Component Administrative Logon
View Policy
View Component
Create Domain Administrative Logon
Access Data in All Domains
View Domain
Create EMV-CAP Application Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Only available if the user belongs to the master domain and not to an organizational unit.
Allows creation of EMV-CAP DIGIPASS records, including the BLOB.
This privilege will only be available if: n n
The HSM, EMV-CAP and EMV-CAP Provisioning license options are all enabled
The administrator account is located in the Master domain
Create Key
Create Organizational Unit
Create Policy
Create Report Definition
Create User
Deactivate DIGIPASS
Delete Admin Session
Administrative Logon
View Key
Administrative Logon
View Domain
View Organizational Unit
Administrative Logon
View Policy
Administrative Logon
View Report Definition
Administrative Logon
View User
Unlock User
Enable User
Disable User
Set User Expiration
Set User Password
Reset User Password
View Domain
View Organizational Unit
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Administrative Logon
View Admin Session
Create report definition and report format.
Create user and user attribute.
This privilege allows an administrator to deactivate a
DIGIPASS authenticator, or, in the context of Multi-Device Licensing and Activation, to generate a deactivation message for a specific
DIGIPASS instance.
With this privilege an administrator can delete any administrative session.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
67
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 43: Administrative Privileges – ODBC Data Store (continued)
Privilege Name Depends On Notes
Delete Back-End Server
Delete Component
Delete DIGIPASS
Administrative Logon
View Back-End Server
Administrative Logon
View Component
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Delete Domain
Allows an administrator to delete aDIGIPASS authenticator from the storage: delete DPSoftParams, DIGIPASS and DIGIPASS Applications.
In the context of Multi-Device Licensing and Activation, when administrating DIGIPASS licenses as well as instances, when a DIGIPASS license is deleted, its DIGIPASS instances are also deleted. Only when DIGIPASS instances or only deactivated DIGIPASS instances linked to this DIGIPASS license exist, can the DIGIPASS license be deleted.
Only available if the user belongs to the master domain and not to an organizational unit.
Delete Key
Delete Organizational Unit
Delete Policy
Delete Report Definition
Delete Report File
Delete Task
Delete User
Disable Server PIN
Administrative Logon
Access Data in All Domains
View Domain
Administrative Logon
View Key
Administrative Logon
View Domain
View Organizational Unit
Administrative Logon
View Policy
Administrative Logon
View Report Definition
Administrative Logon
View Report File
Administrative Logon
View Task
Administrative Logon
View User
View Domain
View Organizational Unit
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Delete report definition and report format.
Delete user and user attribute.
With this privilege an administrator can disable the use of a Server
PIN with a specific DIGIPASS Application
IDENTIKEY Appliance 3.11.12 - Administrator Reference
68
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 43: Administrative Privileges – ODBC Data Store (continued)
Privilege Name Depends On Notes
Disable User
Download Report File
Enable Server PIN
Enable User
Administrative Logon
View User
View Domain
View Organizational Unit
Administrative Logon
View Report File
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Administrative Logon
View User
View Domain
View Organizational Unit
Force DIGIPASS PIN Change Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Generate DIGIPASS Activation Data
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Generate Virtual DIGIPASS
OTP
Import DIGIPASS
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
With this privilege an administrator can enable the use of a Server
PIN with a specific DIGIPASS Application.
This administrative privilege is only valid with DIGIPASS for Mobile
4.0
Create DIGIPASS Applications (you do not directly create DIGIPASS); create and update DPSoftParams; upload, import, query status and stop import for DPX File.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
69
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 43: Administrative Privileges – ODBC Data Store (continued)
Privilege Name Depends On Notes
Import User
Link User
Live Audit Connection
Administrative Logon
Assign DIGIPASS
Create User
Disable User
Enable User
Reset Last Authentication
Time
Reset Password
Set DIGIPASS Expiration
Set Password
Set User Expiration
Unlock User
Update User
View DIGIPASS
View User
View Domain
View Organizational Unit
Administrative Logon
View User
View Domain
View Organizational Unit
Administrative Logon
Link a user to another DIGIPASS user
Move DIGIPASS
With this, an administrator can connect from the Audit Viewer to the Authentication Server to receive live audit messages.
Move a DIGIPASS within the existing organizational structure (other domain, other organizational structure)
Move User
Replication Reconnect
Replication Status
Reset DIGIPASS Activation
Reset DIGIPASS Application
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Administrative Logon
View User
View Domain
View Organizational Unit
Administrative Logon
Replication Status
Administrative Logon
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Move user to an organizational unit
When resetting aDIGIPASS authenticator that has been activated in multi-device activation mode, the information related to Activation
Message 1 for DIGIPASS licenses is being reset with the action corresponding to this privilege.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
70
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 43: Administrative Privileges – ODBC Data Store (continued)
Privilege Name Depends On Notes
Reset DIGIPASS Application
Lock
Reset DIGIPASS PIN
Reset Last Authentication
Time
Reset Offline Authentication
Data
Reset User Password
Resume Task
Rotate Key
Run Report
Send DIGIPASS Activation
Data
Send Notification
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Administrative Logon
View User
View Domain
View Organizational Unit
Administrative Logon
View User
View Component
View Domain
View Organizational Unit
Administrative Logon
View User
View Domain
View Organizational Unit
Administrative Logon
View Task
Administrative Logon
View Key
Administrative Logon
View Report Definition
Administrative Logon
View Domain
View DIGIPASS
View Organizational Unit
Administrative Logon
With this privilege, an administrator can reset the offline authentication history for a certain user or for a certain user/computer combination.
With this privilege, an administrator can send notification messages to a specified user, e.g. for delayed or completed DIGIPASS activation.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
71
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 43: Administrative Privileges – ODBC Data Store (continued)
Privilege Name Depends On Notes
Set Administration Domains Set Administrative Privileges
View Administrative Privileges
View User
View Domain
View Organizational Unit
Administrative Logon
Set Administrative Privileges Administrative Logon
View User
View Administrative Privileges
View Domain
View Organizational Unit
Set Authentication Policy
Overrides
Administrative Logon
Set DIGIPASS Event Counter Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Set DIGIPASS Expiration Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Set DIGIPASS PIN
Set User Expiration
Set User Password
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Administrative Logon
View User
View Domain
View Organizational Unit
Administrative Logon
View User
View Domain
View Organizational Unit
Authentication policy overrides administrative privilege.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
72
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 43: Administrative Privileges – ODBC Data Store (continued)
Privilege Name Depends On Notes
Suspend Task
Take Report File Ownership
Take Report Ownership
Take Task Ownership
Test DIGIPASS OTP
Test DIGIPASS Signature
Unassign DIGIPASS
Administrative Logon
View Task
Administrative Logon
View Report File
Administrative Logon
View Report Definition
Administrative Logon
View Task
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
With this privilege an administrator can take ownership of any report file.
With this privilege an administrator can take ownership of any report.
With this an administrator is able to test-validate a one-time password in a Response-Only or Challenge/Response scenario .
With this an administrator is able to test-validate a signature. It can also be used as an optional third step in the administrator-initiated multi-device activation process where a signature generated by
DIGIPASS upon receiving Activation Message 2 is validated.
When unassigning aDIGIPASS authenticator that has been activated in multi-device licensing mode, it is not possible to unassign a
DIGIPASS license when a DIGIPASS instance, activated or deactivated, linked to the DIGIPASS license, exists. A DIGIPASS instance can never be unassigned.
Unbind DIGIPASS
Unlink User
Unlock DIGIPASS
Unlock User
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Administrative Logon
View User
View Domain
View Organizational Unit
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Administrative Logon
View User
View Domain
View Organizational Unit
IDENTIKEY Appliance 3.11.12 - Administrator Reference
73
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 43: Administrative Privileges – ODBC Data Store (continued)
Privilege Name Depends On Notes
Update Back-End Server
Update Back-End Settings
Update Component
Update DIGIPASS
Update Domain
Update Key
Update Organizational Unit
Update Policy
Update Report Definition
Update Task
Update User
View Admin Session
Administrative Logon
View Back-End Server
Administrative Logon
View Back-End Settings
Administrative Logon
View Policy
View Component
Administrative Logon
View DIGIPASS
View Domain
View Organizational Unit
Administrative Logon
View Domain
Administrative Logon
View Key
Administrative Logon
View Domain
View Organizational Unit
Administrative Logon
View Policy
Administrative Logon
View Report Definition
Administrative Logon
View Task
Administrative Logon
Disable User
Enable User
Reset Offline Authentication
Data
Set User Expiration
Unlock User
View Domain
View Organizational Unit
View User
Administrative Logon
With this privilege an administrator can updated the general backend server settings.
Update DIGIPASS and DIGIPASS Applications.
Update report definition; create, update and delete report format.
Update user; create, update and delete user attributes.
With this privilege an administrator can view active admin sessions.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
74
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 43: Administrative Privileges – ODBC Data Store (continued)
Privilege Name Depends On Notes
View Administrative Privileges
View Audit Information
Administrative Logon
View User
View Domain
View Organizational Unit
Administrative Logon This privilege provides access to the internal IDENTIKEY Appliance Audit Viewer and allows the administrator to browse to the
View Audit Message page using the audit message identifier
(AMID) as input parameter.
View Back-End Server
View Back-End Settings
Administrative Logon
Administrative Logon With this privilege an administrator can view the general back-end server settings.
With this privilege an administrator can view the PAN in clear text rather than encrypted format.
View Clear PAN Administrative Logon
View DIGIPASS
Administrative Logon View Component
View DIGIPASS
View Domain
View EMV PAN
Administrative Logon
View Domain
View Organizational Unit
Administrative Logon
View Domain
View Organizational Unit
Administrative Logon View Key
View Organizational Unit Administrative Logon
View Domain
Administrative Logon View Policy
View Recent DIGIPASS Activity
View DIGIPASS
View and query for DPSoftParams, DIGIPASS and DIGIPASS Application. Also permits the
Get Info
command.
Allows to look up recent authentication, signature validation, provisioning, and administration activity of any DIGIPASS authenticator within the allowed domain scope.
This privilege affects the commands in the Dashboard tab and the
Recent Activity tab as well as the respective SOAP commands when using the IDENTIKEY Authentication Server SDK.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
75
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 43: Administrative Privileges – ODBC Data Store (continued)
Privilege Name Depends On Notes
View Recent User Activity View User Allows to look up recent authentication, signature validation, provisioning, and administration activity of any DIGIPASS user within the allowed domain scope.
This privilege affects the commands in the Dashboard tab and the
Recent Activity tabs as well as the respective SOAP commands when using the IDENTIKEY Authentication Server SDK.
View and query for both report definition and report format.
View Report Definition
View Report File
View Task
View User
Administrative Logon
Administrative Logon
Administrative Logon
Administrative Logon
View Domain
View Organizational Unit
View and query users and user attributes.
5.5. Find/Manage DIGIPASS
Table 44: Find/Manage DIGIPASS Criteria
Domain
Field Name Description
The domain to which the DIGIPASS authenticator belongs.
Organizational Unit
Serial Number/s
Serial Number List
DIGIPASS Type
Application Name
Application Type
This field is read-only. The
Move
command must be used to change this.
The domain to which the DIGIPASS authenticator belongs.
This field is read-only. The
Move
command must be used to change this.
A range of serial numbers can be used to search for a DIGIPASS authenticator.
A comma-separated list of serial numbers to search for a DIGIPASS authenticator.
The type of DIGIPASS represented by the DIGIPASS record (e.g. DIGIPASS 300).
The DIGIPASS application is selected via this list.
Search a DIGIPASS authenticator by type; the following choices are available in the list: n n n n n n n
Any
Response-Only (RO)
Challenge/Response (CR)
Signature (SG)
Multi-Mode (MM)
Unlock (UL)
Master-Activation (MA)
IDENTIKEY Appliance 3.11.12 - Administrator Reference
76
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 44: Find/Manage DIGIPASS Criteria (continued)
Field Name
Secure Channel Support? The following options are available:
Assigned?
Validity Start
Expiration
Description
Results per page
(10~100)
Description n n n
Not Applicable
Yes
No
When the application type has been set to Any or Signature , Secure Channel support cannot be enabled.
The following options are available: n n n
Not Applicable
Yes
No
The DIGIPASS start time. This is the date and time when an activated (software) DIGIPASS authenticator can effectively be used for authentication and signature operations.
For more information about delayed activation, refer to the IDENTIKEY Authentication Server Product
Guide and the IDENTIKEY Authentication Server Administrator Guide.
Fields to enter a data range for the DIGIPASS expiration.
A custom text description of the DIGIPASS authenticator. This can be used to search for specific attributes of a DIGIPASS authenticator, e.g. color, company logo.
A text field to filter the number of results displayed per page.
5.6. DIGIPASS Properties
5.6.1. DIGIPASS
Table 45: DIGIPASS – DIGIPASS
Field Name
Domain Name
Description
The domain to which the DIGIPASS authenticator belongs.
Organizational Unit
DIGIPASS Type
Description
This field is read-only. The
Move
command must be used to change this.
The domain to which the DIGIPASS authenticator belongs.
This field is read-only. The
Move
command must be used to change this.
The type of DIGIPASS represented by the DIGIPASS record (e.g. DIGIPASS 300).
A custom text description of the DIGIPASS authenticator. This can be used to search for specific attributes of a DIGIPASS authenticator, e.g. color, company logo.
Assignment Status
IDENTIKEY Appliance 3.11.12 - Administrator Reference
77
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 45: DIGIPASS – DIGIPASS (continued)
Field Name
Reserve for Individual Assignment
Assigned to User
Description
When used, this option prevents the DIGIPASS from being assigned using the Auto-Assignment feature or by provisioning registration. It also prevents it from being assigned by an administrator who uses the
'Assign next available...' option in the assignment wizard.
User ID of the DIGIPASS user account that the DIGIPASS is assigned to, if it is assigned. This user account must be in the same domain as the DIGIPASS.
Assignment Date
Bind Status
Grace Period End
Valid From
Expires
Read-only. The
Assign
command must be used to change this.
The date and time when the DIGIPASS was assigned to its current user.
Read-only.
The bind status of a DIGIPASS for MobileDIGIPASS.
The date on which the grace period will expire, or did expire, for this DIGIPASS. If the date shows today's date or before, the grace period has already expired. If it is blank, there is no grace period.
Date and time when an activated (software) DIGIPASS authenticator can effectively be used for authentication and signature operations.
For more information about delayed activation, refer to the IDENTIKEY Authentication Server Product Guide and the IDENTIKEY Authentication Server Administrator Guide.
The expiration date and time of the DIGIPASS authenticator.
An expired DIGIPASS authenticator is ignored when processing authentication, administrative logon, signature validation, and provisioning requests.
Backup Virtual DIGIPASS
IDENTIKEY Appliance 3.11.12 - Administrator Reference
78
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 45: DIGIPASS – DIGIPASS (continued)
Field Name
BVDP Mode
Description
Specifies whether and how the Backup Virtual DIGIPASS feature can be used for this DIGIPASS. Note that in order for the Backup Virtual DIGIPASS feature to function, it must also be activated in the .dpx
file for the
DIGIPASS.
Normally, this field will be Default, meaning that the policy applicable to the authentication request determines the setting. This field in the DIGIPASS record is used to override the policy setting for special cases.
Options:
Enabled Until
Uses Remaining
Static Vector ID
Default
No
Yes - Permitted
Yes – Time Limited
Yes - Required
Use the setting of the effective policy.
Backup Virtual DIGIPASS is not permitted.
Backup Virtual DIGIPASS is permitted, but not mandatory.
The Enabled Until date is not applicable when using this option, but the Uses
Remaining count is.
Backup Virtual DIGIPASS is permitted, but not mandatory.
Both the Enabled Until date and the Uses Remaining count will be in effect.
Backup Virtual DIGIPASS is mandatory. This may be useful if the user may have lost the DIGIPASS, to prevent it from being used until they have found it again.
The Enabled Until date is not applicable when using this option, but the Uses
Remaining count is.
The date on which the Backup Virtual DIGIPASS feature may no longer be used, provided that the effective
Enable Backup VDP setting is Yes – Time Limited (it is ignored otherwise).
If this date is blank, it will be set automatically the first time that the user requests a Backup Virtual DIGIPASS
OTP, using the Backup Virtual DIGIPASS time limit defined in the policy.
Once this date has expired, it requires administrator intervention either to extend it or to reset it to blank for the next time that the user needs to use Backup Virtual DIGIPASS .
The remaining number of times that the Backup Virtual DIGIPASS feature may be used for this DIGIPASS.
Once this number has reached zero, Backup Virtual DIGIPASS can no longer be used with this DIGIPASS, unless the administrator increases it or resets it to blank.
If this number is blank and there is a Backup Virtual DIGIPASS Max. Uses/User defined in the policy, it will be set automatically the first time that the user requests a Backup Virtual DIGIPASS OTP, based on the Max.
Uses/User.
The presence of a value here indicates that a DIGIPASS is a software DIGIPASS capable of provisioning. Its specific value is not of use to an administrator normally. It represents a lookup key of a database record used in the provisioning process (DPSoft Parameters) that stores the static vector value.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
79
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 45: DIGIPASS – DIGIPASS (continued)
Field Name
Last Activation
Description
The date and time at which the last provisioning registration operation took place using this DIGIPASS, when an activation code was generated for it.
There is a configurable minimum interval of time between registration operations for a DIGIPASS. See the
Software DIGIPASS Provisioning Section in the IDENTIKEY Authentication Server Product Guide for more details.
Activation Locations
Activation Count
This value is reset to blank by the
Reset Activation
command.
This is typically only used for DIGIPASS for Web, to keep track of the number of different locations at which a particular user has activated it. The value is a comma-separated list of hash values, where each hash value represents one location.
There is a configurable maximum number of activation locations for a DIGIPASS. See the Software DIGIPASS
Provisioning Section in the IDENTIKEY Authentication Server Product Guide for more details.
This value is reset to blank by the
Reset Activation
command.
The total number of provisioning registration operations that have taken place using this DIGIPASS, when an activation code was generated for it. This includes registration operations for which the corresponding
Activate operation was not completed successfully.
There is a configurable maximum number of activation attempts for a DIGIPASS. See the Software DIGIPASS
Provisioning Section in the IDENTIKEY Authentication Server Product Guide for more details.
This value is reset to 0 by the
Reset Activation
command.
Update History
Created
Modified
The date and time that the DIGIPASS was created. Read-only.
The date and time that the DIGIPASS was last modified. Read-only.
5.6.2. License Information
This tab is only available, if a master activation application is linked to DIGIPASS - i.e. where DIGIPASS is a DIGIPASS license.
Table 46: DIGIPASS – License Information
Field Name
License Activation Limit
Activation Count
Description
The maximum number of activations for a DIGIPASS license.
The number of activated DIGIPASS licenses. When no DIGIPASS license has been activated, 0 is displayed as the field value.
Number of remaining allowed activations.
Activations Remaining
Activation Message
Challenge Generated At The date and time, when Activation Message 1 was generated. When Activation Message 1 was never generated, Never is displayed as field entry.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
80
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
5.6.3. Activation Information
Table 47: DIGIPASS – Activation Information (Standard Activation and Licensing)
Field Name Description
Last Activation Date / Time
Activation Locations
Activation Count
Time and date of the last DIGIPASS activation.
Location(s) from which the relevant DIGIPASS authenticator has been activated.
The number of activated DIGIPASS licenses. When no DIGIPASS license has been activated, 0 is displayed as the field value.
Table 48: DIGIPASS – Activation Information (Multi-Device Activation and Multi-Device Licensing)
Field Name Description
The fields listed below are only available if the selected DIGIPASS authenticator is a DIGIPASS instance.
License The serial number of the activated DIGIPASS license.
Device ID
Device Type
The ID of the activated DIGIPASS device.
The type of device on which the DIGIPASS license has been activated.
The following device types are possible:
Activation Confirmed At n n n n n n n n n n n n n
Hardware Device
Unknown software platform iOS
Jailbroken iOS
Android
Rooted Android
Windows Phone
BlackBerry Native
MIDP2 Platform or BlackBerry Java
Windows
Linux
Mac
RFU
The date and time, when Activation Message 2 was validated. When Activation Message 2 was never validated, Never is displayed as field entry.
5.6.4. Recent Activity
This tab displays a list of the recent authentication, signature validation, administration, and provisioning activity of a particular DIGIPASS authenticator. This tab is only available, if the administrator has the View Recent
DIGIPASS Activity privilege set.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
81
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 49: DIGIPASS – Recent Activity
Time
Code
Field Name Description
The date and time when the DIGIPASS activity was recorded.
The audit message code of the DIGIPASS activity.
Description
Category
Client
Policy ID
Reason
If you click a particular code, the respective audit message record is displayed (see
).
The textual description of the audit message.
The category of the audit message.
The location of the client component that triggered the audit message.
If you click a particular client, the properties of the respective client component is displayed (see
The identifier of the policy handling the request.
If you click a particular policy, the properties of the respective policy is displayed (see
The textual description indicating the reason for a failure.
5.7. DIGIPASS Application Tab
Table 50: DIGIPASS Application Fields
Field Name in Administration Interfaces
Description
Application Status
Application Type
This field indicates whether the application is active or not. If it is not active, it cannot be used for authentication, provisioning or signature validation.
Read-only. The
Activate Application
and
Deactivate Application
commands must be used to change this.
The type of DIGIPASS Application:
RO – Response Only
CR – Challenge/Response
SG – Signature
MA - Master Activation Application
Secure Channel Support This field indicates whether the application supports the Secure Channel feature or not by displaying either Yes or No .
Read-only.
Active
Attribute/Value list
This field can be used to deactivate an application, so that it cannot be used.
This list indicates various internal settings of the DIGIPASS Application.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
82
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 50: DIGIPASS Application Fields (continued)
Field Name in Administration Interfaces
Description
Created
Modified
The date and time that the DIGIPASS Application was created. Read-only.
The date and time that the DIGIPASS Application was last modified. Read-only.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
83
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
5.8. Audit Message
The Audit Message tab displays the details for an audit message listed in the Recent Activity tabs.
Table 51: Audit Message
Field Name Description
Date
Time
Type
Source
Category
The date at which the audit message was recorded.
The time at which the audit message was recorded.
The audit message type (code).
The audited component - i.e. the source of the audit message, e.g. "Identikey Server".
The category to which the audit message belongs.
Possible values:
Code
Description
AMID
Details
Action n n n n n
Authentication
EMV-Cap
Signature
Provisioning
Administration
The audit message code.
The description of the audit message.
The audit message identifier.
This is the intended action for a received request.
Example values: n n
Ignore
Process
The name of the DIGIPASS application.
Application
Name
Area
Audit Location
Audit Version
Back-End
Authentication
The functional area of the audited component, where the audit message was recorded.
Example: Active Directory Search
The location of the audit message source. This is typically an IP address or a host name.
The revision of the auditing format.
The back-end authentication protocol ID; value can also be None .
IDENTIKEY Appliance 3.11.12 - Administrator Reference
84
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 51: Audit Message (continued)
Field Name Description
Characteristics A space-separated list of keywords indicating characteristics of interest.
Client Location
Client Type
Command
Configuration
Details
Credentials
Example values (in case of a connection attempt): n n n
IPv6
SSL
TCP
When the client machine is not the source of the audit message, this field displays the location of the client.
The client component type.
The name of the command that triggered the relevant audit process.
Detailed information about the configuration settings.
The credentials that were entered for the connections / authentication attempt.
Example values: n n
None
Password
Data Source Location
The location of the data source, for instance the path and/or file name, if the data source is a file.
Data Source
Type
The type of the data source.
Example values: n n
File
Registry
The destination to deliver a message to (via Message Delivery Component).
Delivery Destination
Delivery Method The method used to deliver a message (via Message Delivery Component).
Description The description of the audit message.
Domain The domain name.
Downtime
DIGIPASS type
In case of an administrative command, this is usually the domain of the administrator. The domain of the targeted user is stored in Target Domain .
The duration (in minutes) of downtime of a RADIUS back end.
The type of DIGIPASS, e.g.
DIGIPASS 300 .
Epoch Certificate The certificate of the current epoch.
Epoch ID The identifier of the current epoch.
Epoch Sequence
Number
The sequence number of the audit message within the current epoch.
Epoch Version
Error Code
The revision of the secure auditing format.
The error code for the audit message.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
85
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 51: Audit Message (continued)
Field Name Description
Error Details
Error Message
The full dump of the error stack.
The string representation of the error code.
Expiration Date The expiration date related to the audit message subject, for instance the expiration date of the grace period.
Fields Details
From Location
A comma-separated list of fields returned by the query or All Fields if all fields are returned.
The source location for a particular process, for instance when something is moved.
Info Message
Input Details
Local Authentication
The message returned by an external component, e.g.
MDC .
Detailed information about the request parameters and/or attributes.
Indicates if local authentication was performed.
Mobile Number The mobile phone number to send a message to via Message Delivery Component (MDC).
Object The name of an object that is related to an audit query or command.
Offline Data
Details
The details of the offline data for the relevant audit message.
Offline State Data The offline state data for the relevant audit message.
Operation
Outcome
Output Details
Password Protocol
The operation that was attempted or processed when the audit message was recorded.
The outcome of an attempt of RADIUS authentication.
Example values: n n n
Challenge
Failure
Success
Detailed information about the response parameters and/or attributes.
The protocol used for password encoding.
Example values:
Policy ID
Protocol n n n n n
CHAP
EAP-MD5
MS-CHAP1
MS-CHAP2
PAP
The unique identifier of the policy handling the request.
The identifier of the communication protocol used.
Quota The value of a quota related to the audit message subject, e.g. BVDP uses remaining .
RADIUS Input Octets
The Acct-Input-Octets attribute from the RADIUS accounting packet, i.e. the number of bytes received for an account input request during the RADIUS accounting session.
RADIUS Output
Octets
RADIUS Profile
The Acct-Output-Octets attribute from the RADIUS accounting packet, i.e. the number of bytes sent for an account output request during the RADIUS accounting session.
The RADIUS profile used for setting up IDENTIKEY Authentication Server and for the RADIUS back end.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
86
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 51: Audit Message (continued)
Field Name Description
RADIUS Status
Type
Reason
Request ID
Request Type
The Acct-Status-Type attribute from the RADIUS accounting packet. Typically indicates the beginning (Start) or the end (Stop) of an accounting session.
A short phrase indicating the reason for a failure.
The request identifier, e.g. the RADIUS packet ID.
The type of packet.
Example values (in case of RADIUS protocol): n n
Access-Request
Access-Accept
Serial Number The serial number of the DIGIPASS authenticator.
Server Location The location of the server, typically an IP address or host name.
Session ID
Session Time
The session identifier.
The duration (in seconds) of the session.
Signature The cryptographic signature of the audit message.
Target Domain This is the domain of the user targeted by an administrative command.
Target User ID This is the user ID of the user targeted by an administrative command.
Task Description The description of the task.
The time that was required to complete the task.
Task Execution
Time
Task ID
Task Result
The task identifier.
The result of the task.
To Location
User ID
The destination location for a particular process, for instance when something is moved.
When the user ID refers to an IDENTIKEY Authentication Server user account, this is the exact user ID.
User Link
User Location
Valid From
In case of an administrative command, this is usually an administrator. The targeted user is stored in Target User ID .
The user ID of the user account linked to this user account.
The location (IP address) of the user's client device, e.g. the RADIUS calling-station-ID or the HTTP browser/client address
The date and time the DIGIPASS authenticator becomes active and can effectively be used, if set or modified by the respective command (delayed activation).
5.9. Policy Properties
Note
Changes to policy settings will not take effect immediately on all IDENTIKEY Authentication Server instances unless replication is used to synchronize the IDENTIKEY Authentication Server instances. Where replication is not used, changes to policy settings will take effect when each IDENTIKEY Authentication Server is restarted, once
IDENTIKEY Appliance 3.11.12 - Administrator Reference
87
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings the policy change is available to it in its data store. Alternatively if there is no restart, the cache of policy settings will refresh from the data store approximately every 15 minutes.
Table 52: Policy Properties - Policy
Field Name Description
Description
Inherits from Policy
This description can be entered to record the purpose of the policy.
Contains the name of the policy from which settings will be inherited, referred to as the parent policy.
Settings are inherited individually, depending on the value in the policy field. They inherit the parent policy value in the following cases:
Local Authentication n n n n
Choice lists/radio buttons – if the selected value is Default
Text fields – if the field is blank
Numeric fields – if the field is blank (not 0)
List fields – if the list is empty
The Show Effective Policy Settings button can be used to display the result of inheriting settings combined with settings of the current policy.
Specifies whether authentication requests using the policy will be handled by the using Local Authentication. For more information about local authentication and back-end authentication, refer to the
IDENTIKEY Authentication Server Product Guide , Section " Authenticating Users".
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 authenticator that meets the restrictions. For example, if the policy requires a DIGIPASS300, but the user has a DIGIPASS 700, the user cannot use DIGIPASS authentication under that policy.
This setting also affects the provisioning registration process. For more information, refer to the
IDENTIKEY Authentication Server Product Guide , Section "Software DIGIPASS Provisioning".
Possible values: n n n n n
Default . Use the setting of the parent policy.
None . IDENTIKEY Authentication Server will not use local authentication under this policy.
They may be handled using back-end authentication or not handled at all by IDENTIKEY
Authentication Server.
Digipass Only . IDENTIKEY Authentication Server will always use local authentication under this policy, using DIGIPASS authentication. If DIGIPASS authentication is not possible, the user cannot log in. Back-end authentication may also be used.
DIGIPASS/Password during Grace Period . IDENTIKEY Authentication Server will always use local authentication under this policy; possibly using DIGIPASS Authentication for Windows Logon if applicable. The static password can only be used within a (configurable) grace period until a DIGIPASS authenticator is used the first time. Back-end authentication may also be used.
DIGIPASS or Password . This authentication mode allows users to permanently use their static password or their DIGIPASS authenticator, even after the grace period has expired and/or they have previously already used their authenticator for authentication. Use of this authentication mode is subject to licensing.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
88
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 52: Policy Properties - Policy (continued)
Field Name Description
Back-End Authentication Specifies whether authentication requests using the policy will be handled by the IDENTIKEY Authentication Server using back-end authentication. For more information about local authentication and backend authentication, refer to the IDENTIKEY Authentication Server Product Guide , Section "Authenticating users".
Back-End Protocol
Created
Modified
This setting also affects the provisioning registration process. For more information, refer to the
IDENTIKEY Authentication Server Product Guide , Section "Software DIGIPASS Provisioning".
Possible values: n
Default . Use the setting of the parent policy.
n
None . Back-end authentication will not be used.
n
If Needed . IDENTIKEY Appliance will utilize back-end authentication but only in certain cases: n n n n n n
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, during the grace period, or if the local authentication mode is set to DIGIPASS or Password .
Provisioning registration n
Always . IDENTIKEY Appliancewill use back-end authentication for every authentication and provisioning registration request.
This setting is required, if you want to use offline authentication for DIGIPASS Authentication for Windows Logon.
To enforce static password verification during offline authentications via DIGIPASS Authentication for Windows Logon, you need to disable Stored Password Proxy and set Back-End
Authentication to Always .
Specifies the protocol to be used for Back-End Authentication.
If you have your own Back-End Authentication engines, they will have protocol names to identify them.
The name for the required engine must be defined in the back-end protocol for the policy.
The following standard authentication options are available: n n n n n
Windows (this is only available when IDENTIKEY Appliance runs on Windows)
RADIUS
NetIQ eDirectory
Microsoft Active Directory
IBM Security Directory Server
The date and time that the policy was created. Read-only.
The date and time that the policy was last modified. Read-only.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
89
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 53: Policy Properties - User
Field Name Description
Dynamic User Registration Specifies whether the Dynamic User Registration (DUR) feature is enabled for the policy. If this feature is used, when the IDENTIKEY Appliance receives an authentication request for a user for the first time and back-end authentication is successful, it will create a DIGIPASS user account automatically. If DUR is used together with Auto-Assignment, a DIGIPASS will be assigned to the new user account immediately.
User Info Synchronization
This setting also determines whether the provisioning registration process is allowed to perform DUR or not.
Specifies whether to set user information when a DIGIPASS user account is created using Dynamic User
Registration (DUR) with an LDAP back-end server, by synchronizing the data from the LDAP back-end server to the respective DIGIPASS user account data fields (DUR user information synchronization).
Possible values:
Password Autolearn
Stored Password Proxy n n n
Default . Use the setting of the parent policy.
No . Do not synchronize user information from LDAP back-end server.
Yes . Synchronize user information from LDAP back-end server.
For more information about DUR user information synchronization, refer to the IDENTIKEY Authentication Server Product Guide .
Specifies whether the Password Autolearn feature is enabled for the policy. This feature enables
IDENTIKEY Appliance to update the password stored in the DIGIPASS user account when back-end authentication is successful.
This setting also determines whether the provisioning registration process will update the password after successful back-end authentication or not.
Specifies whether the stored password proxy feature is enabled for the policy. This feature can be used together with the back-end authentication setting and the Password Autolearn feature. With this combination, even though a back-end authentication check is done during every logon, it is done using the password stored in the DIGIPASS user account. Therefore the user does not have to enter it during the logon, unless it has changed in the back-end system. This mode of operation is referred to as Password
Replacement.
To enforce static password verification during offline authentications via DIGIPASS Authentication for
Windows Logon, you need to disable Stored Password Proxy and set Back-End Authentication to
Always .
Account Lockout
User Lock Threshold Specifies the number of invalid logon attempts that are allowed before a DIGIPASS user account is locked. For example, if User Lock Threshold is 3 , the account will become locked on the third failed logon attempt. Unlocking the account requires administrator action or user auto-unlock enabled.
Note that not all kinds of logon failure will result in locking. For example, if the user ID is incorrect or the account is disabled, the failure would not count for the lock threshold. Locking is used mainly for incorrect OTPs and static passwords.
The locking mechanism is also used for provisioning and signature validation.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
90
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 53: Policy Properties - User (continued)
Field Name Description
Minimum Lock Duration The time span a locked DIGIPASS user account remains locked before a user can try to authenticate again and unlock it using user auto-unlock. The value is given in minutes.
Lock Duration Multiplier
Maximum Unlock Tries
Applies only if user auto-unlock is enabled, effectively by setting Maximum Unlock Tries .
Possible values: 0 – 99999
The multiplier factor to increase the lock duration (initial value specified by Minimum Lock Duration ) after each unsuccessful authentication. The value is given in percent. For example, a value of 200 effectively doubles the lock duration after each unsuccessful authentication.
Applies only if user auto-unlock is enabled, effectively by setting Maximum Unlock Tries .
Possible values: 100 – 500
The maximum number of attempts to unlock a locked DIGIPASS user account during authentication
(user auto-unlock) before it is permanently locked. A locked DIGIPASS user account with no unlock attempts left, can only be unlocked manually by an administrator.
Setting this value to 0 effectively disables user auto-unlock.
Possible values: 0 – 999
For more information about user auto-unlock, refer to the IDENTIKEY Authentication Server Product
Guide .
Max Days Between Authentications Specifies the number of days a DIGIPASS user account can remain inactive before it is suspended. If the account has been suspended the user will not be able to log on.
The user will be notified during authentication that the DIGIPASS user account has been suspended.
Account Constraints
Default Domain
Accepted Domain
Local Admin Users
The default domain in which IDENTIKEY Authentication Server should look for and create a DIGIPASS user account, if a domain is not specified by the user credentials. For more information about the process of resolving the user ID and domain name, refer to the IDENTIKEY Authentication Server Product
Guide , Section "User ID and Domain Resolution".
Only users from this domain will be accepted; all others will be refused.
Indicate access allowed by the user to non-administrative tasks, if the user has administrative privileges.
Possible values: n n n n
Default . Use the setting of the parent policy.
Accept . Allow this user to proceed through the transaction
Reject . Do not allow this user to proceed through the transaction
Required . This user MUST have administrative privileges to proceed with processing.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
91
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 53: Policy Properties - User (continued)
Field Name Description
Windows Group Check Specifies whether and how the Windows Group Check feature is to be used. This feature is typically used for a staged DIGIPASS deployment when the Auto-Assignment method is used. It can also be used when only some users are required to use a DIGIPASS authenticator or when only some users will be permitted access and they have to use a DIGIPASS authenticator.
Windows Group List
Possible values: n n n n n
Default . Use the setting of the parent policy.
No check . Do not use windows group check.
Pass requests for users not in listed groups back to host system . Use windows group check so that any users who are not in one of the listed groups are ignored by IDENTIKEY
Authentication Server. Use of this setting for provisioning or signature validation will have the same effect as Reject requests for users not in listed group .
Reject requests for users not in listed group . Use windows group check so that any users who are not in one of the listed groups are rejected by IDENTIKEY Authentication Server.
Use only back-end authentication for users not in listed groups . Use back-end authentication only for any users who are not in one of the listed groups. Use of this setting for provisioning or signature validation will have the same effect as Reject requests for users not in listed group .
This lists the names of the Windows groups to be checked according to the Windows Group Check setting. There are some important limitations of this check: n n n n
Certain built-in Active Directory groups such as Domain Users and Everyone will not be checked. The check is intended to be used with a new group created specifically for this purpose.
Nested group membership will not be detected by the check.
There is no domain qualifier for a group. The named group must be created in each domain where user accounts exist that need to be added to the group.
A local machine group can be used also.
For groups to appear for an Active Directory back end, the Active Directory back end must exist in
IDENTIKEY Appliance.
RADIUS Attributes
Reply RADIUS Attributes Specifies whether to return RADIUS attributes from a user account when it returns an Access-Accept.
Possible values: n n n
Default . Use the setting of the parent policy.
No . Do not return RADIUS attributes
Yes . Return the RADIUS attributes in the groups listed below
RADIUS Attribute Group List Comma-separated list of RADIUS attribute groups. Only attributes belonging to the listed groups will be returned via this policy.
Static Password
These options allow you to define password complexity rules for the static password of the associated user.
Minimum Password Length Set the minimum length required for the static password. The maximum length is 16 characters.
Possible values: 0 – 9999
IDENTIKEY Appliance 3.11.12 - Administrator Reference
92
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 53: Policy Properties - User (continued)
Field Name Description
Minimum # Lowercase Characters Specifies the minimum number of lowercase characters required in the password.
Possible values: 0 – 9999
Minimum # UPPERCASE Characters Specifies the minimum number of uppercase characters required in the password.
Minimum # Numerical Digits
Possible values: 0 – 9999
Specifies the minimum number of numerical digits required in the password.
Minimum # Special Characters
Possible values: 0 – 9999
Specifies the minimum number of special characters required in the password, in this context, these are non-alphanumeric characters on the keyboard (excluding numbers or letters of the alphabet).
Different From Last # Passwords
Not Based on User ID
Possible values: 0 – 9999
Specifies how many different passwords must be used before a previously used password can be used again.
Possible values: 0 – 24
Specifies whether the password is allowed to contain all or parts of the user ID.
Possible values: n n n
Default . Use the setting of the parent policy.
No . Disables this option.
Yes . Enables this option.
Table 54: Policy Properties – DIGIPASS
Field Name Description
DIGIPASS Assignment
IDENTIKEY Appliance 3.11.12 - Administrator Reference
93
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 54: Policy Properties – DIGIPASS (continued)
Field Name Description
Assignment Mode Specifies the method of automated DIGIPASS Assignment that will be used for this policy, if any. There are two methods, Auto-Assignment and Self-Assignment.
Auto-Assignment is used in conjunction with Dynamic User Registration (DUR). When DUR occurs, the next available DIGIPASS is assigned to the new DIGIPASS user account. A grace period is set for the
DIGIPASS according to the Grace Period setting in the policy.
Self-Assignment is typically used with DUR also, but if the DIGIPASS user account is created first by the administrator, DUR is not necessary. In the Self-Assignment mode, a user is able to assign themselves a DIGIPASS by entering the serial number, a valid OTP from the DIGIPASS and their static password. There is no grace period associated with Self-Assignment, because the user has to use the
DIGIPASS to perform Self-Assignment.
In both cases, any applicable DIGIPASS restrictions apply to the policy. For example, it will not be permitted to self-assign a DIGIPASS 300 if the policy restricts the types to DIGIPASS GO 3 and
DIGIPASS GO 1. In addition, if the user already has a DIGIPASS assigned that meets the policy restrictions, they will not be able to self-assign another DIGIPASS.
This setting is not applicable to provisioning or signature validation.
Possible values:
Grace Period (days)
Serial No. Separator n n n n
Default . Use the setting of the parent policy.
Auto-Assignment . Use the Auto-Assignment method.
Self-Assignment . Use the Self-Assignment method.
Neither . Do not use either method of automated assignment.
This is the default period (in days) between Auto-Assignment of a DIGIPASS authenticator and the date for users to start using their authenticator to log in (if applicable).
The grace period expires the first time an OTP is used to log in (if it has not been set manually to expire prior to that). After the grace period has expired, depending on the Local Authentication settings in the relevant policy, users can then either continue to use both their static password or their
DIGIPASS authenticator ( DIGIPASS or Password ), or must only use the authenticator ( DIGIPASS/Password during Grace Period or Digipass Only ) to log in.
This setting does not affect manual assignment by an administrator or provisioning.
The character (or short sequence of characters) that will be included at the end of the DIGIPASS Serial
Number during a Self-Assignment login. It allows the to easily recognize that a Self-Assignment attempt is being made and extract the Serial Number from the credentials.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
94
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 54: Policy Properties – DIGIPASS (continued)
Field Name Description
Search Upwards in Org. Unit Hierarchy This controls the search scope for an available DIGIPASS for Auto-Assignment or Provisioning Registration, or for a specific DIGIPASS for Self-Assignment.
This setting does not affect manual assignment by an administrator.
Possible values: n n n
Default . Use the setting of the parent policy.
No . The search scope is only the organizational unit in which the user account belongs. If the user does not belong to an organizational unit, the search will look for DIGIPASS that also do not belong to an organizational unit.
Yes . The search will start in the user account's organizational unit, but if necessary it will then move upwards through the organizational unit hierarchy until it reaches the top. If Active Directory is used as the data store, the search will include the DIGIPASS-Pool container.
The length of time in days since assignment until a DIGIPASS expires Expiration Period (days)
Delayed Activation
Delay Period (hours) The delayed activation period (in hours), i.e. the time span after activation until an activated (software)
DIGIPASS authenticator can effectively be used for authentication and signature operations.
Possible values: 0 – 9999
Notify user when activation process starts
For more information about delayed activation, refer to the IDENTIKEY Authentication Server Product
Guide and the IDENTIKEY Authentication Server Administrator Guide .
Determines whether a notification should be sent to the user when a DIGIPASS activation is delayed
(delayed activation). The notification messages are scheduled to be sent via Message Delivery Component (MDC) using the delivery method specified by Delivery Method .
Notify user when activation completes Determines whether a notification should be sent to the user when a delayed DIGIPASS activation completes (delayed activation). The notification messages are scheduled to be sent via Message Delivery
Component (MDC) using the delivery method specified by Delivery Method .
Delivery Method Specifies the default delivery method when sending notifications for delayed activation. The notification messages are scheduled to be sent via Message Delivery Component (MDC) and use message templates specified in the global server configuration (see
5.15.2. MDC Message Settings ).
Possible values: n n n n
Default . Use the setting of the parent policy.
Email . Deliver the notification message via email. The DIGIPASS user account must have a configured email address.
SMS . Deliver the notification message via SMS. The DIGIPASS user account must have a configured mobile phone number.
Voice . Deliver the notification message via voice channel (ie. dictated over a phone line). The
DIGIPASS user account must have a configured mobile phone number.
Applicable DIGIPASS
Application Names The policy can specify a restriction on which DIGIPASS Applications may be used when it is effective. If the list is empty, there is no restriction. If there are one or more entries, they will indicate the application names that are permitted.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
95
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 54: Policy Properties – DIGIPASS (continued)
Field Name Description
Application Type The policy can restrict which DIGIPASS Application type (e.g. Response Only, Challenge/Response) may be used when it is effective.
Secure Channel Support
Possible values: n n n n n n
Default . Use the setting of the parent policy.
No Restriction . DIGIPASS application type is not restricted.
Response Only . Only DIGIPASS applications of type RO (Response-Only) or MM (Multi-
Mode) may be used.
Challenge/Response . Only DIGIPASS applications of type CR (Challenge/Response) or MM
(Multi-Mode) may be used.
Signature . Only DIGIPASS applications of type SG (Signature) or MM (Multi-Mode) may be used.
Multi-Mode . Only DIGIPASS applications of type MM (Multi-Mode) may be used.
Indicates if the DIGIPASS application should support Secure Channel operations.
Possible values:
DIGIPASS Type n n n n
Default . Use the setting of the parent policy.
No . DIGIPASS applications that support Secure Channel are not considered.
Yes – Permitted . DIGIPASS applications that support Secure Channel are not required, but are permitted.
Yes – Required . Requires a DIGIPASS application that supports Secure Channel.
The policy can specify a restriction on which DIGIPASS Types may be used when it is effective. If the list is empty, there is no restriction. If there are one or more entries, they will indicate the DIGIPASS
Types that are permitted.
Allow PIN change Specifies whether DIGIPASS users will be allowed to change their server PIN during authentication requests to which the current policy applies. Normally this setting is enabled, but it can be used to prevent PIN changes if required.
Multiple DIGIPASS App Validation Mode Specifies whether IDENTIKEY Authentication Server should authenticate a user if it detects multiple assigned DIGIPASS applications.
If this option is set to Single DIGIPASS , then users with multiple DIGIPASS applications assigned cannot log in.
If there are any policy restrictions on Application Type, then IDENTIKEY Authentication Server will only detect applications of the restricted type. For more information, refer to the IDENTIKEY Authentication
Server Product Guide , Section " Multiple DIGIPASS or DIGIPASS Applications".
IDENTIKEY Appliance 3.11.12 - Administrator Reference
96
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 55: Challenge Policy Fields
Field Name
1-Step Challenge/Response – Permitted
1-Step Challenge/Response – Challenge Length
1-Step Challenge/Response – Add Check Digit
2-Step Challenge/Response – Request Method
Description
Controls whether 1-step Challenge/Response logins will be enabled for the current policy and, if so, where the challenge should originate.
In order to enable 1-step Challenge/Response, you also need to set the Challenge Check Mode (see below).
Note that 1-step Challenge/Response is not applicable in a RADIUS environment.
Possible values: n n n n
Default . Use the setting of the parent policy.
No . 1-step Challenge/Response may not be used.
Yes – Server Challenge . 1-step Challenge/Response may be used, if the IDENTIKEY Authentication Server instance, which verifies the response also generated the challenge.
Yes – Any Challenge . 1-step Challenge/Response may be used with any random challenge.
Specifies the length of the challenge (excluding a check digit) which should be generated for 1-step Challenge/Response logins.
A check digit may be added to the generated challenge. This allows the
DIGIPASS to identify invalid Challenges more quickly.
The method by which a user has to request a 2-step Challenge/Response login.
This is the only mode of Challenge/Response available in a RADIUS environment.
The request is made in the password field during login. The request will fail if the user does not have a Challenge/Response-capable
DIGIPASS authenticator assigned. This includes DIGIPASS Applications of
Type CR, SG and MM.
Possible values: n n n n n n n n
Default . Use the setting of the parent policy.
None . Do not use 2-step Challenge/Response
Keyword . Use the Request Keyword, with or without another item. This is permitted to be blank.
Keyword Only . Only the keyword will be accepted.
Password . Use the static password.
KeywordPassword . Use the Request Keyword followed by the static password. No separator characters or whitespace should be between them.
PasswordKeyword . Use the static password followed by the
Request Keyword. No separator characters or whitespace should be between them.
KeywordPIN . Use the request keyword followed by the PIN.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
97
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 55: Challenge Policy Fields (continued)
Field Name
2-Step Challenge/Response – Request Keyword
Description
Defines the keyword that a user must enter to request a 2-step Challenge/Response login, if a method using a keyword is selected in the
Request Method.
This can be left blank.
Table 56: Secure Channel Policy Fields
Field Name
Secure Channel Support
Description
Indicates if the DIGIPASS application should support Secure Channel operations.
Possible values: n n n n
Default . Use the setting of the parent policy.
No . DIGIPASS applications that support Secure Channel are not considered.
Yes – Permitted . DIGIPASS applications that support Secure Channel are not required, but are permitted.
Yes – Required . Requires a DIGIPASS application that supports Secure Channel.
The number of days before the first activation message (Activation Message 1) will expire.
Activation Message Validity Period
Message Signing
Allow Custom Request Body
Min App Version
If true, all Secure Channel policy settings can be overwritten by providing a valid request body attribute in the request.
Minimum application version; the application version required to parse the request message.
Possible values: 0 3
1-Step Challenge/Response
Require PIN
Template Number
Font Index
If true, the device must perform PIN verification before generating the response.
Selects the template in the device that specifies the layout of a page with challenge transaction data.
Possible values: 0 15
Selects the font table in case multiple font tables are implemented in the device.
Possible values: 0 3
Signature Transaction
Require PIN
Template Number
Font Index
Show Response
Show Warning
If true, the device must perform PIN verification before generating the response.
Selects the template in the device which specifies the layout of a page with signature transaction data.
Possible values: 0 15
Selects the font table in case multiple font tables are implemented in the device.
Possible values: 0 3
If true, the response will be shown on the device.
If true, a pre-loaded warning will be shown on the device.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
98
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Note
The Secure Channel policy fields are only displayed for deployments based on an ODBC storage.
Table 57: Virtual DIGIPASS Policy Fields
Setting Field Name
Virtual DIGIPASS Delivery Method
MDC profile
Description
The method used to deliver the Virtual DIGIPASS.
Possible values: n n n n
Default . Use the setting of the parent policy.
Email . Deliver the one-time password via email. The
DIGIPASS user account must have a configured email address.
SMS . Deliver the one-time password via SMS. The DIGIPASS user account must have a configured mobile phone number.
Voice . Deliver the one-time password via voice channel (ie.
dictated over a phone line). The DIGIPASS user account must have a configured mobile phone number.
This field also allows you to specify a combination of delivery methods, namely: n n n
Email and SMS
SMS and Voice
Email and Voice
The MDC profile whose settings should be used for this delivery method. An MDC profile defines specific group of settings for a particular delivery method. If there is no specified MDC profile in this field, then the highest-ranked, enabled, and available MDC profile for the specified delivery method/s will be used.
The MDC profile name should not be confused with the profile's display name. The display name is simply an ad-hoc field used primarily to describe and further identify the profile. The MDC profile name is the name that appears in the Profile column of the MDC Configuration Utility.
The MDC profile name is non-unique; as such, multiple MDC profiles with the same name may exist for this delivery method. The highestranked, enabled, and available MDC profile with the specified MDC profile name will be used.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
99
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 57: Virtual DIGIPASS Policy Fields (continued)
Setting Field Name
Primary Virtual DIGIPASS Request Method
Request Keyword
Description
The method by which a User has to request a Primary Virtual DIGIPASS login.
The request is made in the password field during login. The request will be ignored if the user does not have a Primary Virtual DIGIPASS assigned.
Possible values: n n n n n n n
Default . Use the setting of the parent policy.
None . Do not use Primary Virtual DIGIPASS.
Keyword . Use the Request Keyword, with or without another item. This is permitted to be blank.
Keyword Only . Only the keyword will be accepted.
Password . Use the static password.
KeywordPassword . Use the Request Keyword followed by the static password. No separator characters or whitespace should be between them.
PasswordKeyword . Use the static password followed by the
Request Keyword. No separator characters or whitespace should be between them.
Defines the Keyword that a user must enter to request a Primary Virtual
DIGIPASS login, if a method using a Keyword is selected in the Request
Method. This is permitted to be blank.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
100
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 57: Virtual DIGIPASS Policy Fields (continued)
Setting Field Name
Backup Virtual DIGIPASS BVDP Mode
Time Limit (days)
Max Uses/User
Description
Specifies whether and how the Backup Virtual DIGIPASS feature can be used when this policy is effective. Note that in order for the Backup Virtual DIGIPASS feature to function, it must also be activated in the .dpx
file for the DIGIPASS.
Possible values: n n n n n
Default . Use the setting of the parent policy.
No . Backup Virtual DIGIPASS is not permitted.
Yes - Permitted . Backup Virtual DIGIPASS is permitted, but not mandatory. The Time Limit is not applicable when using this option, but the Max. Uses/User limit is.
Yes – Time Limited . Backup Virtual DIGIPASS is permitted, but not mandatory. Both the Time Limit and the Max.
Uses/User limit will be in effect.
Yes - Required . Backup Virtual DIGIPASS is mandatory. The
Time Limit is not applicable when using this option, but the
Max. Uses/User limit is.
When the Enable Backup VDP setting is Yes – Time Limited , the Time
Limit setting indicates the number of days for which the Backup Virtual
DIGIPASS feature may be used by a User, once they start using it.
The Backup Virtual DIGIPASS Enabled Until setting in the DIGIPASS record will be set automatically the first time that the user requests a
Backup Virtual DIGIPASS OTP, using the Time Limit defined in the policy. Once this date has expired, it requires administrator intervention either to extend it or to reset it to blank for the next time that the user needs to use a Backup Virtual DIGIPASS.
Note that if a user has more than one DIGIPASS capable of Backup Virtual DIGIPASS, they will have a separate limit for each one.
The maximum number of uses of the Backup Virtual DIGIPASS feature permitted for each user, if they do not have a specific limit set for them.
If the Backup Virtual DIGIPASS Uses Remaining in the DIGIPASS record is blank and there is a Max. Uses/User limit defined in the policy, the
Uses Remaining will be set automatically the first time that the user requests a Backup Virtual DIGIPASS OTP.
Once the Uses Remaining has reached zero, Backup Virtual DIGIPASS can no longer be used with this DIGIPASS, unless the administrator increases it or resets it to blank.
Note that if a user has more than one DIGIPASS capable of Backup Virtual DIGIPASS, they will have a separate limit for each one.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
101
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 57: Virtual DIGIPASS Policy Fields (continued)
Setting Field Name
Request Method
Request Keyword
Description
The method by which a user has to request a Backup Virtual DIGIPASS login.
The request is made in the password field during login. The request will be ignored if the user does not have a DIGIPASS authenticator assigned that is activated for the Backup Virtual DIGIPASS feature, or if any other policy or DIGIPASS settings do not permit Backup Virtual DIGIPASS use.
Possible values: n n n n n n
Default . Use the setting of the parent policy.
None . Do not use Backup Virtual DIGIPASS.
Keyword . Use the request keyword. This is permitted to be blank.
Password . Use the static password.
KeywordPassword . Use the request keyword followed by the static password. No separator characters or whitespace should be between them.
PasswordKeyword . Use the static password followed by the request keyword. No separator characters or whitespace should be between them.
Defines the keyword that a user must enter to request a Backup Virtual
DIGIPASS login, if a method using a keyword is selected in Request
Method . This is permitted to be blank.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
102
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 57: Virtual DIGIPASS Policy Fields (continued)
Setting Field Name
Virtual Signature Virtual Signature Mode
Delivery Method
MDC profile
Description
Specifies whether or not to allow the use of Virtual Signatures.
n n n
Default . Use the setting of the parent policy.
No . Disables this option.
Yes . Enables this option.
The method used to deliver the Virtual Signature.
Possible values: n n n n
Default . Use the setting of the parent policy.
Email . Deliver the one-time password via email. The
DIGIPASS user account must have a configured email address.
SMS . Deliver the one-time password via SMS. The DIGIPASS user account must have a configured mobile phone number.
Voice . Deliver the one-time password via voice channel (ie.
dictated over a phone line). The DIGIPASS user account must have a configured mobile phone number.
This field also allows you to specify a combination of delivery methods, namely: n n n
Email and SMS
SMS and Voice
Email and Voice
The MDC profile whose settings should be used for this delivery method. An MDC profile defines specific group of settings for a particular delivery method. If there is no specified MDC profile in this field, then the highest-ranked, enabled, and available MDC profile for the specified delivery method/s will be used.
The MDC profile name should not be confused with the profile's display name. The display name is simply an ad-hoc field used primarily to describe and further identify the profile. The MDC profile name is the name that appears in the Profile column of the MDC Configuration Utility.
The MDC profile name is non-unique; as such, multiple MDC profiles with the same name may exist for this delivery method. The highestranked, enabled, and available MDC profile with the specified MDC profile name will be used.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
103
Signature Time Window
Initial Time Window
Event Window
Identification Threshold
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 58: DIGIPASS Control Parameters
Field Name
Identification Time Window
Description
Controls the maximum number of time steps' variation allowable between a DIGIPASS and the host system during login. This only applies to time-based DIGIPASS Applications when verifying a one-time password.
The Dynamic Time Window option may be used to allow more variation according to the length of time since the last successful login.
If this setting is not specified at all, there is an inbuilt default value of 20.
Controls the maximum number of time steps' variation allowable between a DIGIPASS and the host system during digital signature verification. This only applies to time-based
DIGIPASS Applications when validating a signature, but even then it may be used or not according to the online signature level setting.
The Dynamic Time Window option may be used to allow more variation according to the length of time since the last successful login.
If this setting is not specified at all, there is an inbuilt default value of 24.
Controls the maximum allowed time variation allowable between a DIGIPASS and the host system, the first time that the DIGIPASS is used. The time is specified in hours. This
Initial Time Window is also used directly after a Reset Application operation, which can be used if it appears that the internal clock in the DIGIPASS has drifted too much since the last successful login.
This only applies to time-based DIGIPASS Applications when verifying a one-time password.
In either case, after the first successful login, the initial time window is no longer active.
If this setting is not specified at all, there is an inbuilt default value of 6.
Controls the maximum number of events' variation allowable between a DIGIPASS application and the host system during login. This only applies to event-based DIGIPASS
Applications. It always applies when verifying a one-time password but for signature validation, it depends on the online signature level setting whether the event window is used or not.
If this setting is not specified at all, there is an inbuilt default value of 20.
Specifies the number of consecutive failed authentication attempts allowed before the
DIGIPASS Application is locked from future authentication attempts. Once the DIGIPASS
Application is locked, the Reset Appl Lock command is required to unlock it for further authentication.
This locking mechanism is separate from the User Lock Threshold and is normally not necessary. It only applies when a single DIGIPASS Application can be used for a login, either because the user only has one DIGIPASS with one Application, or because the policy restrictions narrow the list down to one DIGIPASS Application. If policy restrictions are used in this way, the Identification Threshold can be used to lock a user out of one kind of login (e.g. a VPN) while still permitting them to use another kind (e.g. a web application).
If this setting is not specified at all, this feature is not used.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
104
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 58: DIGIPASS Control Parameters (continued)
Signature Threshold
Field Name Description
Specifies the number of consecutive failed Signature validation attempts allowed before the DIGIPASS Application is set to be locked from future signature validation attempts.
Once the DIGIPASS Application is locked, the Reset Appl Lock command is required to unlock it for further signature validation.
This locking mechanism is separate from the User Lock Threshold and is normally not necessary. It only applies when a single DIGIPASS Application can be used for a signature validation, either because the user only has one DIGIPASS with one signature-capable application, or because the policy restrictions narrow the list down to one DIGIPASS
Application. If policy restrictions are used in this way, the Signature Threshold can be used to lock a user out of one kind of signature validation while still permitting them to use another kind.
Max. Days Since Last Use
Challenge Check Mode
If this setting is not specified at all, this feature is not used.
This setting specifies the maximum number of days for which a DIGIPASS Application can go unused for authentication or signature validation. After this limit, authentication and signature validation will be rejected until an administrator performs a Reset Application operation.
If this setting is not specified at all, this feature is not used.
This setting is for advanced control over time-based Challenge/Response authentication.
The value 1 should be used for standard RADIUS Challenge/Response. This is the builtin default value if the setting is not specified at all.
Possible values: n n n n n
0 . No check is made. This is necessary for 1-step Challenge/Response.
1 . The challenge presented for verification must be the last one that was generated specifically for that DIGIPASS. This is the normal mode of operation in
2-step Challenge/Response.
2 . The challenge presented for verification is ignored; the last one that was generated specifically for that DIGIPASS is used.
3 . Only one verification is permitted per time step. This option only applies to time-based Challenge/Response. This is a method of avoiding a potential replay of a captured response if the same challenge comes up again in the same time step.
4 . If the same challenge and response are presented for verification twice in a row during the same time step, they are rejected. This is an advanced method of avoiding a potential replay of a capture Challenge/Response.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
105
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 58: DIGIPASS Control Parameters (continued)
Field Name
Online Signature Level
Description
This setting is for advanced control of Signature validation.
The value 0 can be used for DIGIPASS Application that are neither time- nor eventbased. This is the built-in default value if the setting is not specified at all.
Possible values: n
0 . The signature is validated in offline mode. This is useful when the signatures may not be validated in the same sequence as they were generated by the user. It is also useful when there may be some delay after the signature is generated by the user, before the signature is validated.
For time-based DIGIPASS Applications: This mode is typically used with a large time step. When this mode is used, no clock synchronization occurs between the DIGIPASS and the IDENTIKEY Appliance. The IDENTIKEY Appliance will not reject an older signature than the most recently validated signature, provided it is still within the Signature Time Window.
For event- based DIGIPASS Applications: When this mode is used, the
IDENTIKEY Appliance will not reject an older signature than the most recently validated signature, provided it is still within the Event Window.
n
1 . The signature is validated in online mode. This is useful when the signatures are expected or required to be validated immediately after they are generated.
For time-based DIGIPASS Applications: This mode is typically used with a small time step. When this mode is used, clock synchronization occurs between the DIGIPASS and the IDENTIKEY Appliance. The IDENTIKEY Appliance will reject an older signature than the most recently validated signature.
A newer signature must be within the Signature Time Window.
This mode will allow more than one signature to be validated in the same time step, provided that the same exact signature is not repeated twice in a row.
For event- based DIGIPASS Applications: When this mode is used, the
IDENTIKEY Appliance will reject an older signature than the most recently validated signature. A newer signature must be within the Event Window.
n
2 . The signature is validated in strict online mode. This is useful for timebased signatures when you want to prevent more than one signature from the same time step from being validated. Otherwise, this mode is the same as online mode.
n
3 . The signature is validated using the Deferred Event Count. This mode only applies to event-based signatures. For each signature validation request, the
Deferred Event Count must be supplied as a parameter.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
106
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 59: Offline Authentication
Field Name
Offline Authentication Enabled
Offline Time Window (days)
Offline Event Window
Description
Controls whether or not to enable Offline Authentication.
n n n
Default . Use the setting of the parent policy.
No . Disables this option.
Yes . Enables this option.
To have offline authentication data created for DIGIPASS Authentication for Windows
Logon, you also need to set Back-End Authentication to Always .
The number of days offline authentication data is valid, if the offline authentication data is time-based.
Possible values: 1 – 99
The number of times offline authentication data can be used before it expires.
Possible values: 1 – 2999
Table 60: Password Randomization
Field Name
Enabled
Back-End Password Length
Description
Controls whether or not to enable Password Randomization n n n
Default . Use the setting of the parent policy.
No . Disables this option.
Yes . Enables this option.
Specifies the length of the password that is to be generated when using Password
Randomization.
Valid values range from 7 to 127. The default is 16.
Table 61: Dynamic Component Registration
Field Name
Enabled
Description
Controls whether or not to enable Dynamic Component Registration.
n n n
Default . Use the setting of the parent policy.
No . Disables this option.
Yes . Enables this option.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
107
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 61: Dynamic Component Registration (continued)
Field Name Description
Windows Group Check Specifies whether and how the Windows Group Check feature should be used for
Dynamic Component Registration.
Possible values: n
Default . Use the setting of the parent policy.
Group List n
No check . Every new Client record is registered dynamically.
n
Accept requests for clients listed in groups . Group Membership for the client component will be checked before it is created. The client component will only be created if the client component is in the group mode list.
n
Accept requests for clients listed in groups . Group Membership for the client component will be checked. If the client component is found in a
Group Membership list then the client component will not be created.
The Group Check only works with Active Directory domain groups. It will not work with Windows local groups as these groups do not support the concept of hosts and computers. For Linux, the only available option is No check.
This lists the names of the Windows Groups to be checked according to the Windows Group Check radio button setting.
For groups to appear for an Active Directory back end, the Active Directory back end must exist in IDENTIKEY Appliance.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
108
Table 62: RADIUS
Field Name
Supported Protocols
Wireless Session Lifetime
TLS Session Lifetime
Max. Fast Reconnect Count
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Description
List of RADIUS protocols which may be used with this policy.
Default
Any
Secure
Custom
Use the setting of the parent policy.
Use any RADIUS protocol suggested by the client.
Enable all of the following EAP or PEAP protocols: n n n
EAP-TTLSv0
PEAPv0
PEAPv1
Select one or more of the following protocols.
n n n n n n n n
EAP-TTLSv0
PEAP v0
PEAP v1
PAP
CHAP
MSCHAP
MSCHAP2
VASCO-specific
For more information on these protocols, refer to the Supported RADIUS Protocols section of the IDENTIKEY Authentication Server Administrator Guide .
The length of time a machine may be connected before a fast-reconnect is required.
Two RADIUS return attributes are returned to the WAP with an Access-Accept: n n
Session-Timeout (value: Wireless Session Lifetime)
Terminate-Action (value: RADIUS-Request)
Note: The WAP in use may not support the use of these attributes, and may use its own configured defaults.
Default value: 3600 seconds (1 hour)
The length of time allowable between full (OTP) authentications.
Default value: 86400 seconds (24 hours)
Number of Fast Reconnects which may be made before a full (OTP) authentication is forced.
Note: If roaming wireless connections will be in use, the Max. Fast Reconnect Count setting should be set higher than if static wireless connections are used.
Default value: 48
IDENTIKEY Appliance 3.11.12 - Administrator Reference
109
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
5.10. Pre-Loaded Policies
Pre-loaded policies are created for IDENTIKEY Appliance during installation and provide useful policy examples for typical environments.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
110
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 63: Pre-Loaded Policies
Policy Name Parent Policy
Base Policy -
Description Fields with settings which are different from the parent policy
Globally applicable settings. In general, all other Policies should inherit from this, directly or indirectly.
User Lock Threshold=3
PIN Change Allowed=Yes
Challenge Request Method=Keyword
Primary VDP Request Method=Password
Backup VDP Request Method=Keyword
Password Backup VDP Request Keyword=otp
Identification Time Window=20
Check Challenge Mode=1
Event Window=20
Sync Window=6
Online Signature Level= 0
Identification Threshold=0
Local Authentication=None
Back-End Authentication=None
DUR=No
Password Autolearn=No
Stored Password Proxy=No
Group Check Mode=No
Check Assignment Mode=Neither
Search Up OU Path=No
Application Types=No Restriction
1-Step Challenge/Response=No
1-Step Challenge Check Digit=No
Backup VDP Enabled=No
IDENTIKEY Appliance 3.11.12 - Administrator Reference
111
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 63: Pre-Loaded Policies (continued)
Policy Name Parent Policy
IDENTIKEY Administration
Logon
IDENTIKEY Local Authentication
IDENTIKEY Windows Password Replacement
Base Policy
Base Policy
IDENTIKEY Local
Authentication
IDENTIKEY Microsoft AD Password Replacement
IDENTIKEY Local
Authentication
Description
Settings for an administration logon including Audit Viewer live connection. Separated from the main authentication policies to avoid accidental interference.
Locking is off to reduce the chance of a lock-out.
Settings applicable to all
IDENTIKEY Appliance authentication Policies, including local authentication. In general, all other IDENTIKEY Appliance
Policies using local authentication should inherit from this, directly or indirectly.
IDENTIKEY Appliance model for password replacement and
Dynamic User Registration, using Windows back-end authentication.
Fields with settings which are different from the parent policy
Local Authentication=DIGIPASS/Password during Grace Period
User Lock Threshold=0
Local Authentication=DIGIPASS/Password during Grace Period
IDENTIKEY Appliance model for password replacement with
Microsoft Active Directory (LDAP connection).
Back-End Authentication=Always
Back-End Protocol=Windows
DUR=Yes
Assignment Mode=Neither
Password Autolearn=Yes
Stored Password Proxy=Yes
Local Auth=Default
Backend Auth=Always
Backend Protocol=Microsoft AD
DUR=Yes
Password Autolearn=Yes
Stored Password Proxy=Yes
IDENTIKEY Appliance 3.11.12 - Administrator Reference
112
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 63: Pre-Loaded Policies (continued)
Policy Name
IDENTIKEY Novell eDirectory
Password Replacement
IDENTIKEY Windows Auto-
Assignment
IDENTIKEY Microsoft AD Auto
Assignment
IDENTIKEY Windows Self-
Assignment
IDENTIKEY Microsoft AD Self
Assignment
IDENTIKEY Novell eDirectory
Self-Assignment
Parent Policy
IDENTIKEY Local
Authentication
IDENTIKEY Windows Password
Replacement
IDENTIKEY Local
Authentication
IDENTIKEY Windows Password
Replacement
IDENTIKEY Novell eDirectory Password Replacement
Description Fields with settings which are different from the parent policy
IDENTIKEY Appliance model for password replacement with
NetIQ eDirectory (formerly Novell eDirectory) (LDAP connection).
IDENTIKEY Appliance model for
Auto-Assignment based on the
Windows password replacement model.
IDENTIKEY Appliance model for
Auto Assignment for Microsoft
Active Directory
IDENTIKEY Appliance model for
Self-Assignment based on the
Windows password replacement model.
IDENTIKEY Appliance model for
Self-Assignment for AD Password Replacement
IDENTIKEY Appliance model for self-assignment for NetIQ eDirectory (formerly Novell eDirectory).
Local Auth=Default
Backend Auth=Always
Backend Protocol=Novell eDirectory
DUR=Yes
Password Autolearn=Yes
Stored Password Proxy=Yes
Assignment Mode=Auto-Assignment
Search Up OU Path=Yes
Grace Period=7
Local Auth=Default
Backend Auth=If Needed
Backend Protocol=Microsoft AD
Assignment Mode=Auto-Assignment
Search-Up-OU-Path=Yes
Assignment Mode=Self-Assignment
Search Up OU Path=Yes
Self Assignment Separator=|
Local Auth = Default
Backend Auth = Always
Backend Protocol = Microsoft AD
Assignment Mode = Self-Assignment
Search-Up-OU-Path = Yes
Local Auth = Default
Backend Auth = Always
Backend Protocol = Novell eDirectory
Assignment Mode = Self-Assignment
Search-Up-OU-Path = Yes
IDENTIKEY Appliance 3.11.12 - Administrator Reference
113
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 63: Pre-Loaded Policies (continued)
Policy Name Parent Policy
IDENTIKEY RADIUS Password Replacement
IDENTIKEY RADIUS Auto-
Assignment
IDENTIKEY Local
Authentication
IDENTIKEY Local
Authentication
Description
IDENTIKEY Appliance model for password replacement and
Dynamic Component Registration using a RADIUS server for back-end authentication.
IDENTIKEY Appliance model for
Auto-Assignment based on the
RADIUS password replacement model.
Fields with settings which are different from the parent policy
Backend Authentication=Always
Backend Protocol=RADIUS
Password Autolearn=Yes
Stored Password Proxy=Yes
Grace Period=7
Search Up OU Path=Yes
Assignment Mode=Self-Assignment
IDENTIKEY RADIUS Self-
Assignment
IDENTIKEY Back End
Authentication
IDENTIKEY DP110 Provisioning 1
IDENTIKEY DP110 Provisioning 2
IDENTIKEY DP4Mobile Provisioning 1
IDENTIKEY Local
Authentication
Base Policy
Base Policy
Base Policy
Base Policy
IDENTIKEY Appliance model for
Self-Assignment based on the
RADIUS password replacement model.
IDENTIKEY Appliance model for only back-end authentication.
Change the back-end protocol to the one required.
DIGIPASS for Web provisioning model scenario 1 - Activation codes are encrypted with preloaded static passwords.
Search Up OU Path=Yes
Assignment Mode=Self-Assignment
Self Assignment Separator=|
Backend Protocol=RADIUS
Backend Authentication=Always
IDENTIKEY DP110 Provisioning model scenario 2 - Dynamic
Registration using back-end system. Change the back-end protocol to the one required.
Local Auth = DIGIPASS/Password during
Grace Period
Back-End Authentication = Always
1-Step Challenge/Response=Yes – Any challenge
IDENTIKEY DIGIPASS for Mobileprovisioning model scenario 1
Local Auth=DIGIPASS/Password during
Grace Period
1-Step Challenge/Response=Yes-Any challenge
IDENTIKEY Appliance 3.11.12 - Administrator Reference
114
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 63: Pre-Loaded Policies (continued)
Policy Name Parent Policy
IDENTIKEY DP4Mobile Provsioning 2
IDENTIKEY DP4Mobile Provsioning 3
IDENTIKEY DP4Web Provisioning 1
IDENTIKEY DP4Web Provisioning 2
IDENTIKEY DP4Web Provisioning 3
IDENTIKEY Deferred Time signature Verfication
Base Policy
IDENTIKEY Real-Time signature verfication 1
Base Policy
IDENTIKEY Real-Time signature verfication 2
Base Policy
Base Policy
Base Policy
Base Policy
Base Policy
Base Policy
Description Fields with settings which are different from the parent policy
IDENTIKEY DIGIPASS for Mobileprovisioning model scenario 2
IDENTIKEY DIGIPASS for Mobileprovisioning model scenario 3
Local Authentication = DIGIPASS/Password during Grace Period
Backend authentication= NONE
DIGIPASS type:
'Mob30'
Local Authentication = DIGIPASS/Password during Grace Period
Backend authentication= IF NEEDED
DIGIPASS type:
'Mob30'
IDENTIKEY DIGIPASS for WebProvisioning model scenario 1 -
Activation codes are encrypted with pre-loaded static passwords.
IDENTIKEY DIGIPASS for WebProvisioning model scenario 2 - preloaded user accounts and static passwords.
Local Auth = DIGIPASS/Password during
Grace Period
IDENTIKEY DIGIPASS for WebProvisioning model scenario 3 -
Dynamic Registration using back-end system. Change the back-end protocol to the one required.
Local Auth = DIGIPASS/Password during
Grace Period
DUR=Yes
Deferred time signature verification settings: Time based.
Signature Time Window = 24
Online signature level = 1 - Multiple Signatures allowed in same Time Step
Real-time signature verification settings: Time-based, several signatures are allowed in the same timestep but 2 identical successive signatures will be rejected.
Real-time signature verification settings: Time-based, one signature allowed per timestep.
Online signature level = 2 - Only 1 Signature/Time Step allowed
IDENTIKEY Appliance 3.11.12 - Administrator Reference
115
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 63: Pre-Loaded Policies (continued)
Policy Name
IDENTIKEY Real-Time signature verfication 3
Windows logon online authentication - Windows Back-End
Windows logon online authentication - LDAP AD Back-End
Windows logon online and offline authentication – Windows Back-End
Parent Policy
Base Policy
IDENTIKEY Local
Authentication
IDENTIKEY Local
Authentication
Windows logon online authentication - Windows Back-End
Windows logon online and offline authentication – LDAP AD
Back-End
Windows logon online authentication - LDAP AD
Back-End
Description Fields with settings which are different from the parent policy
Signature Time Window = 24 Deferred time signature verification settings: Event based, off-line mode.
Windows Logon with Windows back end
Windows Logon for LDAP AD back end
Windows logon online and offline authentication for Windows back end
Windows logon online and offline authentication settings for LDAP
AD back end
Back-End Authentication = Always
Back-End Protocol = Windows
Dynamic Component Registration = Yes
Enable Random Password = No
Client Group List =
Client Group Mode = No check
Offline Authentication = No
Back-End Authentication = Always
Back-End Protocol = Microsoft AD
Dynamic Component Registration = Yes
Enable Random Password = No
Client Group List =
Client Group Mode = No check
Offline Authentication = No
OfflineOffline Authentication = Yes
Offline Time Window (days) = 21
Offline Event Window = 300
Offline Authentication = Yes
Offline Time Window (days) = 21
Offline Event Window = 300
5.11. Client Properties
Note
Changes to client records (add, change, delete) will not take effect immediately on all IDENTIKEY Authentication
IDENTIKEY Appliance 3.11.12 - Administrator Reference
116
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Server instances unless replication is used to synchronize them. Where replication is not used, changes to client records will take effect when each IDENTIKEY Authentication Server instance is restarted, once the client change is available to it in its data store. Alternatively, if there is no restart, the cache of client records will refresh from the data store approximately every 15 minutes.
Table 64: Client Fields
Field Name Description
Enabled
Client Type
Location
Protocol ID
Policy ID
Created
Modified
If selected, this client component is enabled and accepted to communicate with IDENTIKEY Authentication Server.
The type of client component represented by the record. For SOAP clients, the type needs to match the component type parameter passed in the SOAP requests. Each application can identify itself as a different type of client.
The IP address or name of the machine represented by the record.
For RADIUS clients, the location must be the NAS-IP-Address or NAS-Identifier values that are sent in the RADIUS requests. A RADIUS client with Location set to default can be used to accept RADIUS requests from all IP addresses, using the same shared secret. However, where a RADIUS client record with the exact location exists, its shared secret will be used in preference to the default RADIUS client's shared secret.
For Windows Logon clients, the location can either be the FQDN , or, if the client has been created via
Dynamic Component Registration, it can be a host name or a NetBIOS name. A Windows Logon client with Location set to default can be used as a template to dynamically create components for new clients.
For all other client types the location must be the source IP address of requests which originate from that client component.
The protocol by which requests will be received from the client.
SOAP The standard SOAP protocol over HTTPS. This is used by programs using the SOAP interface from the SDK, the Administration Web Interface, and IDENTIKEY User Websites.
RADIUS
SEAL
The standard RADIUS protocol. This is used by various remote network access hardware and software systems. It can also be used as a simple authentication programming interface.
A proprietary TCP/IP based protocol used by and VACMAN Middleware 3.x. It is used by the IIS6 Module, Tcl Command-Line
Administration and for replication between IDENTIKEY Authentication Server instances.
The name of the policy that should be used for authentication, provisioning and signature validation requests from the client component.
The date and time that the client component was created. Read-only.
The date and time that the client component was last modified. Read-only.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
117
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 65: License Fields
Field Name Description
License Key IDENTIKEY Authentication Server requires you to upload a corresponding valid license for any of the following client types: n n n
Any SEAL authentication client (DIGIPASS Authentication Module)
IDENTIKEY Federation Server
IDENTIKEY User Websites
The license consists of a set of parameters followed by a signature.
For more information, refer to the IDENTIKEY ApplianceAdministrator Guide Section "Licensing".
Table 66: RADIUS Fields
Field Name
Shared Secret
Confirm Shared Secret
Character Encoding
Description
The RADIUS shared secret between the and the RADIUS client.
Allows confirmation of a new shared secret.
Encoding/locale format required by the RADIUS server.
If your RADIUS server requires the password field to be in any specific encoding/locale format other than
UTF-8, set this field to convert all RADIUS packets accordingly, otherwise authentication requests will be rejected.
Default setting: UTF-8
Table 67: SOAP Fields
Field Name Description
Trusted for Request Forwarding If selected, the client is considered to be trusted to forward SOAP requests from other clients. This setting is required to allow intermediary servers, such as HTTP proxy servers or load balancers, to forward SOAP requests and still identify the originating client.
In this case, IDENTIKEY Authentication Server evaluates the X-Forwarded-For (XFF) field of the HTTP header to identify the IP address of the originating client. More than one proxy server may appear in the list, each one verified to be trusted. If any of the servers in the XFF field is not trusted to forward requests, the initial client is considered to be the originating SOAP client, i.e. the proxy server or load balancer directly sending the request to IDENTIKEY Authentication Server.
Note that this option does not work, if you are using a load balancer with SSL tunneling. For more information, refer to the IDENTIKEY Authentication Server Performance and Deployment Guide , Section "Load Balancing".
IDENTIKEY Appliance 3.11.12 - Administrator Reference
118
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
5.12. Back-End Server Properties
Table 68: RADIUS Back-End Server Fields
Field Name Description
Back-End Server ID
Domain Name
Priority
Authentication IP Address
Authentication Port
Accounting IP Address
Accounting Port
Shared Secret
Confirm Shared Secret
Timeout
Retries
Mandatory. The name to uniquely identify the back-end server.
The name of the AD domain to be used.
The priority in the case that there are multiple back-end servers. The highest priority server is tried first, then the next highest one, etc.
Possible values: 0 – 100
The IP address on which the RADIUS server receives authentication requests.
The UDP port on which the RADIUS server receives authentication requests.
Possible values: 0 – 65535
The IP address on which the RADIUS server receives accounting requests.
The UDP port on which the RADIUS server receives accounting requests.
Possible values: 0 – 65535
The shared secret between IDENTIKEY Authentication Server and the RADIUS server.
Allows confirmation of a new shared secret.
The number of seconds to wait for a response from the back-end server before either retrying or trying another back-end server.
Possible values: 1 – 999
The number of times to retry if no response is received from the RADIUS server.
Possible values: 0 – 9
Table 69: Microsoft Active Directory Back-End Server Fields
Field Name Description
Back-End Server ID
Domain Name
Priority
Mandatory. The name to uniquely identify the back-end server.
The name of the AD domain to be used.
The priority in the case that there are multiple back-end servers. The highest priority server is tried first, then the next highest one, etc.
Possible values: 0 – 100
IDENTIKEY Appliance 3.11.12 - Administrator Reference
119
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 69: Microsoft Active Directory Back-End Server Fields (continued)
Field Name Description
Enable SSL
Location
Port
Timeout
Search Base DN
Security Principal ID
Specifies whether to encrypt the connection using SSL.
The fully qualified domain name (FQDN) or host name of the Active Directory domain controller.
The port on which the server receives authentication requests.
Possible values: 0 – 65535
The number of seconds to wait for a response from the back-end server before either retrying or trying another back-end server.
Possible values: 1 – 999
The distinguished name (DN) where the search for user accounts starts.
The user ID of the user account required for back-end authentication requests. Specify the ID of the account being used to log in to Active Directory.
If this is an encrypted connection, the format of the security principal ID will be the DN.
If this is not an encrypted connection, the format of the security principal ID is the SAM account name.
Warning
The built-in Active Directory administrator account CANNOT be used as the security principal ID. An administrator must be created to be used as the security principal ID.
Security Principal Password
Attribute Mapping
User Name Attribute Name
Phone Attribute Name
Mobile Attribute Name
Email Attribute Name
The password for the user account required for back-end authentication requests.
The LDAP attribute name to use as user's display name for DUR user information synchronization.
The LDAP attribute name to use as user's landline phone number for DUR user information synchronization
The LDAP attribute name to use as user's mobile phone number for DUR user information synchronization.
The LDAP attribute name to use as user's email address for DUR user information synchronization.
Table 70: NetIQ eDirectory Back-End Server Fields
Field Name Description
Back-End Server ID
Domain Name
Mandatory. The name to uniquely identify the back-end server.
The name of the domain to be used.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
120
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 70: NetIQ eDirectory Back-End Server Fields (continued)
Field Name Description
Priority
IP Address
Port
Timeout
Search Base DN
Security Principal DN
The priority in the case that there are multiple back-end servers. The highest priority server is tried first, then the next highest one, etc.
Possible values: 0 – 100
The IP address of the LDAP server.
The port on which the server receives authentication requests.
Possible values: 0 – 65535
The number of seconds to wait for a response from the back-end server before either retrying or trying another back-end server.
Possible values: 1 – 999
The distinguished name (DN) where the search for user accounts starts.
The distinguished name (DN) of the user account required for back-end authentication requests. The distinguished name must have permission to perform searches for users on the LDAP server. When a distinguished name is not supplied, the LDAP server must allow anonymous searches.
The password for the user account required for back-end authentication requests.
Security Principal Password
Attribute Mapping
User Name Attribute Name
Phone Attribute Name
Mobile Attribute Name
Email Attribute Name
Field Name
Back-End Server ID
Domain Name
Priority
Enable SSL
Location
The LDAP attribute name to use as user's display name for DUR user information synchronization.
The LDAP attribute name to use as user's landline phone number for DUR user information synchronization
The LDAP attribute name to use as user's mobile phone number for DUR user information synchronization.
The LDAP attribute name to use as user's email address for DUR user information synchronization.
Description
Mandatory. The name to uniquely identify the back-end server.
The name of the domain to be used.
The priority in the case that there are multiple back-end servers. The highest priority server is tried first, then the next highest one, etc.
Possible values: 0 – 100
Specifies whether to encrypt the connection using SSL.
Mandatory. The IP address of the LDAP server
IDENTIKEY Appliance 3.11.12 - Administrator Reference
121
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 70: NetIQ eDirectory Back-End Server Fields (continued)
Field Name Description
Port
Timeout
Search Base DN
User Object Class Name
User ID Attribute Name
Security Principal ID
The port on which the server receives authentication requests.
Possible values: 0 – 65535
Number of seconds to wait for a response from the back-end server before either retrying or trying another back-end server.
Possible values: 1 – 999
The distinguished name (DN) where the search for user accounts starts.
Mandatory. The name of the user object class to search within.
Mandatory. The name of the user attribute which is to be used for the search.
The distinguished name (DN) of the user account required for back-end authentication requests. The distinguished name must have permission to perform searches for users on the LDAP server. When a distinguished name is not supplied, the LDAP server must allow anonymous searches.
The password to be used for the security principal ID Security Principal Password
Attribute Mapping
User Name Attribute Name
Phone Attribute Name
Mobile Attribute Name
Email Attribute Name
The LDAP attribute name to use as user's display name for DUR user information synchronization.
The LDAP attribute name to use as user's landline phone number for DUR user information synchronization
The LDAP attribute name to use as user's mobile phone number for DUR user information synchronization.
The LDAP attribute name to use as user's email address for DUR user information synchronization.
Table 71: Back-End Server Settings Fields
Field Name Description
Microsoft Active Directory
The options in this section specify default values for all Microsoft Active Directory back-end servers, unless specified otherwise in the individual back-end server records.
If the global catalog is configured and no back-end servers have been defined, domain discovery via the global catalog will be used to search for the user. If domain discovery via the global catalog is to be used, users must be set up in the same domain in Microsoft Active Directory as they are in IDENTIKEY Authentication Server.
Enable SSL
Global Catalog Location
Specifies whether to encrypt the connection using SSL.
The location of the Active Directory global catalog.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
122
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 71: Back-End Server Settings Fields (continued)
Field Name Description
Global Catalog Port
Timeout
Security Principal ID
The port to be used for the Active Directory global catalog.
Possible values: 0 – 65535
Number of seconds to wait for a response from the back-end server before either retrying or trying another back-end server.
Possible values: 0 – 32767
The user ID of the user account required for back-end authentication requests. Specify the ID of the account being used to log in to Active Directory.
If this is an encrypted connection, the format of the security principal ID will be the DN.
If this is not an encrypted connection, the format of the security principal ID is the SAM account name.
Warning
The built-in Active Directory administrator account CANNOT be used as the security principal ID. An administrator must be created to be used as the security principal ID.
Security Principal Password
NetIQ eDirectory
The password for the user account required for back-end authentication requests.
The options in this section specify default values for all NetIQ eDirectory back-end servers, unless specified otherwise in the individual backend server records.
If anonymous binding is disabled on the NetIQ eDirectory server the security principal DN has to be a valid NetIQ eDirectory account with the necessary permissions to search the directory for the user accounts to be authenticated.
Search Base DN
Security Principal DN
The DN where the search for user accounts starts.
The distinguished name (DN) of the user account required for back-end authentication requests. The distinguished name must have permission to perform searches for users on the LDAP server. When a distinguished name is not supplied, the LDAP server must allow anonymous searches.
Security Principal Password
IBM Security Directory Server
The password for the user account required for back-end authentication requests.
The options in this section specify default values for all IBM Security Directory Server back-end servers, unless specified otherwise in the individual back-end server records.
Search Base DN The distinguished name (DN) where the search for user accounts starts.
Security Principal ID
Security Principal Password
The distinguished name (DN) of the user account required for back-end authentication requests. The distinguished name must have permission to perform searches for users on the LDAP server. When a distinguished name is not supplied, the LDAP server must allow anonymous searches.
The password to be used for the security principal ID
IDENTIKEY Appliance 3.11.12 - Administrator Reference
123
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 71: Back-End Server Settings Fields (continued)
Field Name Description
Attribute Mapping
The options in this section specify default values for all LDAP back-end servers, unless specified otherwise in the individual back-end server records.
User Name Attribute Name The LDAP attribute name to use as user's display name for DUR user information synchronization.
Phone Attribute Name
Mobile Attribute Name
The LDAP attribute name to use as user's landline phone number for DUR user information synchronization
The LDAP attribute name to use as user's mobile phone number for DUR user information synchronization.
Email Attribute Name The LDAP attribute name to use as user's email address for DUR user information synchronization.
5.13. Organizational Unit Property Sheet
IDENTIKEY Appliance 3.11.12 - Administrator Reference
124
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 72: Organizational Unit Fields
Field Name in
Administration
Interface
Description
Domain
Description
Parent Organizational Unit
Created
Modified
The domain to which the organizational unit belongs.
Read-only after creation.
A short description for the organizational unit.
The parent organizational unit.
This is used to define a hierarchy of organizational units.
Read-only after creation.
The date and time that the record was created.
Read-only.
The date and time that the record was last modified.
Read-only.
5.14. Reports Properties
Table 73: Report Fields
Field Name
Report Name
Domain Name
Report Type
Description
Description
The name the report was given when it was created.
The domain the report was created in.
The available report types are:
List Analysis Report
Detailed Analysis Report
List analysis reports list items that match the predefined criteria
The detailed analysis report shows detail of the events specified in the report definition.
Distribution Analysis Report
Trend Analysis Report
Distribution analysis reports breakdown the values of certain items over other items.
Trend analysis reports express a trend/evolution over a requested period of time for a set of reported items. The system therefore makes sub-counts at a regular interval of the amount of times an item has occurred.
The description of the report that was entered when the report was created.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
125
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 73: Report Fields (continued)
Field Name
Data Source
Grouping Level
Time Frequency
Created
Modified
Description
Where the data in the report comes from. The sources can be:
Users The user data will be used to generate the report
Users + Audit
DIGIPASS
DIGIPASS + Audit
User data and audit data will be used to generate the report
DIGIPASS data will be used to generate the report
DIGIPASS and audit data will be used to generate the report.
Audit Only audit data will be used to generate the report.
The grouping level will be used to group the information on the report into the format you require. The grouping levels are:
Client
Domain
The report information will be grouped for each client.
The report information will be grouped for each domain.
Organizational Unit
User
DIGIPASS
The report information will be grouped for each organizational unit.
The report information will be grouped for each user.
The report information will be grouped for each DIGIPASS.
For trend analysis reports. This type of report shows trends over a time period, taking sub-counts at certain time periods. Use this field to specify the sub-count time frequency.
Date the report was created.
Date the report definition was last modified.
5.15. Servers – Global Configuration
The SERVERS > Global Configuration tab contains solution-wide configuration settings applying to all IDENTIKEY
Authentication Server instances in a replicated environment.
The following settings can be configured here: n n
Auditing
Message Delivery Component (MDC) Message Settings: n n
MDC Virtual DIGIPASS
MDC Virtual Signature n n n
MDC Offline Activation Data
MDC DP Activation Delayed
MDC DP Activation Completed
IDENTIKEY Appliance 3.11.12 - Administrator Reference
126
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
5.15.1. Auditing Settings
Table 74: Global Configuration – Auditing
Field Name Description
Recent Activity Settings
Maximum Days
Maximum Records
The maximum age of audit records included in recent activity queries. A value of 0 returns no data at all.
Possible values: 0 – 90
Default value: 30
The maximum number of most recent audit records included in recent activity queries. A value of 0 returns no data at all.
Possible values: 0 – 100
Default value: 100
5.15.2. MDC Message Settings
Table 75: Global Configuration – MDC Virtual DIGIPASS Message Settings
Field Name Description
SMS Message Template Message template to use in SMS messages for Virtual DIGIPASS.
Voice Message Template
Default value: "Your one-time password is [OTP]."
Message template to read by the voice delivery service for Virtual DIGIPASS.
Default value: "Your one-time password is [OTP]."
Email Message Settings
Message template to use in e-mail messages for Virtual DIGIPASS messages. Contains the following elements:
Email Message Header Name Optional. The name of a custom message header field to set in the message header.
Email Message Header Value
Email Message Subject
Email Message Template
Default value: <empty>
Optional. The value of the custom message header field specified by Email Message Header Name .
Default value: <empty>
The text which should appear in the Subject field when a message is sent for Virtual DIGIPASS.
Default value: " Your One-Time Password"
Message template to use in mail messages for Virtual DIGIPASS.
Default value: "Your one-time password is [OTP]."
IDENTIKEY Appliance 3.11.12 - Administrator Reference
127
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 76: Global Configuration – MDC Virtual Signature Message Settings
Field Name Description
SMS Message Template Message template to use in SMS messages for virtual signatures.
Voice Message Template
Default value: "Your e-signature is [signature]. Signature Data Fields: [datafields]."
Message template to read by the voice delivery service for virtual signatures.
Default value: "Your e-signature is [signature]. Signature Data Fields: [datafields]."
Email Message Settings
Message template to use in e-mail messages for virtual signature messages. Contains the following elements:
Email Message Header Name Optional. The name of a custom message header field to set in the message header.
Email Message Header Value
Email Message Subject
Default value: <empty>
Optional. The value of the custom message header field specified by Email Message Header Name .
Default value: <empty>
The text which should appear in the Subject field when a message is sent for virtual signatures.
Email Message Template
Default value: " Your E-Signature Request"
Message template to use in mail messages for virtual signatures.
Default value: "Your e-signature is [signature]. This e-signature has been generated using the following signature data fields you have provided: [datafields]."
Table 77: Global Configuration – MDC Offline Activation Data Message Settings
Field Name Description
SMS Message Template Message template to use in SMS messages for DIGIPASS for Mobile activation.
Voice Message Template
Default value: "Your offline activation data is [oad]. Serial number: [serialnumber]."
Message template to read by the voice delivery service for DIGIPASS for Mobile activation.
Default value: "Your offline activation data is [oad]. Serial number: [serialnumber]."
Email Message Template
Message template to use in e-mail messages for DIGIPASS for Mobile activation. Contains the following elements:
Email Message Header Name Optional. The name of a custom message header field to set in the message header.
Email Message Header Value
Email Message Subject
Default value: <empty>
Optional. The value of the custom message header field specified by Email Message Header Name .
Default value: <empty>
The text which should appear in the Subject field when a message is sent for DIGIPASS for Mobile activation.
Default value: " Your DIGIPASS Offline Activation Data"
IDENTIKEY Appliance 3.11.12 - Administrator Reference
128
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 77: Global Configuration – MDC Offline Activation Data Message Settings (continued)
Field Name Description
Email Message Template Message template to use in mail messages for DIGIPASS for Mobile activation.
Default value: "Your offline activation data for the DIGIPASS with serial number [serialnumber] is [oad].
QR-code: [oadQR]."
Table 78: Global Configuration – MDC DP Activation Delayed
Field Name Description
SMS
Message Template Message template to use in SMS messages for activation delayed notifications (delayed activation).
Default value: "The activation process (max [delayed_activation_period]h) for your DIGIPASS has been started. Serial number: [serialnumber]."
Voice
Message Template Message template to read by the voice delivery service for activation delayed notifications (delayed activation).
Default value: "The activation process (max [delayed_activation_period]h) for your DIGIPASS has been started. Serial number: [serialnumber]."
Header Name
Header Value
Subject
Message Template
Optional. The name of a custom message header field to set in the message header.
Default value: <empty>
Optional. The value of the custom message header field specified by Email Message Header Name .
Default value: <empty>
The text which should appear in the Subject field when a message is sent for activation delayed notifications (delayed activation).
Default value: "Your DIGIPASS Activation Status"
Message template to use in mail messages for activation delayed notifications (delayed activation).
Default value: "The activation process for your DIGIPASS with serial number [serialnumber] has been started. You will receive additional notification within [delayed_activation_period] hours."
Table 79: Global Configuration – MDC DP Activation Completed
Field Name Description
SMS
Message Template Message template to use in SMS messages for activation completed notifications (delayed activation).
Default value: "The activation process for your DIGIPASS has been completed. Serial number: [serialnumber]."
Voice
IDENTIKEY Appliance 3.11.12 - Administrator Reference
129
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 79: Global Configuration – MDC DP Activation Completed (continued)
Field Name Description
Message Template Message template to read by the voice delivery service for activation completed notifications (delayed activation).
Default value: "The activation process for your DIGIPASS has been completed. Serial number: [serialnumber]."
Header Name Optional. The name of a custom message header field to set in the message header.
Header Value
Subject
Message Template
Default value: <empty>
Optional. The value of the custom message header field specified by Email Message Header Name .
Default value: <empty>
The text which should appear in the Subject field when a message is sent for activation completed notifications (delayed activation).
Default value: "Your DIGIPASS Activation Status"
Message template to use in mail messages for activation completed notifications (delayed activation).
Default value: "The activation process for your DIGIPASS with serial number [serialnumber] has been completed."
When configuring message templates, you can use different placeholder strings as variables. The placeholder strings are replaced during run-time with the actual values, if applicable, otherwise the placeholder string will not be replaced.
Table 80: Message Template Placeholders
Placeholder String Description
Generic Placeholders (all message settings)
[domain]
[email]
[mobile]
[phone]
[serialnumber]
[userid]
[username]
The user domain.
The user's email address.
The user's mobile number. In Active Directory, this refers to the Mobile field in the user's list of available
Telephones .
The user's phone number. In Active Directory, this refers to the Telephone number field.
The serial number of the DIGIPASS authenticator.
The user identifier.
The user name.
Authentication Placeholders (MDC Virtual DIGIPASS Message Settings)
[OTP]
The user's requested one-time password.
Virtual Signature Placeholders (MDC Virtual Signature Message Settings)
IDENTIKEY Appliance 3.11.12 - Administrator Reference
130
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
Table 80: Message Template Placeholders (continued)
Placeholder String Description
[datafields]
[signature]
[oadQR]
A comma-separated list of user data fields used to generate the requested signature.
The requested signature.
Activation Placeholders (MDC Offline Activation Data Message Settings)
[oad]
The generated offline activation data, in text format.
The generated offline activation data, presented in QR format.
This field can only be used in email message templates!
Delayed Activation Placeholders (MDC DP Activation Delayed Message Settings, MDC DP Activation Completed Message Settings)
[delayed_activation_ period]
The delayed activation period (in hours), i.e. the time span until the DIGIPASS authenticator becomes active.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
131
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings
5.16. Servers – List
Table 81: Server List – Summary
Field Name Description
Location
Policy
Created
Modified
License Key
The IP address of the IDENTIKEY Authentication Server represented by the record.
The name of the policy that should be used for administration logon requests from the component, including live connections from the Audit Viewer. This policy is used if there is no specific Administration Program Client record for the location of the administration logon.
The date and time that the client was created. Read-only.
The date and time that the client was last modified. Read-only.
For each IDENTIKEY Authentication Server, a License Key is required. This consists of a set of parameters followed by a signature. Refer to the Licensing chapter in the IDENTIKEY Appliance Administrator Guide for more information.
5.17. LDAP Back-End Authentication
5.17.1. Supported LDAP Back Ends back-end authentication using the following LDAP back ends are supported by IDENTIKEY Appliance: n n n
Microsoft Active Directory
NetIQ eDirectory
IBM Security Directory Server
5.17.2. Microsoft Active Directory Back-End Authentication Using LDAP Protocol
When deploying Microsoft Active Directory with IDENTIKEY Appliance for back-end authentication, ensure that: n n n n
The domain controllers must be Windows Server 2008 or higher.
If the global catalog is set up (via Back End > Settings in the Administration Web Interface) and no backend components have been defined, domain discovery via the global catalog will be used to search for the user. If domain discovery via the global catalog is to be used, users must be set up in the same domain on
Active Directory as they are on IDENTIKEY Appliance.
The IDENTIKEY Appliance must be configured to use the DNS server containing the DNS records of the Active Directory server on the host OS.
The user ID that is to be used to log in to the Active Directory back end during authentication must have both search and update permissions for the data that is to be accessed. Also, for ANY group that uses
IDENTIKEY Appliance 3.11.12 - Administrator Reference
132
5. IDENTIKEY Authentication Server Administration Web Interface Field Listings back-end authentication via LDAP and Active Directory, the permission List contents must be granted in the Active Directory Users and Computers Extension to bind to Active Directory.
Table 82: Supported User Logon Format for Microsoft Active Directory
UserID Format Source of UserID
UserID
MYREALM\userid [email protected]
SAMAccountName attribute of the user
Fully qualified domain name + SAMAccountName attribute of the user
SamAccountName attribute of the user + fully qualified domain name
LDAP Configuration
The LDAP back end needs to be configured in order to allow the back end to authenticate via the LDAP protocol.
For instructions on how to do this, refer to the IDENTIKEY Appliance Administrator Guide.
Warning
When using Microsoft Active Directory as the back end and configuring LDAP back-end authentication with SASL-
DIGEST-MD5, the cyrus-sasl-md5 library must be installed to ensure connectivity between IDENTIKEY Authentication Server and Active Directory!
5.17.3. NetIQ eDirectory Back-End Authentication Using LDAP Protocol
The version of NetIQ eDirectory used for LDAP back-end authentication on IDENTIKEY Appliance must be version
8.8. In addition, the following rules must be followed to set up NetIQ eDirectory for LDAP back-end authentication on IDENTIKEY Appliance: n
If anonymous binding is disabled on the NetIQ eDirectory server, the security principal DN has to be a NetIQ n n eDirectory account that has the necessary permissions to search the directory for the user accounts that have to be authenticated.
Each user ID has to be unique below the search base distinguished name in the LDAP structure.
Partitioning is not supported, although exactly the same search base distinguished name may be used on n different servers.
NetIQ eDirectory must be enabled with universal password.
Table 83: Supported User Logon Format for NetIQ eDirectory
User ID Format Source of User ID
UserID
MYREALM\userid [email protected]
User ID of the user
Fully qualified domain name + user ID of the user
User ID attribute of the user + fully qualified domain name
Note
For more information about setting up a back-end server record for NetIQ eDirectory, refer to the Administration
Web Interface Help .
IDENTIKEY Appliance 3.11.12 - Administrator Reference
133
6. Reporting
6. Reporting
IDENTIKEY Appliance provides a wide range of reporting options, with low-level control of aspects including desired fields, run-time query options, permissions, templates and scheduling.
You can use either pre-defined standard reports, which can be edited, or you can create your own customized reports.
Reports are managed from the Administration Web Interface.
For more information on reports, refer to the IDENTIKEY Appliance Product Guide .
6.1. Standard Reports
The IDENTIKEY Appliance reporting package will come with standard reports. Standard reports are provided for the most common administration tasks.
The standard reports can be grouped by their use: n n n
Reports produced by the helpdesk to help with troubleshooting functional problems n
Detailed Activity Summary n n n n n n n n
Detailed Authentication
Detailed DIGIPASS Registration
Detailed Provisioning
Detailed Signature Validation
DP Last Authentication List
Expired Users
Inactive DIGIPASS List
Signature Validation History n n
User Authentication History
User Last Authentication List n
Users About To Expire
Reports produced by system administrators to help with troubleshooting system problems n n n n
Authentication Activity by Client
Authentication Activity by User
Failed Operations Summary
Provisioning Activity by Client n n n n n n
Provisioning Activity by User
Succeeded Operations Summary
Transaction Signing Activity by Client
Transaction Signing Activity by User
Reports produced by administrators for system auditing information n
Account Lock Trend
Administration Activity Summary
Authentication Trend n n
DIGIPASS About To Expire
DP Assignment Activity Summary
IDENTIKEY Appliance 3.11.12 - Administrator Reference
134
6. Reporting n n n n n
DP Availability by Type
DP Deployment by Type
DP Deployment Trend
Expired DIGIPASS n n
Provisioning Activity Trend
Transaction Signing Activity Trend n
Unassigned DIGIPASS List
Reports relating to RADIUS clients and users n n n n
RADIUS Client Activity Summary
RADIUS Client Detailed Activity
RADIUS User Activity Summary
RADIUS User Detailed Activity
6.2. Query Definitions
Queries consist of: n n n a Data field, which is a field from the database, an Operator, which is the operation to be performed on the data field, a Value, which is the value the data field will be compared against. A value is not necessary with all operators.
To define a query you must select a data field and an operator. Operators can be selected from the following: n n n n n n n n n n n n n n n n equals does not equal starts with does not start with includes does not include ends with does not end with is null is not null is blank is not blank is greater than is greater than or equal to is less than is less than or equal to
A value is not required for every operator.
Combinations of Data field, Operator and Values can be used to define queries.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
135
6. Reporting
6.3. Query Filters
As mentioned above, queries can be defined from user, DIGIPASS and audit data fields. The fields listed below are available for selection when defining a query.
Any date defined in this list can have the following filter applied to it:
Use the operators is less than or equal to or is greater than or equal to and specify one or more days, weeks or months from now, where now is taken to be the current date.
The filter must be in the format n n n
1 day from now
6 weeks from now
5 years from now with the exact spelling and the exact number of spaces. The number must be a numeric character. The filter is not case sensitive.
The words from now can be replaced with ago. So the term is greater than or equal to 3 years ago will select information 3 years old or older.
Table 84: User Field List
Display Name Type Accepted Values
Domain Link
User:Backend Authentication
User:Created time
User:Description
String
String
Date
String
Domain of linked user.
n n n n
Default
None
If Needed
Always
Format: yyyy/mm/dd hh:mm:ss
User:Disabled Boolean n n
0
1
IDENTIKEY Appliance 3.11.12 - Administrator Reference
136
Table 84: User Field List (continued)
Display Name Type Accepted Values
User:Domain
User:Email
User:Expiration Date
User:Has Digipass
String
String
Date
String
User:Link
User:Local Authentication
String
String
Format: yyyy/mm/dd hh:mm:s n n
Assigned
Unassigned
User ID of linked User.
n n n n n
Default
None
Digipass Only
Digipass/Password
DIGIPASS or Password
User:Lock Count
User:Locked
Number
Boolean n n
0
1
User:Mobile
User:Modified time
User:Organizational Unit
User:Phone
User:Status
User:User ID
User:User Name
String
Date
String
String
String
String
String
Format: yyyy/mm/dd hh:mm:ss
The fields specified in the user field list can be referred to in the XSLT templates.
Table 85: DIGIPASS field list
Display Name Type Accepted Values
Digipass:Application Names String
Digipass:Application Types
Digipass:Assigned
String
Date
Comma-separated list of DIGIPASS Application
Names.
Comma-separated list of DIGIPASS Application
Types.
Format: yyyy/mm/dd hh:mm:ss
IDENTIKEY Appliance 3.11.12 - Administrator Reference
6. Reporting
137
Table 85: DIGIPASS field list (continued)
Display Name Type Accepted Values
Digipass:Backup VDP Enabled String
Digipass:Backup VDP Expires Date
Digipass:Backup VDP Uses Left Number
Digipass:Created time
Digipass:Digipass Type
Digipass:Domain
Date
String
String
Digipass:Grace Period End
Digipass:Modified time
Digipass:Serial Number
Digipass:Status
Date
Date
String
String
Digipass:User ID
Digipass:Expiration Date
String
Date or
String n n n n
Default
No
Yes – Permitted
Yes – Required
Format: yyyy/mm/dd hh:mm:ss
Format: yyyy/mm/dd hh:mm:ss
5-character code.
Format: yyyy/mm/dd hh:mm:ss
Format: yyyy/mm/dd hh:mm:ss n n
Assigned
Unassigned
User ID of the user to whom the
DIGIPASS authenticator is assigned.
Format: yyyy/mm/dd hh:mm:s
Table 86: Audit field list
Display Name
Audit:Action
Audit:AMID
Audit:Application
Audit:Area
Audit:Category
Audit:Characteristics
Audit:Client Location
Audit:Code
Type
String
String
String
String
String
String
String
String
Accepted Values
See
for a list of possible codes and messages used by the Audit System.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
6. Reporting
138
Table 86: Audit field list (continued)
Display Name
Audit:Command
Audit:Configuration Details
Audit:Credentials
Audit:Data Source
Audit:Data Source Location
Audit:Description
Audit:Downtime
Audit:Error Code
Audit:Error Details
Audit:Error Message
Audit:Fields
Audit:From
Audit:Input Details
Audit:Message
Audit:Object
Audit:Operation
Audit:Outcome
Audit:Output Details
Audit:Password Protocol
Audit:Policy ID
Audit:Quota
Audit:RADIUS Octets Input
Audit:RADIUS Octets Output
Type Accepted Values
String
String
String
String
String
String
String
String
String
String
String See
for a list of possible codes and messages used by the Audit System.
Number
Number See
13.1. IDENTIKEY Appliance Error Codes
for a list of error codes used by IDENTIKEY Appliance.
String See
13.1. IDENTIKEY Appliance Error Codes
used by IDENTIKEY Appliance.
for a list of error codes
String See
13.1. IDENTIKEY Appliance Error Codes
for a list of error codes used by IDENTIKEY Appliance.
String
String
String
String See
by the Audit System.
for a list of possible codes and messages used
String
Number
Number The number of bytes sent by the user
Number The number of bytes received by the user
IDENTIKEY Appliance 3.11.12 - Administrator Reference
6. Reporting
139
Table 86: Audit field list (continued)
Display Name
Audit:RADIUS Status Type
Audit:Reason
Audit:Request ID
Audit:Request Type
Audit:Server Location
Audit:Session ID
Audit:Session Time
Audit:Source
Audit:Source Location
Audit:Timestamp
Audit:To
Audit:Type
Audit:Type code
Audit:Version
Type Accepted Values
String
String
String
String
String
The audit function performed – for instance, start, stop, update
String
Number How long the user has been connected, in seconds
String
String
Date
String
Format: yyyy/mm/dd hh:mm:ss
String
Number
String
Note
Two or more values after the operator will be interpreted as if the word 'and' is between them.
6. Reporting
IDENTIKEY Appliance 3.11.12 - Administrator Reference
140
7. Importing Users with Comma-Separated Value Files
7. Importing Users with Comma-Separated Value Files
You can import DIGIPASS user accounts in bulk into the database via a comma-delimited text file saved in .csv
format. The following restrictions apply to the user import file: n n n n n
Each user account must be on a separate line in the text file.
A header line must be included at the beginning of the file to specify the names of the fields included, and the order.
The correct case is not required.
Text strings must be surrounded by double quotes.
If double quotes exist within the text string, these must be changed to double double quotes.
A user import file contains the following columns: n n n n n n n n n
User ID (maximum 255 characters)
User Name (maximum 64 characters)
Organizational Unit (organizational unit must exist already in data store)
Domain (domain must exist already in data store)
Password (maximum 255 characters)
Phone (maximum 64 characters)
Email (maximum 64 characters)
Mobile (maximum 64 characters)
SerialNumber
Note
When importing user records via .csv files, the password must meet the password complexity requirements of the policy. If a user account is created without a password, the password field must be omitted.
The SerialNumber column is optional. It can be used, however, to assign a specific DIGIPASS to each user being imported. The serial numbers for each user can be formatted as written on the DIGIPASS itself (e.g. 9087653-
4
) or as it appears in a DIGIPASS record (e.g. 009087634).
Note
A DIGIPASS record must already exist in the database in the correct domain to be assigned to the user. If a domain is not specified for a user account, the user account will be added to the master domain. If the specified domain does not exist in the database, the user account will not be imported.
Example
Example text file
USERID,DOMAIN,USERNAME,ORGANIZATIONALUNIT,PASSWORD,PHONE,EMAIL,MOBILE
"testuser1","master","TestUser1","","password","0455584965","[email protected]","0410 555 555"
"testuser2","master","TestUser2","","secret","055511312","[email protected]",""
IDENTIKEY Appliance 3.11.12 - Administrator Reference
141
7. Importing Users with Comma-Separated Value Files
To import the user information listed in this .csv
file, use the User > Import wizard in the Administration Web Interface.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
142
8. Performance Monitoring
8. Performance Monitoring
Performance Monitoring allows you to monitor specific parts of IDENTIKEY Appliance processing to produce useful performance statistics. Performance Monitoring is disabled, enabled, and managed using the Configuration Utility.
IDENTIKEY Appliance uses the following plugins in order to define its output: n n
Counter: records statistics on transactions specified in the filter.
.csv
file: allows you to define a comma-separated variable (CSV) file to which results should be written.
Refer to
for more information on the fields used by this file.
For information about performance monitoring setup and configuration, refer to the Performance Monitoring section in the IDENTIKEY Authentication Server Administrator Guide .
8.1. CSV File Format
Table 87: Performance Monitoring CSV output file format
Field Name Description
PROCID
ID
ParentID
Type
Start
Wall
Time
Process Identifier
Assigned by the OS. Each process has a process identifier assigned to it when it is started for the first time
Transaction Identifier
Assigned by IDENTIKEY Appliance, and is unique per process identifier. The first instance of a transaction identifier within a process identifier will be instance 1, and the number will increase by 1 each time the transaction is used.
Parent Transaction Identifier
The transaction identifier of the hierarchical parent
Performance monitoring transaction type name
Transaction Start Time
Time in milliseconds from the Epoch start (Midnight 1/1/1970
UTC)
Transaction Wall Time
Elapsed time in milliseconds of the transaction, including children
Transaction Time
Elapsed time in milliseconds of the transaction, excluding children
IDENTIKEY Appliance 3.11.12 - Administrator Reference
143
8. Performance Monitoring
Table 87: Performance Monitoring CSV output file format (continued)
Field Name Description
Blocked
System
User
Status
KVP
Transaction Block Time
Cumulative time in milliseconds that the transaction was blocked, exclusive of child times
Transaction System Time
System time in milliseconds of transaction, inclusive of child system time
Transaction User Time
User time in milliseconds of transaction, inclusive of child user time
Transaction Status
Possible values: n n n n
Good
Aborted
Failed
Unknown
Key Value Pairs
Miscellaneous additional information
Note
Start time is calculated from time when plugin is loaded on restart, or from time when IDENTIKEY Authentication
Server Web Administration Service is loaded.
8.2. Filters
Filters allow IDENTIKEY Appliance to restrict the amount of information that it monitors. At least one filter must be provided.
The filter must consist of the name of a performance transaction, and can contain the exact name of the performance transaction, or wildcards can be used to identify a group of transactions. When specifying a range of transactions, you can use the asterisk (*) as a wildcard; for example, you can specify all signature transactions using identikey.scenario.signature.*.
8.2.1. Performance Monitoring Transactions
This section lists the different performance monitoring transactions (per component) used in IDENTIKEY Appliance.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
144
8. Performance Monitoring n n
Queueing n identikey.queue.task
Administration n identikey.scenario.administration.component.create
n n n n n n n n identikey.scenario.administration.component.update
identikey.scenario.administration.configuration.query
identikey.scenario.administration.create
identikey.scenario.administration.delete
identikey.scenario.administration.digipass.adddevice
identikey.scenario.administration.digipass.assign
identikey.scenario.administration.digipass.bind
identikey.scenario.administration.digipass.deactivate
n n n n n n n n n n n n n n n n identikey.scenario.administration.digipass.decryptinformationmessage
identikey.scenario.administration.digipass.delete
identikey.scenario.administration.digipass.expiration
identikey.scenario.administration.digipass.generateactivationdata
identikey.scenario.administration.digipass.generateactivationmessage
identikey.scenario.administration.digipass.move
identikey.scenario.administration.digipass.query
identikey.scenario.administration.digipass.reset
identikey.scenario.administration.digipass.sendactivationdata
identikey.scenario.administration.digipass.unassign
identikey.scenario.administration.digipass.unbind
identikey.scenario.administration.digipass.view
identikey.scenario.administration.dpapp.changepin
identikey.scenario.administration.dpapp.create
identikey.scenario.administration.dpapp.disablepin
identikey.scenario.administration.dpapp.enablepin
n n n n n n n n n n n n n n n n n n n n identikey.scenario.administration.dpapp.getinfo
identikey.scenario.administration.dpapp.query
identikey.scenario.administration.dpapp.reset
identikey.scenario.administration.dpapp.reseterrorcount
identikey.scenario.administration.dpapp.resetpin
identikey.scenario.administration.dpapp.seteventcount
identikey.scenario.administration.dpapp.setpin
identikey.scenario.administration.dpapp.setpinminlen
identikey.scenario.administration.dpapp.test
identikey.scenario.administration.dpapp.unlock
identikey.scenario.administration.dpapp.update
identikey.scenario.administration.dpapp.view
identikey.scenario.administration.dpapp.virtualotp
identikey.scenario.administration.dpx.abort
identikey.scenario.administration.dpx.import
identikey.scenario.administration.dpx.import.subtask
identikey.scenario.administration.dpx.status
identikey.scenario.administration.dpx.upload
identikey.scenario.administration.emvcap.create
identikey.scenario.administration.emvcap.mode1test
IDENTIKEY Appliance 3.11.12 - Administrator Reference
145
n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n n identikey.scenario.administration.emvcap.mode2test
identikey.scenario.administration.emvcap.mode3test
identikey.scenario.administration.get.admin.domains
identikey.scenario.administration.group.query
identikey.scenario.administration.key.query
identikey.scenario.administration.key.rotate
identikey.scenario.administration.key.rotate.abort
identikey.scenario.administration.key.rotate.status
identikey.scenario.administration.key.view
identikey.scenario.administration.logoff
identikey.scenario.administration.logon
identikey.scenario.administration.policy.create
identikey.scenario.administration.policy.delete
identikey.scenario.administration.policy.geteffective
identikey.scenario.administration.policy.modify
identikey.scenario.administration.query
identikey.scenario.administration.radiusdict.getenumvals
identikey.scenario.administration.radiusdict.query
identikey.scenario.administration.report.changeowner
identikey.scenario.administration.report.delete
identikey.scenario.administration.report.download
identikey.scenario.administration.report.query
identikey.scenario.administration.report.view
identikey.scenario.administration.session.delete
identikey.scenario.administration.session.keepalive
identikey.scenario.administration.session.query
identikey.scenario.administration.set.admin.domains
identikey.scenario.administration.signature.test
identikey.scenario.administration.task.cancel
identikey.scenario.administration.task.delete
identikey.scenario.administration.task.query
identikey.scenario.administration.task.resume
identikey.scenario.administration.task.suspend
identikey.scenario.administration.task.update
identikey.scenario.administration.task.view
identikey.scenario.administration.update
identikey.scenario.administration.user.abort
identikey.scenario.administration.user.disable
identikey.scenario.administration.user.enable
identikey.scenario.administration.user.getperms
identikey.scenario.administration.user.import
identikey.scenario.administration.user.import.subtask
identikey.scenario.administration.user.link
identikey.scenario.administration.user.move
identikey.scenario.administration.user.resetpassword
identikey.scenario.administration.user.setexpiration
identikey.scenario.administration.user.setpassword
identikey.scenario.administration.user.setperms
IDENTIKEY Appliance 3.11.12 - Administrator Reference
8. Performance Monitoring
146
n n n n n n n n n n n n n n n n identikey.scenario.administration.user.status
identikey.scenario.administration.user.unlink
identikey.scenario.administration.user.unlock
identikey.scenario.administration.userattribute.create
n n n n identikey.scenario.administration.userattribute.delete
identikey.scenario.administration.userattribute.modify
identikey.scenario.administration.userfile.upload
identikey.scenario.administration.view
EMVCAP n n identikey.scenario.emvcap.authenticateuser
identikey.scenario.emvcap.securecodevalidation
Signature identikey.scenario.signature.auditactions
identikey.scenario.signature.authsignature
identikey.scenario.signature.databaseupdates
identikey.scenario.signature.gensignature
identikey.scenario.signature.identifyclientcomponent
identikey.scenario.signature.readpolicy
identikey.scenario.signature.responsegeneration
identikey.scenario.signature.signaturevalidation
n n identikey.scenario.signature.usercheck
identikey.scenario.signature.virtualsignaturegeneration
Provisioning n identikey.scenario.provisioning.activate
n n n n identikey.scenario.provisioning.assign
identikey.scenario.provisioning.databaseupdates
identikey.scenario.provisioning.dsappactivate
identikey.scenario.provisioning.dsappgenerateactivationdata
n n n n n n n n identikey.scenario.provisioning.dsappregister
identikey.scenario.provisioning.dsappsrpactivate
identikey.scenario.provisioning.dsappsrpgenerateactivationdata
identikey.scenario.provisioning.dsappsrpgenerateephemeralkey
identikey.scenario.provisioning.dsappsrpregister
identikey.scenario.provisioning.mdlactivate
identikey.scenario.provisioning.mdladddevice
identikey.scenario.provisioning.mdlregister
n n identikey.scenario.provisioning.register
identikey.scenario.provisioning.servertime
Authentication n identikey.scenario.authentication.auditaccounting
n n n n identikey.scenario.authentication.authuser
identikey.scenario.authentication.backend
identikey.scenario.authentication.backendaccounting
identikey.scenario.authentication.changebackendpassword
n n n n identikey.scenario.authentication.databaseupdates
identikey.scenario.authentication.dynamicclientregistration
identikey.scenario.authentication.dynamicuserregistration
identikey.scenario.authentication.generatechallenge
8. Performance Monitoring
IDENTIKEY Appliance 3.11.12 - Administrator Reference
147
8. Performance Monitoring n n n n n n n n n n n n n n n n n n n n n n identikey.scenario.authentication.groupcheck
identikey.scenario.authentication.identifyclientcomponent
identikey.scenario.authentication.localauth
identikey.scenario.authentication.localauth.digipass
identikey.scenario.authentication.localauth.nodigipass
identikey.scenario.authentication.offlineauthenticationdatageneration
identikey.scenario.authentication.onestepchallenge
identikey.scenario.authentication.readpolicy
identikey.scenario.authentication.responsegeneration
identikey.scenario.authentication.updatepassword
identikey.scenario.authentication.usercheck
identikey.scenario.authentication.windowspasswordrandomization
Reporting n identikey.scenario.reporting.add
n n n n n n identikey.scenario.reporting.changeowner
identikey.scenario.reporting.delete
identikey.scenario.reporting.download
identikey.scenario.reporting.format.query
identikey.scenario.reporting.generation
identikey.scenario.reporting.query
n n identikey.scenario.reporting.update
identikey.scenario.reporting.view
Storage n n n identikey.subsystems.storage.ad
identikey.subsystems.storage.odbc
Communicators n identikey.communicator.asynchronous
identikey.communicator.command
n n n n identikey.communicator.query
identikey.communicator.radius
identikey.communicator.seal
identikey.communicator.soap
Crypto n n identikey.crypto.hsm
identikey.crypto.ssm
Audit identikey.audit
identikey.scenario.audit.digipass.getactivity
identikey.scenario.audit.getmessage
identikey.scenario.audit.user.getactivity
ODBC n n n n n n n identikey.subsystems.storage.odbc.commit
identikey.subsystems.storage.odbc.connect
identikey.subsystems.storage.odbc.create
identikey.subsystems.storage.odbc.move
identikey.subsystems.storage.odbc.remove
identikey.subsystems.storage.odbc.search
identikey.subsystems.storage.odbc.update
IDENTIKEY Appliance 3.11.12 - Administrator Reference
148
9. System Monitoring
9. System Monitoring
The purpose of system monitoring is to monitor IDENTIKEY Appliance via a management application and an SNMP server to request information from IDENTIKEY Appliance; system monitoring also serves to alert administrators of certain events that originate in different system components.
We recommend to monitor the following types of events: n n n
System OS events
IDENTIKEY Appliance Configuration Tool events
IDENTIKEY Authentication Server events
The System Monitoring tool requires one or more notification targets to be defined to specify the output format.
The available target formats are: n n n
SMS
SNMP traps
In order monitor the system via SNMP, for instance to be notified about events via SNMP traps and to process these traps, SNMP must be configured. For detailed information on System Monitoring, querying the SNMP server,using
SNMP and configuring notification targets , refer to the System Monitoring sections of the IDENTIKEY ApplianceProduct Guide and the IDENTIKEY ApplianceAdministrator Guide .
9.1. SNMP Trap Parameters
SNMP traps can be configured as notification targets for the different event types. The trap parameters are specified in the following table.
Table 88: SNMP Traps - Parameters
System Monitored
Element Monitored
System OS Events:
Disk space /var/log: log file system
Trap Parameters
/var/pg: DB file system
/var/identikey: IDENTIKEY file system – log and trace files
A DISMAN-EVENT-MIB::mteTriggerFired trap is sent with the following parameters: n n n n n n n n n n
DISMAN-EVENT-MIB::sysUpTimeInstance 0:0:22:00.30
SNMPv2-MIB::snmpTrapOID.0
DISMAN-EVENT-MIB::mteTriggerFired
DISMAN-EVENT-MIB::mteHotTrigger.0 log file system
DISMAN-EVENT-MIB::mteHotnotification targetName.0
DISMAN-EVENT-MIB::mteHotContextName.0
DISMAN-EVENT-MIB::mteHotOID.0 UCD-SNMP-MIB::dskErrorFlag.1
DISMAN-EVENT-MIB::mteHotValue.0 1
UCD-SNMP-MIB::dskPath.1 /var/log
UCD-SNMP-MIB::dskErrorMsg.1 /var/log: less than 10% free (=
100%)
IDENTIKEY Appliance 3.11.12 - Administrator Reference
149
9. System Monitoring
Table 88: SNMP Traps - Parameters (continued)
System Monitored
Element Monitored
Memory Memory Low
Processes, monitored via
SNMP traps:
Identikey server (ikeyserver)
LDAP sync daemon (ikldapsync)
MDC daemon (mdcserver)
System Logging daemon (syslog-ng)
Timeserver (ntpd)
Trap Parameters
A DISMAN-EVENT-MIB::mteTriggerFired trap is sent with the following parameters: n n n n n n n n n n n
DISMAN-EVENT-MIB::sysUpTimeInstance 0:0:26:01.01
SNMPv2-MIB::snmpTrapOID.0
DISMAN-EVENT-MIB::mteTriggerFired
DISMAN-EVENT-MIB::mteHotTrigger.0 memory
DISMAN-EVENT-MIB::mteHotnotification targetName.0
DISMAN-EVENT-MIB::mteHotContextName.0
DISMAN-EVENT-MIB::mteHotOID.0
UCD-SNMP-MIB::memSwapError.0
DISMAN-EVENT-MIB::mteHotValue.0 1
UCD-SNMP-MIB::memErrorName.0 swap
UCD-SNMP-MIB::memSwapErrorMsg.0 Running out of swap space
(3136)
A DISMAN-EVENT-MIB::mteTriggerFired trap is sent with the following parameters: n n n n n n n n n n n
DISMAN-EXPRESSION-MIB::sysUpTimeInstance 0:0:00:50.30
SNMPv2-MIB::snmpTrapOID.0
DISMAN-EVENT-MIB::mteTriggerFired
DISMAN-EVENT-MIB::mteHotTrigger.0 process down
DISMAN-EVENT-MIB::mteHotnotification targetName.0
DISMAN-EVENT-MIB::mteHotContextName.0
DISMAN-EVENT-MIB::mteHotOID.0
SNMPv2-SMI::enterprises.2021.2.1.100.4
DISMAN-EVENT-MIB::mteHotValue.0 1
SNMPv2-SMI::enterprises.2021.2.1.2.4 "syslog-ng"
SNMPv2-SMI::enterprises.2021.2.1.101.4 "No syslog-ng process running."
A similar trap is sent when the service comes back online: n n n n n n n n n n n
DISMAN-EXPRESSION-MIB::sysUpTimeInstance 0:0:00:40.40
SNMPv2-MIB::snmpTrapOID.0
DISMAN-EVENT-MIB::mteTriggerFired
DISMAN-EVENT-MIB::mteHotTrigger.0 process up
DISMAN-EVENT-MIB::mteHotnotification targetName.0
DISMAN-EVENT-MIB::mteHotContextName.0
DISMAN-EVENT-MIB::mteHotOID.0
SNMPv2-SMI::enterprises.2021.2.1.100.4
DISMAN-EVENT-MIB::mteHotValue.0 0
SNMPv2-SMI::enterprises.2021.2.1.2.4 "syslog-ng"
SNMPv2-SMI::enterprises.2021.2.1.101.4 ""
IDENTIKEY Appliance Configuration Tool Events:
IDENTIKEY Appliance 3.11.12 - Administrator Reference
150
9. System Monitoring
Table 88: SNMP Traps - Parameters (continued)
System Monitored
Element Monitored
Configuration
Tool
Trap Parameters
All Configuration Tool events in the audit log are monitored.
For Configuration Tool events, traps with the following parameters are sent: n n n n
DISMAN-EVENT-MIB::sysUpTimeInstance 2:1:13:15.27
SNMPv2-MIB::snmpTrapOID.0 VASCO-AXSGUARD-IDENTIFIER-
MIB::vdsIaAuditNotification
VASCO-AXSGUARD-IDENTIFIER-MIB::vdsIaNotificationContent.0
"User sysadmin logged in"
VASCO-AXSGUARD-IDENTIFIER-MIB::vdsIaNotificationType.0 Success
The MIB files sent with the VASCO- AXSGUARD- IDENTIFIER-
MIB::vdsIaAuditNotification trap contains the information listed here, and explains which notifications and information can be monitored .
IDENTIKEY Authentication Server Events:
IDENTIKEY
Authentication
Server
All IDENTIKEY Authentication Server events in the audit log are monitored.
n
SNMP- FRAMEWORK- MIB::snmpEngineTime.0 = INTEGER: 1193 seconds n
SNMP-FRAMEWORK-MIB::snmpEngineBoots.0 = INTEGER: 2 n
SNMPv2-MIB::snmpTrapOID.0 = OID:VASCO-IDENTIKEY-MIB::vdsIkSecAlertEvent n
VASCO-IDENTIKEY-MIB::vdsIkSecAlertTime.11 = STRING:2014-11-
12,14:10:31.6,+0:0 n
VASCO-IDENTIKEY-MIB::vdsIkSecAlertType.11 = STRING: Failure n
VASCO-IDENTIKEY-MIB::vdsIkSecAlertContent.11 = STRING: "Timee=\"2014/11/12 14:10:31\"; Code=\"F- 002001\";AMID-
D=\"0x47D1168D40EC1D4148F99985FD450501\";
Desc=\"Userauthentication failed.\";"
When an SNMP trap is sent, the information is added to a Security Alert Table; this is an SNMP table defined in
IDENTIKEY Authentication Server and contains a list of recent security alerts. This list is defined in the VASCO-
IDENTIKEY-MIB.txt
file and can be accessed using an SNMP viewer. It is non-persistent, i.e. the list is cleared when the IDENTIKEY Authentication Server process is stopped.
9.2. MIB
The data for monitoring IDENTIKEY Appliance via SNMP is held in a Management Information Base (MIB) .
The MIB is an extensible data store which contains the information required for your particular instance of SNMP.
Whilst MIB refers to the data store in general, the term can also be used to refer to a particular component of the
MIB, which should really be referred to as a MIB-module.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
151
9. System Monitoring
SNMP for IDENTIKEY Appliance supports a subset of the available MIB-modules. There are also some MIB modules specific to IDENTIKEY Appliance.
9.2.1. MIB Table
The following table provides an overview of the MIBs used in IDENTIKEY Appliance.
Table 89: MIB Table
MIB Name Function
VASCO-MIB
VASCO-IDENTIKEY-SCENARIO-MIB
VASCO-IDENTIKEY-DATAMODEL-MIB
VASCO-IDENTIKEY-CRYPTO-MIB
VASCO-IDENTIKEY-COMMUNICATOR-SOAP-MIB
VASCO-IDENTIKEY-COMMUNICATOR-SEAL-MIB
RADIUS-AUTH-CLIENT-MIB
RADIUS-AUTH-SERVER-MIB
VASCO-AXSGUARD-IDENTIFIER-MIB
Defines the high-level structure of the VASCO Data Security
Enterprise MIB. It provides the main structure in which all the
VASCO product MIBs can be placed. It includes global definitions valid for all VASCO's products.
Defines all data for scenarios for VASCO products.
IDENTIKEY Authentication Server data model MIB. It contains a very basic counter based view on the interaction with the database.
Defines the crypto key information for IDENTIKEY Authentication Server.
Defines the SOAP communicator information for IDENTIKEY
Authentication Server.
Defines the SEAL communicator information for IDENTIKEY
Authentication Server.
For entities implementing the client-side of the RADIUS authentication protocol.
For entities implementing the server-side of the RADIUS authentication protocol
Contains traps specific to IDENTIKEY Appliance.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
152
10. Login Permutations
10. Login Permutations
The information that must be entered during a login will vary according to the configuration settings of the relevant policy, the login method, and any actions to be performed during the login.
This section refers to authentication processing only, not signature validation or provisioning.
Login Methods
The login methods specified are: n n n
Response-Only
Challenge/Response: n
1-Step Challenge/Response: a random challenge is presented on the login page before the user n
ID is known. This is supported for SOAP clients and form-based IIS Modules.
2-Step Challenge/Response: a challenge is generated after the user submits their user ID with a request to be given a challenge. The user then logs in with the response to the challenge in a second step. This is supported for all kinds of authentication client.
Virtual DIGIPASS - primary or backup
Login Actions
A user may be allowed to do these things during a login: n n n n
Set their Server PIN – on first use or after a PIN reset.
Change their Server PIN.
Inform the IDENTIKEY Appliance that their static password for the back-end system – e.g. Windows - has been modified.
Perform a Self-Assignment for a DIGIPASS in their possession.
Login Variables
The variables which a user may need to enter, in order to do one of the above functions are listed below. The code or word used to designate each variable in the following tables is included in brackets.
n n n n n n one-time password (OTP)
Password (Password)
Server PIN (PIN)
Serial Number of their DIGIPASS (Serial No)
Serial Number Separator (Sep.)
Request Keyword (Keyword)
Password Format
In a SOAP authentication request, there are two password formats that can be used: n n
Cleartext Combined : all the login variables listed above must be entered into a single password field. This format applies when the login screen or web page cannot be extended with additional entry fields.
Cleartext Separate : the login variables are entered in separate fields.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
153
10. Login Permutations
In RADIUS authentication requests, the PAP password protocol corresponds to the Cleartext Combined password format. The CHAP, MSCHAP and MSCHAP2 password protocols are handled as different password formats (as the password is hashed in various ways according to the protocol). In general, these hash-based password formats are not capable of combining different login variables, unless IDENTIKEY Appliance is already aware of all the variables.
In administrative logons and IIS Module authentication requests, the Cleartext Combined password format is always used.
10.1. Login Policy Settings
The policy settings which will affect the variables required in logins are:
Stored Password Proxy
If this attribute is set to Enabled, each user's password must be kept up to date in IDENTIKEY Appliance. This is typically achieved by enabling Password Autolearn.
Password Autolearn
If IDENTIKEY Appliance is informed of a user's password change, the new password will only be recorded by
IDENTIKEY Appliance if Password Autolearn is enabled in the relevant policy.
Serial Number Separator
If a Serial Number Separator is specified, the user may enter their DIGIPASS serial number exactly as it appears on the back of their DIGIPASS (or in the documentation provided to the user), including dashes. If a
Serial Number Separator is not specified, the DIGIPASS serial number must be padded to 10 characters, with all non-numerical characters removed.
back-end authentication
For more information about login policy settings relating to back-end authentication, refer to
10.2. Login Permutations Tables .
10.2. Login Permutations Tables
In the following login permutations tables, back-end authentication Required means that the back-end authentication setting is set to Always or If Needed .
Where back-end authentication is enabled, logins which receive a fail from the back-end authenticator may achieve a login action – for example, Change PIN – even though the login was unsuccessful.
Note back-end authentication is required for Self-Assignment and Password Autolearn logins.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
154
10. Login Permutations
10.2.1. Response-Only: Cleartext Separate Password Format
With this login permutation, the following two tables only apply if SOAP uses Cleartext Separate password format.
In both tables, back-end authentication is still required for successful Self-Assignment.
The following table applies in this case when: n n
EITHER the Stored Password Proxy feature is enabled
OR back-end authentication is not enabled
Table 90: Login Permutations - Response-OnlyCleartext Separate
Login Type Existing
PIN?
Input Fields Required
Server
PIN
Required
Normal login
Set PIN
Change PIN
Changed Password
Set PIN and Changed Password
Change PIN and Changed Password
Self-Assignment
No
Server
PIN
Required
Normal login
Changed Password
Self-Assignment
Yes
No
N/A
N/A
N/A
Yes
No
Yes
Yes
No
Yes
PIN+OTP
OTP+NewPIN+ConfirmPIN
PIN+OTP+NewPIN+ConfirmPIN
Password+PIN+OTP
Password+OTP+NewPIN+ConfirmPIN
Password+PIN+OTP+NewPIN+ConfirmPIN
SerialNo+Password+PIN+OTP
SerialNo+Password+OTP+NewPIN+ConfirmPIN
OTP
Password+OTP
SerialNo+Password+OTP
The following table applies in this case when: n n
The Stored Password Proxy feature is not enabled
AND back-end authentication is enabled
IDENTIKEY Appliance 3.11.12 - Administrator Reference
155
10. Login Permutations
Table 91: Login Permutations - Response-Only Separate
Login Type Existing
PIN?
Input Fields Required
Server
PIN
Required
Normal login
Set PIN
Change PIN
Changed Password
Set PIN and Changed Password
Change PIN and Changed Password
Self-Assignment
No
Server
PIN
Required
Normal login
Changed Password
Self-Assignment
Yes
Yes
No
Yes
No
Yes
Yes
No
N/A
N/A
N/A
Password+PIN+OTP
Password+OTP+NewPIN+ConfirmPIN
Password+PIN+OTP+NewPIN+ConfirmPIN
Password+PIN+OTP
Password+OTP+NewPIN+ConfirmPIN
Password+PIN+OTP+NewPIN+ConfirmPIN
SerialNo+Password+PIN+OTP
SerialNo+Password+OTP+NewPIN+ConfirmPIN
Password+OTP
Password+OTP
SerialNo+Password+OTP
10.2.2. Response-Only: CHAP/MS-CHAP/MS-CHAP2
The following table applies if RADIUS is using CHAP, MS-CHAP, or MS-CHAP2, and: n n
EITHER the Stored Password Proxy feature is enabled
OR back-end authentication is not enabled
Table 92: Login Permutations - Response-Only CHAP/MSCHAP/MSCHAP2
Login Type Server PIN
Required?
Password Field Contents
Normal login Yes
No
PIN+OTP
OTP
10.2.3. 2-Step Challenge/Response: Cleartext Separate Password Format
The following table applies when SOAP uses Cleartext Separate password format
The column Stored Password Proxy Off AND Back-End Auth. Required contains Yes when:
IDENTIKEY Appliance 3.11.12 - Administrator Reference
156
10. Login Permutations n n
The Stored Password Proxy feature is not enabled
AND back-end authentication is enabled
In most cases, this does not affect 2-Step Challenge/Response; just when a Keyword only is used.
Table 93: Login Permutations – 2-Step Challenge/Response Cleartext Separate
Login Type Request Method Stored Password Proxy Off AND back-end authentication Required
Normal Login Keyword
Password
Keyword-Password
Password-Keyword
Changed Password Keyword
Password
Keyword-Password
Password-Keyword
Self-Assignment
1
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Yes
No
N/A
N/A
Pre-Challenge Step Input Fields for
Response step
Keyword
Keyword
Password+OTP
OTP
Password OTP
Keyword+Password OTP
Password+Keyword OTP
Keyword Password+OTP
Password OTP
Keyword+Password OTP
Password+Keyword OTP
Password OTP
SerialNo (separate parameter)
2
Note
Self-Assignment using 2-Step Challenge/Response is always done using the static password. The request method is not applicable until after the DIGIPASS is assigned to the user account.
1
Back-end authentication is still required for successful Self-Assignment.
2
If a Serial Number Separator is not set, the serial number must have all non-numerical characters removed and be padded to 10 characters with preceding zeroes.
10.2.4. 2-Step Virtual DIGIPASS Login
The 2-step Virtual DIGIPASS login is possible when using a SOAP client, the RADIUS Access-Challenge mechanism or an IIS Module in form-based authentication mode. The static password is required in either the first or the second step, but not both.
However, many RADIUS environments, IIS Module basic authentication, and DIGIPASS Authentication for Windows
Logon do not support the 2-step login process. If the 2-step login process is not possible, two separate 1-step logins are required. The second login must include the password as well as the OTP, but it is not necessary to provide the password in the first login, if only a keyword is used.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
157
10. Login Permutations
Using the Cleartext Combined password format, all inputs in the table below are entered into the Password field.
In addition, with the Cleartext Separate password format, the keyword and/or password are always entered into the Static Password field, while the OTP is entered into the OTP field.
Table 94: Login Permutations – Virtual DIGIPASS
Login Type Request Method
Normal Login
Changed Password
Keyword
Password
Keyword-Password
Password-Keyword
Keyword-Only
Keyword
Password
Keyword-Password
Password-Keyword
Keyword-Only
2-Step Login Two 1-Step Logins
Step 1 Step 2 Step 1 Step 2
Keyword
Password
Password+OTP Keyword
OTP Password
Keyword+Password OTP
Password+Keyword OTP
N/A
Keyword
Keyword+Password
Password+Keyword
N/A Keyword
Password+OTP Keyword
Password+OTP
Password+OTP
Password+OTP
Password+OTP
OTP
Password+OTP
Password OTP
Keyword+Password OTP
Password+Keyword OTP
N/A N/A
Password
Keyword+Password
Password+Keyword
Keyword
Password+OTP
Password+OTP
Password+OTP
Password+OTP
Note
DIGIPASS Authentication for Windows Logon does not support 2-step Virtual DIGIPASS login and requires two 1step logins to be performed consecutively instead.
The Keyword-Only request method is only available with DIGIPASS Authentication for Windows Logon.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
158
11. Open Port Numbers on Firewall
11. Open Port Numbers on Firewall
IDENTIKEY Appliance uses several different ports to communicate (see
Table 95: Incoming Ports used by
and
Table 96: Outgoing Ports used by IDENTIKEY Authentication Server
). If these are blocked by a firewall, some features will not work correctly.
11.1. Incoming Ports
Table 95: Incoming Ports used by IDENTIKEY Appliance
Port Description Default Protocol
SOAP
RADIUS Authentication
8888
1812
TCP
UDP
RADIUS Accounting
SEAL without SSL
1813
20003
UDP
TCP
Configuration
Not configurable
Configuration Tool:
Authentication Server >
RADIUS Communicator >
Authentication Port
Configuration Tool:
Authentication Server >
RADIUS Communicator >
Accounting Port
Not configurable
Source
SOAP client
RADIUS client
RADIUS back-end server
RADIUS client
RADIUS back-end server
SEAL with SSL
Net-SNMP agent
Net-SNMP trap handler
Audit replication
Configuration replication
Replication Wizard
20004
161
162
5432
20014
20101
TCP
UDP
UDP
TCP
TCP
TCP
Not configurable
Not configurable
Not configurable
Not configurable
Not configurable
Not configurable
IIS module
Replication from other
IDENTIKEY Authentication
Server instances
IIS module
DIGIPASS Authentication for
Windows Logon
IDENTIKEY Authentication
Server
IDENTIKEY Authentication
Server
IDENTIKEY Appliance in replication setup
IDENTIKEY Appliance in replication setup
IDENTIKEY Appliance Replication Wizard
IDENTIKEY Appliance 3.11.12 - Administrator Reference
159
11. Open Port Numbers on Firewall
11.2. Outgoing Ports
Table 96: Outgoing Ports used by IDENTIKEY Authentication Server
Port Description Default Protocol Configuration
RADIUS Authentication 1812 UDP
RADIUS Accounting
LDAP
1813
389
UDP
TCP
Administration Web Interface: Backend server records > Authentication
Port
Administration Web Interface: Backend server records > Accounting Port
Administration Web Interface: Backend server records > Port
LDAPS
HTTPS
636
443
Audit replication 5432
Configuration replication 20014
Replication Wizard 20101
SNMP trap 162
TCP
TCP
TCP
TCP
TCP
UDP
Administration Web Interface: Backend server records > Port
Not configurable
Not configurable
Not configurable
Not configurable
Not configurable
Destination
RADIUS back-end server
RADIUS back-end server
NetIQ eDirectory, IBM Security Directory
Server, or Active Directory back-end servers
NetIQ eDirectory, IBM Security Directory
Server, or Active Directory, back-end servers
VASCO Customer Portal
( https://cp.vasco.com/ )
IDENTIKEY Appliance in replication setup
IDENTIKEY Appliance in replication setup
IDENTIKEY Appliance Replication Wizard
Alerts sent by IDENTIKEY Appliance
SNMP trap server
IDENTIKEY Appliance 3.11.12 - Administrator Reference
160
12. Audit Message Types
12. Audit Message Types
IDENTIKEY Appliance logs the following types of audit messages:
Table 97: Audit Message Types
Error
Warning
Information
Success
Failure
RADIUS
Type Description
The message contains details about a system, configuration, licensing or some internal error. Errors do not include normal processing events such as failed logins.
Warning messages contain details about potential problems within the system. This could include details such as a failed connection attempt to a database
Informational messages provide details about events within the system that need to be recorded but do not indicate errors or potential errors.
Success messages contain details about processing events that were correctly processed. This may include successful authentications or successful administration commands.
Failure messages contain details about processing events that failed. This may include rejected authentications, or administration actions that failed.
RADIUS accounting message.
12.1. Messages
Table 98: Audit Messages
Message Code Description
E000001
E001001
E001002
E001003
E002001
Notes
A system error has occurred.
The DIGIPASS Plug-In failed to start up.
This message is used whenever there is a general processing error. It will contain full details of the error.
The Plug-In encountered a fatal error on startup such as an invalid or missing configuration file.
The DIGIPASS Plug-In has been forced into the disabled state.
The Plug-In has started up, but is in a disabled state in which it will not process authentication requests. This is typically due to a license problem (an invalid or missing License Key in the Plug-In's Component record); an invalid Component Location setting in the configuration file; or a missing Component record for the Plug-In.
The Authentication Server failed to start up The Authentication Server encountered a fatal error on startup. This is typically due to an invalid or missing configuration file or failure to connect to the data store.
The Active Directory AAL3 library failed to initialize.
The Active Directory AAL3 library encountered a fatal error on initialization, e.g. invalid configuration settings in the configuration file.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
161
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
E002002
E002003
E002004
E002005
E002006
E002007
E002008
E002009
Notes
The DIGIPASS Authentication library failed to initialize.
The ODBC AAL3 library failed to initialize.
The RADIUS protocol handler failed to initialize.
The protocol handler that receives and processes
RADIUS requests did not start up. This may be because of a missing license key in the Authentication Server
Component record, or because the license key in that component record does not enable RADIUS support.
Look for the line RADIUS=Yes in the license key details.
A common reason for this error, when RADIUS is enabled in the license key, is that the RADIUS ports are already in use by another process on the machine.
Alternatively, the configuration settings may be invalid.
The Authentication Server AAL3 library failed to initialize.
The authentication server AAL3 library encountered a fatal error on initialization, e.g. invalid configuration settings in the configuration file.
The Replication library failed to initialize.
The Authentication library encountered a fatal error on initialization, e.g. invalid configuration settings in the configuration file.
The ODBC AAL3 library encountered a fatal error on initialization, e.g. invalid configuration settings in the configuration file.
Initialization of a Replication destination server failed.
The replication library encountered a fatal error on initialization, e.g. invalid configuration settings in the configuration file.
The replication library found the configuration of a destination server to be invalid. The library will still start up if its main configuration settings are valid and there is at least one valid destination server. For the invalid destination servers, this audit message is generated.
The Authentication Server protocol handler failed to initialize.
The VM2 Compatibility protocol handler failed to initialize.
The protocol handler that receives and processes administration requests and authentication requests from the IIS modules failed initialization. This is typically due to invalid configuration settings or because the API port is already in use by another process on the machine.
The protocol handler that receives and processes authentication requests from the VACMAN Middleware version 2 IIS modules failed initialization. This is typically due to invalid configuration settings or because the API port is already in use by another process on the machine.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
162
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
E002010
E002011
E002012
E009001
E012001
E012002
Notes
The SOAP protocol handler failed to initialize.
The RADIUS dictionary was loaded but with some errors.
The SOAP protocol handler encountered a fatal error on initialization. Typically, this occurs when the
SOAP ports configured in IDENTIKEY Authentication
Server are already in use by another application or service.
IDENTIKEY Authentication Server failed to import one or more RADIUS attribute definitions from the RADIUS dictionary due to parse errors. Those parse errors were ignored and IDENTIKEY Authentication Server succeeded to import the remaining RADIUS attribute definitions.
Failed to load the RADIUS dictionary file.
An error occurred in the Message Delivery Component.
The RADIUS Profile was not found in Steel-Belted
RADIUS.
IDENTIKEY Authentication Server failed to load the
RADIUS dictionary file because the file was not available.
This could be due to an incorrect configuration (incorrect path to and/ or dictionary file name).
The Message Delivery Component (MDC) encountered an error during the process of submitting a request to the HTTP gateway and interpreting the response. This may indicate a configuration problem for the gateway or connectivity issues. The audit message may contain further details from the gateway.
When a RADIUS Profile name is in the DIGIPASS user account but that name is not found in SBR, the login is failed with this error.
This can also occur if there is no RADIUS Profile in the
DIGIPASS user account, but there is a default RADIUS profile configured that was not found in SBR.
The RADIUS Attribute was not known by Steel-Belted RADIUS.
When the DIGIPASS user account has a RADIUS attribute in its Authorization Profiles/Attributes list, the attribute must be found in SBR. When such an attribute is not known to SBR, the login is failed with this error.
The most likely reason for this error to occur is that the spelling of the attribute Name is different in SBR compared to the DIGIPASS user account. This may also occur if the value of the attribute does not convert to the correct data type expected by SBR. For example, if an IP address attribute has a value which is not a representation of an IP address.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
163
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
E013001
E013002
E013003
E013004
E016001
E020001
E020002
W004001
Notes
A connection to an ODBC data source could not be established.
A connection to an ODBC data source is broken.
The migration subsystem cannot migrate the data record.
The data version cannot be handled by this server.
End synchronization for profile incomplete by error.
Task management failed to start.
Task management failed to stop.
A connection attempt to Active Directory failed.
An attempt to connect to an ODBC data source failed.
This may be caused by any of the following: n n n n
The database is unavailable for some reason such as rebooting.
The database is too busy temporarily to service the connection.
There are networking problems.
Your credentials used in connecting to the database are invalid.
An established connection to an ODBC data source has broken. This may be caused by any of the following: n n n
The database suddenly becomes unavailable for some reason such as rebooting.
The database becomes too busy temporarily to service the connection.
There are networking problems.
Data migration is enabled, but the migration subsystem cannot migrate the data record. This usually happens if the data migration failed due to an error.
Data migration is enabled, but the migration subsystem is unable to handle the data record. This usually happens if the record data version is unsupported.
This audit message is produced by the LDAP Synchronization Tool.
IDENTIKEY Authentication Server failed to initialize and start the task scheduler.
IDENTIKEY Authentication Server failed to stop the task scheduler.
An attempt to connect to an Active Directory domain controller failed. This may be caused by any of the following: n n n
The domain controller is unavailable for some reason such as rebooting.
The domain controller is too busy temporarily to service the connection.
There are DNS or networking problems.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
164
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
W004004 A connection attempt to a Replication destination server failed.
W005001
W005004
W006001
W006002
A connection to Active Directory has terminated due to an error.
A connection to a Replication destination server has terminated due to an error.
An invalid RADIUS packet has been received.
A RADIUS request has been received from an unknown source.
Notes
An attempt by the Replication library to connect to a destination server failed. This may be caused by any of the following: n n n
The incorrect IP address or port is configured.
The destination server is unavailable for some reason such as rebooting.
There are networking/connectivity problems, such as an intermediate firewall blocking the port.
An established connection to an Active Directory domain controller has broken. This may be caused by any of the following: n n n
The domain controller suddenly becomes unavailable for some reason such as rebooting.
The domain controller becomes too busy temporarily to service the connection.
There are DNS or networking problems.
An established connection to a destination server has broken. This may be caused by any of the following: n n
The destination server suddenly becomes unavailable for some reason such as rebooting.
There is a temporary networking or connectivity problem.
A RADIUS request received was invalid (did not conform to the RADIUS protocol). The request is discarded.
This can also occur when a response is received from a
RADIUS Server to which a request was forwarded, if the response was invalid. The response is discarded.
A RADIUS request was received but there is no RADIUS client component for the source of the request, and there is no “default” RADIUS client c omponent. The request is discarded.
This audit message will be repeated at intervals when the same unknown source sends requests, but not for every request.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
165
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
W006003 A request has been received from a RADIUS Client with no Shared Secret defined.
W006004
W006005
W006006
W009001
W009002
A RADIUS request forwarded by this server has been received – there must be a circular proxy chain.
An Access-Challenge received from the RADIUS
Server cannot be handled.
A RADIUS Server is not responding.
Virtual DIGIPASS one-time password delivery failed.
Unable to send activation notification message due to missing destination attribute in the user account.
Notes
A RADIUS request was received where there is a
RADIUS client component for the source of the request, but that component record does not have a shared secret defined. Therefore, it is not possible to handle the request and it is discarded.
This will not occur if there is a “default” RADIUS client component that has a shared secret.
This audit message will be repeated at intervals when the same source sends requests, but not for every request.
This can occur when the forwards a request to a
RADIUS server, and the RADIUS server forwards the request back, due to its own proxy rules. It can also occur indirectly in a longer 'proxy chain'. The request is discarded, otherwise an infinite loop could be created.
If this occurs, there must be an error in the proxy configuration of the RADIUS server(s).
This can occur when the IDENTIKEY Authentication
Server forwards a request to a RADIUS server and the
RADIUS server responds with an Access-Challenge. An
Access-Challenge can only be handled when the
IDENTIKEY Authentication Server forwards the password unmodified to the RADIUS server. If the
IDENTIKEY Authentication Server 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.
The IDENTIKEY Authentication Server has not managed to get a response from the RADIUS server for some time. This message indicates that there may be a problem with the RADIUS server.
The MDC could not successfully deliver a text message via the HTTP gateway. The audit message should contain further details from the gateway.
The activation notification could not be sent, because no destination attribute is specified in the respective user account.
This audit message is usually recorded during delayed activation, if the activation/registration operation completes successfully, but the notification messages cannot be sent.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
166
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
W010001
W011001
W011002
W011003
W012001
W012002
W012003
A blank password was used for back-end authentication, as Stored Password Proxy is disabled and the user did not enter a static password.
A Backup Virtual DIGIPASS quota of uses has been finished.
No DIGIPASS was found to assign to a new
DIGIPASS user account for Auto-Assignment.
A DIGIPASS user account has become locked.
A Replication queue entry has been rejected due to possible tampering.
A Replication update received has been ignored, as the local data is more up-to-date.
A Replication queue entry has not been inserted.
Notes
This message only occurs when the back-end authentication setting is Always .
When Stored Password Proxy is disabled, the
IDENTIKEY Authentication Server does not pass on the password stored in the DIGIPASS user account to Windows for back-end authentication. If a user does not enter their password as well as their OTP, the login will fail because their password has not been provided to
Windows.
BVDP Uses Remaining has just been decremented to 0 for a DIGIPASS. The user will not be able to use that
DIGIPASS for Backup Virtual DIGIPASS logins until the
Uses Remaining is increased or cleared.
No available DIGIPASS were found for Auto-Assignment. This may be because: there were no unassigned
DIGIPASS in the right location; the unassigned
DIGIPASS did not conform to policy restrictions; the unassigned DIGIPASS were Reserved for individual assignment .
The location in which the IDENTIKEY Authentication
Server searches for available DIGIPASS records can be controlled to some extent using the Search Upwards in
Org. Unit hierarchy setting.
A user just exceeded the User Lock Threshold of failed logins and their DIGIPASS user account is now locked.
Administrator action is required to unlock the account.
This message is audited when IDENTIKEY Authentication Server detects that the replication queue entry’s hash value is incorrect. This could be due to possible replication entry tampering.
The Authentication Server has received a data update from another Authentication Server via the replication process, but its local data is already newer than the data received via replication.
It is normal that this can occur, but it can also indicate a potential synchronization issue.
This can occur when a replication queue has reached its maximum size. This is most likely to occur when the destination server is down or cannot be contacted due to a networking problem.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
167
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
W012004
W013001
W013002
W014001
W015001
W015002
W016001
W016002
W016004
I001001
I001002
I002001
Notes
A failed attempt to append to the replication queue has been deleted.
An invalid request has been received by the
Authentication Server.
A request has been received by the Authentication Server from an unknown source.
The License Key is missing or invalid.
This message is audited when IDENTIKEY Authentication Server fails to add a replication entry into the replication queue and finally deletes the replication entry.
The Authentication Server has received an invalid authentication, administration or replication request.
The Authentication Server has received an authentication, administration or replication request from an unknown or unauthorized source. If the request was from a valid source, this message indicates that a component record is missing (or that a required restart of the service has not been made since the creation of the necessary component record).
A valid, unexpired license key is required to process any kind of authentication request. This message will be generated periodically when authentication requests are received by the Authentication Server, when it does not have a valid license key.
An invalid request has been received by the SOAP server.
A request has been received from a client for which the component record is disabled.
Synchronization incomplete.
User link for synchronization not attempted.
Synchronization of user information attributes during Dynamic User Registration failed.
IDENTIKEY Authentication Server received a request for a client component that is disabled.
This audit message is produced by the LDAP Synchronization Tool
This audit message is produced by the LDAP Synchronization Tool
User information attributes from the back-end system have not been added to the DIGIPASS user account during Dynamic User Registration.
Configuration details are given in the audit message.
The DIGIPASS Plug-In has started up successfully.
The Authentication Server has started up successfully.
The Active Directory AAL3 library has been initialized successfully.
Configuration details are given in the audit message.
Note that the Authentication Server can start up successfully even if a component such as the RADIUS protocol handler does not start up successfully.
The Active Directory 'AAL3' library has completed initialization. Configuration details are given in the audit message.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
168
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
I002002
I002003
I002004
I002005
I002006
I002007
I002008
I002009
I002010
I003001
I003002
I004001
I004004
I005001
Notes
The DIGIPASS Authentication library has been initialized successfully.
The ODBC AAL3 library has been initialized successfully.
The RADIUS protocol handler has been initialized successfully.
The Authentication Server AAL3 library has been initialized successfully
The Authentication library has completed initialization.
Configuration details are given in the audit message.
The ODBC AAL3 library was initialized successfully. Configuration details are given in the audit message.
The protocol handler that receives and processes
RADIUS requests started up. Configuration details are given in the audit message.
The Authentication Server AAL3 library was initialized successfully. Configuration details are given in the audit message.
The Replication library has been initialized successfully.
Initialization of a Replication destination server succeeded.
The replication library was initialized successfully. Configuration details are given in the audit message.
The replication library initialized a destination server successfully. Configuration details are given in the audit message.
The Authentication Server protocol handler has been initialized successfully.
The VM2 Compatibility protocol handler has been initialized successfully.
The protocol handler that receives and processes administration requests and authentication requests from the IIS modules was initialized successfully. Configuration details are given in the audit message.
The protocol handler that receives and processes authentication requests from the VACMAN Middleware version 2 IIS modules was initialized successfully. Configuration details are given in the audit message.
The SOAP protocol handler has been initialized successfully.
IDENTIKEY Authentication Server has successfully initialized the SOAP communication sub-system and has started listening for incoming requests.
The DIGIPASS Plug-In has shut down.
The Authentication Server has shut down.
A connection attempt to Active Directory was successful.
A connection attempt to a Replication destination server was successful.
A connection to Active Directory has been terminated normally.
An established connection to an Active Directory domain controller has ended with a normal disconnection.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
169
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
I005002
I005004
I006001
I006002
I006003
I007001
I007002
I007003
I007004
I008001
I008002
Notes
A connection to Active Directory has been timed out for load-balancing.
A connection to a Replication destination server has been terminated normally.
A RADIUS Access-Request has been received.
A RADIUS Accounting-Request has been received.
An established connection to an Active Directory domain controller has been ended for load-balancing purposes. Periodically, the connections will be dropped and new ones established, in case there is a less busy domain controller available. The time period is defined by the configuration setting Max-Bind-LifeTime in the file, in minutes.
An established connection to a replication destination server has ended with a normal disconnection.
IDENTIKEY Authentication Server has received an access request. The audit message will indicate what action will be taken as well as key details of the request.
IDENTIKEY Authentication Server has received an accounting request. The audit message will indicate what action will be taken as well as key details of the request.
A RADIUS Server has started responding again.
A RADIUS Access-Accept has been issued.
A RADIUS Access-Challenge has been issued.
A RADIUS Access-Reject has been issued.
IDENTIKEY Authentication Server has rejected an access request.
A RADIUS Accounting-Response has been issued.
IDENTIKEY Authentication Server has acknowledged an accounting request. Note however that, unless the request is forwarded to a RADIUS server, no processing is carried out by the IDENTIKEY Authentication Server.
A DIGIPASS has been moved for assignment to a user.
After IDENTIKEY Authentication Server had not managed to get a response from the RADIUS server for some time, this message indicates that it is responding again.
The IDENTIKEY Authentication Server has accepted an
Access-Request. Note however that it is still possible that after the IDENTIKEY Authentication Server has accepted the request, another component of the overall process may still decide to reject the request ultimately.
IDENTIKEY Authentication Server has issued a challenge, either Challenge/Response or Virtual DIGIPASS.
A user-to-user link has been removed due to assignment of a DIGIPASS.
Upon assignment of a DIGIPASS to a user, if the
DIGIPASS is not already in the same location (organizational unit) as the user, it is moved to that location.
If a DIGIPASS user account is linked to another in order to share the DIGIPASS, it must not have a DIGIPASS assigned itself. If DIGIPASS is assigned, the link will be broken.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
170
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
I009001
I010001
I010002
I011001
I011002
A Virtual DIGIPASS one-time password has been delivered.
User authentication was not handled.
A stored password change was unhandled.
A DIGIPASS grace period has been ended by the use of a one-time password
A Backup Virtual DIGIPASS expiration date has been set due to the first request for a Virtual onetime password.
Notes
The MDC successfully delivered a text message via the
HTTP gateway, as reported by the gateway. The audit message may contain further details from the gateway.
Note that depending on the gateway, it may still be possible for delivery to fail after the gateway has reported success.
IDENTIKEY Authentication Server decided not to handle an authentication request due to policy and/or
DIGIPASS user account settings. The main reasons why this may occur are: the effective Local Authentication and back-end authentication settings were both
None ; the user failed the Windows Group Check , using the Pass Requests for users not in listed groups back to host system option.
Note that the effective settings are the effective settings of the policy, unless the DIGIPASS user account overrides the policy.
IDENTIKEY Authentication Server decided not to handle a password change request due to policy and/or
DIGIPASS user account settings. The main reasons why this may occur are: the effective Local Authentication and back-end authentication settings were both
None ; the user failed the Windows Group Check , using the Pass Requests for users not in listed groups back to host system option.
Note that the effective settings are the effective settings of the policy, unless the DIGIPASS user account overrides the policy.
The first time that an assigned DIGIPASS is used successfully to log in, if a grace period is still active, it expires upon using the OTP. Depending on the Local
Authentication settings in the relevant policy, users can then either continue to use both their static password or their DIGIPASS authenticator ( DIGIPASS or Password ), or must only use the authenticator
( DIGIPASS/Password during Grace Period or Digipass Only ) to log in.
A user has requested a Backup Virtual DIGIPASS OTP for the first time, when the effective Backup VDP
Enabled setting is Yes – Time Limited and they did not already have an Enabled Until date set on their
DIGIPASS. At this time, they are given the Time Limit from the policy by adding it to the current date.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
171
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
I011003
I011004
I011005
I011006
I011007
I011008
I011009
I011010
I011011
Notes
A Backup Virtual DIGIPASS time limit has been expired by the use of the normal one-time password.
A Backup Virtual DIGIPASS quota of uses has been set due to the first request for a Virtual one-time password.
A DIGIPASS user account has been created using
Dynamic User Registration.
A new static password has been stored using
Password Autolearn.
A DIGIPASS has been assigned to a new DIGIPASS user account using Auto-Assignment.
A DIGIPASS has been assigned to a DIGIPASS user account using Self-Assignment.
A DIGIPASS challenge has been issued for a Self-
Assignment attempt.
A user has changed their DIGIPASS PIN.
Successfully assigned DIGIPASS
A user who has been using Backup Virtual DIGIPASS
(Backup VDP) has used their normal OTP login using the DIGIPASS again. When the effective Backup VDP
Enabled setting is Yes – Time Limited , using the normal OTP login ends their time limit immediately. This is done by setting the Enabled Until date on their
DIGIPASS to the current date.
An administrator action is required to reset their
Enabled Until date, if the user is to be allowed to use
Backup Virtual DIGIPASS again.
A user has requested a Backup Virtual DIGIPASS OTP for the first time, when the effective Backup VDP Max.
Uses/User setting is greater than 0 and they did not already have a Uses Remaining date set on their
DIGIPASS. At this time, they are given the Max.
Uses/User limit from the policy.
A DIGIPASS user account has been created automatically upon successful back-end authentication .
This occurs when the Dynamic User Registration feature is enabled.
A new static password has been stored in the DIGIPASS user account after successful back-end authentication
. This occurs when the Password Autolearn feature is enabled.
Upon creation of a new DIGIPASS user account through
Dynamic User Registration, an available DIGIPASS has been assigned to the new account automatically. This occurs when the Auto-Assignment feature is enabled.
A user has successfully assigned a DIGIPASS to themselves using the Self-Assignment feature.
A user has obtained a challenge during an attempt to assign a DIGIPASS to themselves using the Self-Assignment feature. In order to complete the assignment, they must provide the correct response to the challenge from the DIGIPASS.
A user has changed their Server PIN during their login, or set it up on first use or after a PIN reset.
The DIGIPASS has been successfully assigned during software DIGIPASS Provisioning .
IDENTIKEY Appliance 3.11.12 - Administrator Reference
172
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
I011011
I011012
I011013
I011014
I011015
I011016
I011017
I011018
I011019
I012001
I013001
I013002
I013003
I016001
Notes
A DIGIPASS authenticator has been assigned to a
DIGIPASS user account in Provisioning registration.
Added new DIGIPASS for Web activation location
The command has auto-assigned a new DIGIPASS license to the specified user.
Static Password Update Successful
A DIGIPASS has been assigned to a DIGIPASS User
Account by an Administrator.
A static password has been randomized and updated with AD successfully.
A new DIGIPASS has been added for a Web activation location during software DIGIPASS Provisioning .
The static password for the user has been successfully changed.
An administrator has assigned a DIGIPASS to a
DIGIPASS user.
IDENTIKEY Authentication Server has successfully generated a new random static password for the user and has updated this new password for this user in Active
Directory.
Offline authentication data generated successfully.
Authentication Server has received offline authentication state data.
Offline data in unconfirmed state, offline data needs to be re-generated.
IDENTIKEY Authentication Server has generated new offline authentication data for the DIGIPASS Authentication for Windows Logonaccording to the policy settings for the offline data generation.
IDENTIKEY Authentication Server has received an offline authentication data usage update from a DIGIPASS
Authentication for Windows Logon client.
IDENTIKEY Authentication Server has detected that the offline data for the DIGIPASS Authentication for Windows Logon client is in an unconfirmed state. As a consequence, the offline data will be re-generated.
A DIGIPASS authenticator has been unassigned from a user account during the execution of the command.
A DIGIPASS authenticator has been unassigned from a DIGIPASS user account by an administrator.
A query has been specified [object] for report generation.
A connection to an ODBC data source has been made successfully.
A connection to an ODBC data source has been terminated normally.
An established connection to an ODBC data source has ended with a normal disconnection.
A data record has been migrated successfully.
Start synchronization for profile.
This audit message is produced by the LDAP Synchronization Tool.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
173
12. Audit Message Types
I020020
I020021
I020022
I020023
I020024
I021001
Table 98: Audit Messages (continued)
Message Code Description
I016002
I016003
I016004
I020001
I020002
I020010
I020011
I020012
I021002
S001001
End synchronization for profile.
End synchronization for profile incomplete by terminate request.
Synchronization of user information attributes during Dynamic User Registration was successful.
Task management has started successfully.
Task management stopped.
Task started.
Task completed.
Task canceled.
Task created.
Task deleted.
Task modified.
Task suspended.
Task resumed.
Epoch Header.
Epoch Footer.
A query for a single [object] record was successful.
Notes
This audit message is produced by the LDAP Synchronization Tool.
This audit message is produced by the LDAP Synchronization Tool.
User information attributes from the back-end system have been added to the DIGIPASS user account during
Dynamic User Registration.
The sub-system in charge of the task management has started successfully.
The sub-system in charge of the task management has stopped successfully.
The execution of an individual background task has started.
The execution of an individual task has completed.
The execution of an individual background task has been canceled.
A new task has been created successfully.
A task has been deleted successfully.
A task has been modified successfully.
The execution of a task has been suspended.
The execution of a task has been resumed.
This audit message denotes the start of a new secure auditing epoch.
This audit message denotes the end of a secure auditing epoch.
IDENTIKEY Authentication Server or an administrator has made a successful query to the data store for a single record. In the case of the IDENTIKEY Authentication Server this may be a search for its component record; for an administrator it could be any single record query. The audit message has details of the record found.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
174
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
S001002
S001003
S002001
S002002
A query for [object] records was successful.
A command of type [object] [command] was successful.
User authentication was successful.
User authentication issued a challenge.
Notes
IDENTIKEY Authentication Server or an administrator has made a successful query to the data store for some records. In the case of the IDENTIKEY Authentication
Server this may be a search for a RADIUS client component record; for an administrator it could be any list query. The audit message has details of the records found but this may be truncated.
An administrator has issued a successful data modification command such as an update of settings or one of the DIGIPASS Application operations like Reset PIN.
The audit message has details of the command and results.
The Authentication library has passed authentication for a request. Note however that the IDENTIKEY
Authentication Server or another component of the overall process may still decide to reject the request ultimately.
The Authentication library has issued a challenge for an authentication request, either Challenge/Response or Virtual DIGIPASS.
S002003
S002004
A random server challenge has been issued.
A stored password change was successful.
S002005
S002006
S002007
S002008
S002009
S003001
Encrypted Static Password Change successful.
Fast-reconnect granted for user.
A secure challenge has been issued.
A signing request has been issued.
Back-end password change was successful.
A replication update was sent successfully.
IDENTIKEY Authentication Server has successfully processed a password change request.
IDENTIKEY Authentication Server has successfully updated the encrypted static password for the selected authenticator (DP110).
IDENTIKEY Authentication Server successfully authenticated a user via a fast reconnect authentication.
The command has successfully generated a secure challenge.
The command has successfully generated a signing request.
The Active Directory static password of the user with a configured IDENTIKEY Authentication Server back end was changed successfully.
This message is audited at the source server, when a database change is sent to a destination server and processed successfully.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
175
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
S003002
S004001
S004002
S004003
S004004
S005001
S005002
S005008
S005009
S005010
S005011
S005012
S005013
S005014
Notes
A Replication update received has been processed successfully.
An administrative logon was successful.
A Live Audit connection was successful.
An administrative session was closed.
An administrative session was killed.
This message is audited at the destination server, when a database change is received and processed successfully.
An administrative logon to the Authentication Server was successful.
A Live Audit connection to the Authentication Server was successful.
An administrative session was closed. This could be due to the session expiring, the session having been idle for too long, or due to an explicit session logoff performed by an administrator.
An administrator has successfully killed an administrative session.
Registration Successful
Activation Successful
The registration of a software DIGIPASS during Provisioning was successful.
The activation of a software DIGIPASS during software
DIGIPASS Provisioning was successful.
Registration of a DIGIPASS license was successful.
The command has successfully generated an activation message.
Registration of DIGIPASS device was successful.
The command has successfully generated an activation message.
A DIGIPASS instance was successfully activated.
DSAPP-SRP registration was successful.
The signature was successfully validated.
The command has successfully registered DSAPP-
SRP; this registration is required to authenticate the user and initiate a DSAPP-SRP provisioning operation.
DSAPP-SRP generation of ephemeral key was successful.
The command has successfully exchanged keys for a
DSAPP-SRP provisioning operation.
DSAPP-SRP generation of activation data was successful.
Activation data for standard online activation or activation in Multi-Device Licensing mode (Activation Message 1) were successfully generated and the generated activation data was successfully encrypted using DSAPP-SRP session keys.
DSAPP-SRP activation was successful.
The command to activate DSAPP-SRP was successful.
This command is required to activate a DIGIPASS authenticator after a successful provisioning operation; the activation also validates the OTP of the newly generated software DIGIPASS or binds it to a mobile device.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
176
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
S006001
S007001
S008001
S009001
S009002
S010001
S010002
S016001
S016002
S016003
S016004
S022001
S022002
S022003
Notes
Signature Validation Successful.
Report generation was successful.
Server configuration was successful.
A DNS record update was successful.
A DNS record was de-registered successfully.
EMV-CAP user authentication was successful.
EMV-CAP DIGIPASS provisioning succeeded.
Synchronization successful.
When signing a transaction using the Signature Verification function, the signature validation was successful.
A report was generated successfully.
IDENTIKEY Authentication Server has successfully updated the server configuration.
The IDENTIKEY Authentication Server has successfully updated a DNS record.
IDENTIKEY Authentication Server successfully deregistered itself from the DNS subsystem. As a consequence, this instance of IDENTIKEY Authentication
Server will not be available anymore for DIGIPASS
Authentication for Windows Logon clients who dynamically search for IDENTIKEY Authentication Server hosts.
An EMV-CAP-based user authentication was successful for the specified user.
IDENTIKEY Authentication Server successfully provisioned a new EMV-CAP DIGIPASS.
This audit message is produced by the LDAP Synchronization Tool.
User link for synchronization successful.
DIGIPASS assignment for synchronization successful.
This audit message is produced by the LDAP Synchronization Tool.
This audit message is produced by the LDAP Synchronization Tool.
Create organizational unit for synchronization successful.
This audit message is produced by the LDAP Synchronization Tool.
Key rotation operation was successful.
Key rotation operation has started.
The key rotation of a single [object] was successful.
IDENTIKEY Authentication Server has successfully rotated a key.
IDENTIKEY Authentication Server has started a key rotation operation.
Key rotation of a single [object] was successful.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
177
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
F001001
F001002
F001003
F002001
F002002
F002003
F002004
F002005
A query for a single [object] record failed.
A query for [object] records failed.
A command of type [object] [command] failed.
User authentication failed.
An encrypted static password change failed.
A stored password change failed.
Encrypted Static Password Change failed.
Fast-reconnect denied for user.
Notes
IDENTIKEY Authentication Server or an administrator has made an unsuccessful query to the data store for a single record. In the case of the IDENTIKEY Authentication Server this may be a search for its component record; for an administrator it could be any single record query. The audit message has basic details of the failure, but there should be a preceding E000001 with more details.
IDENTIKEY Authentication Server or an administrator has made an unsuccessful query to the data store for some records. In the case of the IDENTIKEY Authentication Server this may be a search for a RADIUS client component record; for an administrator it could be any list query. The audit message has basic details of the failure, but there should be a preceding E000001 with more details.
An administrator has issued an unsuccessful data modification command such as an update of settings or one of the DIGIPASS Application operations like Reset
PIN. The audit message has basic details of the failure, and there may be a preceding E000001 with more details.
The Authentication library has failed authentication for a request. The audit message has details of the failure
(see Chapter
) and there may be a preceding E000001 with error details.
IDENTIKEY Authentication Server has failed to update the encrypted static password for the specified authenticator (DP110).
The Authentication Server has not processed a password change request. The audit message has details of the failure (see Chapter
and there may be a preceding E000001 with error details.
IDENTIKEY Authentication Server has failed to update the encrypted static password for a specified authenticator (DP110).
IDENTIKEY Authentication Server has failed to authenticate a user using the fast reconnect mechanism.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
178
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
F002006
F002007
F002008
F002009
F003001
F003002
F004001
F004002
F005001
F005008
Notes
A stored static password change failed due to password strength requirements not being met.
A secure challenge could not be generated.
A signing request could not be generated.
Back-end password change failed.
Sending a Replication update was unsuccessful.
Processing a Replication update received was unsuccessful.
IDENTIKEY Authentication Server has failed to update the stored static password as the new password does not meet the minimum password strength requirements.
The command has failed to generate a secure challenge due to invalid input data.
The command has failed to generate a signing request due to invalid input data.
Changing the Active Directory static password of the user with a configured IDENTIKEY Authentication
Server back end failed.
This message is audited at the source server, when a database change is not sent to a destination server successfully, or it was sent but the processing at the destination was unsuccessful.
This message is audited at the destination server, when a database change is received but is not processed successfully.
An administrative logon was rejected.
A Live Audit connection was rejected.
The Authentication library has failed an administrative login request. The audit message has details of the failure (see Chapter
) and there may be a preceding E000001 with error details.
Note that this may occur even when preceded by a successful authentication (S002001) message, for example if the user's credentials were OK but they did not have Administrative Logon privilege.
The Authentication library has failed a Live Audit connection request. The audit message has details of the failure (see ) and there may be a preceding E000001 with error details.
Note that this may occur even when preceded by a successful authentication (S002001) message, for example if the user's credentials were OK but they did not have Administrative Logon or Live Audit Connection privilege.
The provisioning registration did not succeed.
Registration was unsuccessful.
A registration attempt of a DIGIPASS license failed.
The command has failed to generate an activation message or activation message image due to invalid input data.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
179
12. Audit Message Types
Table 98: Audit Messages (continued)
Message Code Description
F005009 A registration attempt of a DIGIPASS device failed.
Notes
The command has failed to generate an activation message or activation message image due to invalid input data.
The signature validation has failed.
F005010 An activation attempt of a DIGIPASS instance failed.
DSAPP-SRP registration failed.
F005011
F005012
F005013
F005014
F006001
DSAPP-SRP generation of ephemeral key failed.
DSAPP-SRP generation of activation data failed.
DSAPP-SRP activation failed.
Signature validation was unsuccessful.
The command failed to register DSAPP- SRP; consequently, the user was not authenticated and the
DSAPP-SRP provisioning operation was not initiated.
The keys for a DSAPP-SRP provisioning operation could not be exchanged.
Activation data for standard online activation or activation in Multi-Device Licensing mode (Activation Message 1) could not be generated.
The command failed to activate DSAPP-
SRP; consequently, the OTP of the newly generated software DIGIPASS could not be validated or bound to a mobile device.
A signature validation has failed.
Table 99: Audit Messages (specific to IDENTIKEY Applianceonly)
Message Code Description Notes
SE024001 Configuration change
SE024002 System action
The Configuration Tool settings were changed.The
audit message should contain details on old and new values, although password fields will be blocked out.
A system action was performed. Examples of such actions are: n n n n n n
Reboots shutdowns backup restore license installed reset admin user
IDENTIKEY Appliance 3.11.12 - Administrator Reference
180
13. Error and Status Codes
13. Error and Status Codes
This section lists the standard IDENTIKEY Appliance error and status codes with the associated messages and some further explanation. These lists only include codes generated specifically by IDENTIKEY Appliance, and may not map to error codes from other sources (e.g. Windows) in trace and audit messages.
13.1. IDENTIKEY Appliance Error Codes
Refer to the following tables for information on specific error and status codes.
Table 100: Error Code List
Error
Code
Error Message Description Notes
0
-1
-2
-3
-10
-11
-12
-13
STAT_SUCCESS
STAT_ERROR
STAT_INVPARAM
STAT_MEMORY
STAT_COMMS
STAT_LICENCE
STAT_OS_FAILURE
STAT_NOT_FOUND
(No error)
An unspecified error occurred
The parameters supplied were invalid
A memory error occurred
A communications error occurred
A license error has occurred
An operating system call failed
The object was not found
This error code may occur when a more specific error code is not available or was recorded separately.
Parameters supplied to a function or command were invalid.
Memory allocation failed. This is normally due to the system running low on memory.
Inter-process or inter-component communication failed. This may also occur with communications to Active Directory or a database. This error is normally accompanied by further details.
General-purpose license failure when a more specific code is not available or was recorded separately.
A system call failed. This may include file handling, Active Directory Services Interface and other calls. It is normally accompanied by further details.
An attempt was made to perform an operation on an object, such as an Active Directory object, but the object did not exist. For example, this may occur when one administrator deletes a record that another administrator is about to update, when the update operation is attempted.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
181
13. Error and Status Codes
Table 100: Error Code List (continued)
Error
Code
Error Message
-14 STAT_EXISTS
-15
-16
-17
-18
-19
-20
-21
-22
-23
STAT_OVERFLOW
STAT_VERSION
STAT_INVDATA
STAT_INVOBJECT
STAT_INVCOMMAND
STAT_INUSE
STAT_NOSUPPORT
STAT_OBJERR
STAT_MISSINGFLD
Description Notes
The object already exists
The supplied buffer was of the incorrect size
A version error has occurred
The supplied data are invalid
The object is invalid
The command is invalid
The object is in use
The operation is not supported
An object error has occurred
A required field was missing
An attempt was made to create an object, such as an Active Directory object, but the object already exists. For example, this may occur when two administrators try to create the same record at the same time.
An internal data buffer was of insufficient length to hold the data required.
A version mismatch has occurred. Further details in the error record will indicate which versions were mismatched.
General-purpose error when input data to an operation is incorrect. Further details of the error will be recorded.
An attempt was made to perform an operation upon an object type that was not recognized.
An attempt was made to perform an operation using a command that was not recognized.
An attempt was made to delete an object, such as an Active Directory object, but that object was in use.
This may occur when you try to delete a policy, but another policy inherits from the one you are deleting, or a component uses the policy.
General-purpose error when an operation is attempted on an object that does not support it. For example, an attempt is made to generate a Virtual DIGIPASS OTP using a
DIGIPASSthat is not enabled for Virtual
DIGIPASS.
General-purpose error on an operation on an object. This should be supplemented with more specific details.
An operation was attempted without specifying one or more mandatory input fields.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
182
13. Error and Status Codes
Table 100: Error Code List (continued)
Error
Code
Error Message
-24 STAT_AUDITFAILURE
-30
-31
-32
-33
-34
-35
-80
-100
-101
-102
Description Notes
STAT_INVCONFIG
STAT_INVTYPE
STAT_NOT_INITIALISED
STAT_CACHE_FULL
STAT_CACHE_MAX_REF_COUNT
STAT_BUSY
STAT_TIMEOUT
VDSERR_INVPLUGIN
VDSERR_NOSPACE
VDSERR_USERCANCEL
Auditing failed
The configuration is invalid
A type mismatch has occurred
An operation failed because auditing was mandatory, but failed.
The configuration data in the configuration file are invalid. The error record should indicate which specific data were invalid.
General-purpose error when one data type is expected but a different data type was provided.
One or more objects were not initialized Internal initialization error. More specific error details will be recorded.
The cache is full An attempt was made to add an entry to a cache, but the cache has reached its configured maximum size.
The cache entry has reached the maximum reference count
The system is currently too busy to service the request
An attempt was made to retrieve an item from a cache, but the item was already in use and the configuration indicates a limit on the number of times an item can be retrieved from the cache at one time.
The system received a new request for processing, but hit a resource usage limit of some type. This indicates that the system is too loaded to handle the request. For example, there may be no spare database connection to use, even after waiting a short time for one to become available.
A timeout has occurred
An invalid plug-in was supplied
There is no space left to write the message
User cancelled authentication process
An operation failed because of a timeout.
Audit configuration specifies a plug-in method that is unknown or that could not be successfully loaded.
While auditing to text file, the server was unable to write. This would normally occur if disk space has run out.
The user chose to cancel a request rather than provide credentials when prompted.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
183
13. Error and Status Codes
Table 100: Error Code List (continued)
Error
Code
Error Message
-140
-141
-142
-143
-150
-200
-201
-202
-250
Description Notes
STAT_DPERROR A DIGIPASS error has occurred General-purpose failure of a DIGIPASS operation such as OTP verification, Reset PIN,
Unlock, etc. This is normally accompanied by a more specific error code and message from the IDENTIKEY Authentication Server
VACMAN Controller library.
STAT_MISSING_STATE_DATA
STAT_IDENT_ERROR_
THRESHOLD_REACHED
Offline state data was required but not supplied
The threshold for identifying errors has been reached.
STAT_CHANGE_PIN_MANDATORY An error with the mandatory change of the DIGIPASS authenticator PIN has occurred.
STAT_VDP_DELIVERY_FAILED Delivery of the Virtual DIGIPASS onetime password failed
STAT_LICENCE_EXP
STAT_INVLICENCE
STAT_LICENCE_INVSIG
STAT_NEEDSKEY
The license has expired
The license data are invalid
The License Key is corrupted
Decryption has failed - no Storage Key is specified in the Encryption Settings
A Virtual DIGIPASS OTP was generated successfully, but delivery by text message failed.
A separate message will give more details about the failure.
The license key has an expiration date set, and the date has passed. A permanent license key must be obtained.
One of the details embedded into the license key is invalid for the component in which it is being loaded. The component will not be able to use the license key. This may be the IP address, the component type, or any other detail that can be seen in the license key text.
The signature at the bottom of the license key is invalid. This would typically occur if the license key details were modified in any way.
Some encrypted data has been created or modified using configured, rather than default, encryption settings. This error occurs when that data is read by a component that does not have configured encryption settings – the component is therefore unable to decrypt the data.
It is necessary to configure the encryption settings in the component.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
184
13. Error and Status Codes
Table 100: Error Code List (continued)
Error
Code
Error Message
-251 STAT_WRONG_CIPHER
-252
-300
-350
STAT_DECRYPT_FAILURE
STAT_DB_ERROR
STAT_DISCARD_REQUEST
Description Notes
Decryption has failed - an incorrect
Cipher is specified in the Encryption
Settings
Decryption has failed - an incorrect
Storage Key is specified in the Encryption Settings
A database error occurred
The request received was discarded
Some encrypted data has been created or modified using differently configured encryption settings. This error occurs when that data is read by a component with configured encryption settings that use a different Cipher Name – the component is therefore unable to decrypt the data.
It is necessary to make sure that the encryption settings in all components are identical.
Some encrypted data has been created or modified using differently configured encryption settings. This error occurs when that data is read by a component with configured encryption settings that use a different Storage Key – the component is therefore unable to decrypt the data.
It is necessary to make sure that the encryption settings in all components are identical.
General-purpose error on a database operation. This should be supplemented with more specific details.
A replication update that was received was found to be superseded by a later change. In this case, the update is discarded, as it is no longer relevant.
This may occur when creating a record, after a record has been deleted and then re-created.
It may occur when modifying a record, if a later modification occurred before replication could apply the first change.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
185
13. Error and Status Codes
Table 100: Error Code List (continued)
Error
Code
Error Message
-351 STAT_RETRY_REQUEST
-352
-353
-400
-401
STAT_INVHASH
STAT_REPLQUEUE_FULL
STAT_NOTAVAIL
STAT_ADDR_RESOLVE
Description Notes
The request received must be retried
A replication queue entry had an invalid hash value
The replication queue is full
There was no comms descriptor available
The supplied address could not be resolved
A replication update that was received could not be applied immediately. In this case, the update is rejected. The retry mechanism at the source server will re-send the update, according to its configuration settings.
This may occur if a record does not exist yet, when trying to apply a modification or deletion.
It may occur after a record has been deleted and re-created, when a modification of the record is replicated but the sequence of deletion and re-creation has not been followed in the correct order.
When an entry was read from the replication queue before sending, its integrity hash value check failed. This suggests that the queue entry may have been modified since it was added to the queue. In this case, the queue entry is not trusted, and an error is reported.
An operation failed because it needed to update the database, but the update could not be added to the Replication queue. If the queue is full, no database updates are allowed, to avoid the databases from being pushed too far out of synchronization.
Check the Replication Status dialog in the
Active Directory Users and Computers
Extension and the Replication audit messages to investigate why the queue has become full. It is necessary to reduce the queue size for the system to continue to function.
If this error occurs often, without good reason, consider increasing the maximum queue size. This can be configured in the
Replication tab of the Configuration Utility.
The comms descriptor map has not been loaded. (Support)
Name resolution problem, i.e.a problem in the DNS, the netbios etc.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
186
13. Error and Status Codes
-408
-450
-500
-501
-550
-600
-601
-602
-650
-700
-800
-801
-404
-405
-406
-407
Table 100: Error Code List (continued)
Error
Code
Error Message
-402 STAT_SOCKET_ERR
-403 STAT_DESC_STATE
STAT_DESC_LIMIT
VDSERR_CLOSED
VDSERR_WOULDBLOCK
STAT_INPROGRESS
STAT_INV_DESCRIPT
STAT_INVKEY
STAT_ALREADY_STARTED
STAT_ALREADY_STOPPED
STAT_MALFORMED_DATA
STAT_RAD_INVATTRIB
STAT_RAD_SIZE
STAT_RAD_INVDICT
STAT_INIT_FAILED
STAT_OPEN_FAILED
VDSERR_BAD_PKT_LENGTH
VDSERR_MALLOC_FAIL
Description Notes
A socket error occurred. Descriptor should be closed
Descriptor was in the wrong state
Communication protocol mismatch.
Such a wrong state can for instance be to try binding the socket twice.
The maximum number of open descriptors has been reached
The connection has been closed by the remote end
The command would block, use
'select'
The command is in progress, use
'select'
The comms descriptor is not valid
The key received was invalid
The Service was already started
The Service was already stopped
An invalid comms descriptor can for instance be that the socket has not been created.
The encryption key is invalid.
When trying to start a service, the service was already running.
When trying to stop a service, the service was not running.
This error may be returned when a corrupt configuration file is used.
the RADIUS attribute field layout is invalid.
The config file/registry data could not be read
One of the RADIUS attributes was invalid
The action will result in a size limitation being exceeded
An invalid dictionary file was used
Initialization of lock failed
Failed to open handle
A buffer overflow would occur, this is only used within the RADIUS library
Normally occurs when a file cannot be opened.
An invalid length was supplied
Memory allocation failed
IDENTIKEY Appliance 3.11.12 - Administrator Reference
187
13. Error and Status Codes
Table 100: Error Code List (continued)
Error
Code
Error Message
-802 VDSERR_BLANK_PASSWORD
Description Notes
-903
-904
-999
-1001
-1002
-803
-1003
-1004
-1005
VDSERR_INV_PASSWORD
STAT_ENCRYPT_TYPE
STAT_BAD_PROTOCOL
STAT_NULL_PTR
STAT_UNKNOWN_PKTSOURCE
VDSERR_NOSECRET
STAT_RAD_BADAUTH
STAT_RAD_BADMSGAUTH
STAT_RAD_BADADDRESS
Password was blank
Password was invalid
Can occur when attempting to verify a MS-
CHAP/MS-CHAP2 password when the subsequently hashed password provided by the used is equivalent to hashing a blank string, i.e. the provided password is blank.
Occurs within MS-CHAP/MS-CHAP2 password verification when the provided password is incorrect and it is not a blank string.
The MPPE encryption policy is not supported
Invalid MPPE protocol used
A null pointer was received
The packet is from an unknown source A client component does not exist for the client who sent the packet.
The shared secret of the packet's source is unknown
There is no shared secret within the client component for the peer which sent this packet.
Incorrect response authenticator The response packet returned from the
RADIUS server bears an incorrect authenticator.
The Message-Authenticator attribute was not correct
The packet is not from the address sent to
The response from the back end does not match the source address to which the request was sent.
Active Directory Error -5300
-5301
-10057
STAT_ADERROR
STAT_INCSCHEMA
UA_USERID_TOO_LONG
-10059 UA_PASSWORD_TOO_LONG
-10060 UA_UNAME_TOO_LONG
User ID is longer than 255 characters.
Password is longer than 255 characters.
User name is longer than 64 characters.
The maximum user ID length has been exceeded.
The maximum password length has been exceeded.
The maximum user name length has been exceeded.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
188
13. Error and Status Codes
Table 100: Error Code List (continued)
Error
Code
Error Message
-10061 UA_SERIAL_TOO_LONG
-10062 UA_SERIAL_TOO_SHORT
-10063 UA_SERIAL_INVALID_CHARS
-10064 UA_ORGUNIT_TOO_LONG
-10065 UA_DOMAIN_TOO_LONG
-10066 UA_DN_TOO_LONG
-10067 UA_MOBILE_TOO_LONG
-10069 UA_USER_PARSE_ERROR
-10072 UA_PHONE_TOO_LONG
-10073 UA_EMAIL_TOO_LONG
-10074 UA_INVALID_USER_DETAILS
-10075 UA_MOBILE_INVALID_CHARS
Description Notes
Serial Number is longer than 10 characters.
Serial Number is less than 10 characters long.
Serial Number contains non-alphanumeric characters.
The Serial Number contains non-alphanumeric characters. Serial Number must be
10 alphanumeric characters, with no dashes
(-).
The maximum organizational unit length has been exceeded.
Organizational unit is longer than 255 characters.
Domain is longer than 255 characters.
The maximum domain length has been exceeded.
Distinguished Name is longer than
1024 characters.
The maximum LDAP Distinguished Name
(DN) length has been exceeded.
Mobile Number is longer than 64 characters.
A syntax error occurred reading from the file.
The maximum serial number length has been exceeded. The serial number must be
10 characters, with no dashes (-) and with leading zeros (0) to make it up to 10 characters.
The minimum Serial Number length has not been provided. Serial Number must be 10 characters, with no dashes (-) and with leading zeros (0) to make it up to 10 characters.
Phone Number is longer than 64 characters.
Email Address is longer than 64 characters.
No user ID was given. Either the user
ID or, for Active Directory, the Distinguished Name is needed to import a user.
The maximum length for the mobile phone number has been exceeded.
A syntax error occurred while reading lines from the import file: double-quotes were missing; there are too many fields in the line; a comma is missing between fields.
The maximum phone number length has been exceeded.
The maximum length for the e-mail address has been exceeded.
A user ID must be supplied to import a user.
The only exception is when using Active Directory, it is sufficient to give the distinguished name instead of the user ID.
The Mobile No. is invalid. Only numbers, spaces, dashes (-) and brackets are allowed with a + at the start to indicate a country code if needed.
The mobile number is only allowed to include numeric characters, spaces, dashes(-) and brackets (){}[]. In addition a + is allowed at the start for the country code.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
189
13. Error and Status Codes
Table 100: Error Code List (continued)
Error
Code
Error Message
-10076 UA_PHONE_INVALID_CHARS
-10077 UA_EMAIL_INVALID_CHARS
-10078 UA_USER_HEADER_ERROR
Description Notes
The Phone No. is invalid. Only numbers, spaces, dashes (-) and brackets are allowed with a + at the start to indicate a country code if needed.
The phone number is only allowed to include numeric characters, spaces, dashes(-) and brackets (){}[]. In addition a + is allowed at the start for the country code.
The specified email address contains invalid characters and is not in the form user@domain.
The Field Header was not found or invalid when reading from the file.
The e-mail address is only allowed to include alphanumeric characters, @, dots (.), underscores (_) and dashes (-).
The first line of an import file must be a header line. The header line is a comma-separated list of field names, indicating which fields are included in every other line of the file.
This message indicates that the header line was not found, that it included unknown field names, or that it was not a comma-separated list of field names.
See the Import User Records topic in the online help for the Active Directory Users and
Computers Extension for a definition of the import file header format.
13.2. DIGIPASS Authentication for Windows Logon Error Messages
Table 101: DIGIPASS Authentication for Windows Logon Error Messages
Error
Code
Message Notes
-750 An SSL Error has occurred
-751 SSL Certificate has expired
-752 SSL Certificate not trusted
-753 SSL certificate was rejected because its key usage does not permit certificate signing.
-754 SSL handshake timed out. This can occur when connecting to a non-
SSL port.
The server certificate is no longer valid and should be regenerated.
The authority used for the server certificate is not included in the machine's Certificate
Authority.
Self-signed certificates may be used as both Certificate Authority (signing) certificates and server certificates. Commercial certificates require a separate Certificate Authority certificate.
Check client and IDENTIKEY Appliance configuration to ensure that the client is connecting to IDENTIKEY Appliance using the secure port.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
190
13. Error and Status Codes
13.3. VACMAN Controller Error Codes
140
141
142
143
144
137
138
139
145
146
147
148
132
133
134
135
136
0
1
130
131
The error codes in the table below are returned by IDENTIKEY Appliance's authentication core product, VACMAN
Controller . They may occur in trace and audit messages.
Table 102: VACMAN Controller Error Codes – Authentication and
Administration
Code Message success failure invalid response pointer missing required challenge unsupported tokentype invalid randomnumber pointer invalid unlockcode pointer invalid challenge pointer invalid challengelength pointer challenge not supported unlock function not supported invalid signature pointer challenge corrupted invalid fieldcount invalid testcode pointer invalid hostdatetime pointer invalid clockshift pointer invalid challengemsg pointer invalid masterkey pointer invalid activationcode pointer invalid data fields pointer
IDENTIKEY Appliance 3.11.12 - Administrator Reference
191
Table 102: VACMAN Controller Error Codes – Authentication and
Administration (continued)
Code Message
161
162
163
156
157
158
159
160
153
154
155
149
150
151
152
201
202
203
164
165
166
167
179
204
205 invalid iv length invalid derivation data length invalid kcv length invalid datafield pointer invalid event window invalid data block size invalid time window obsolete hash data block invalid hash data block invalid salt pointer invalid state data block pointer invalid hash data block pointer invalid key pointer salt buffer too big key buffer too big invalid serial number suffix invalid response length
Missing Required CESPR
Input Data Corrupted (Challenge or CESPR) session handle invalid code replay attempt ident error threshold reached sign error threshold reached duplicate signature found inactive days reached
IDENTIKEY Appliance 3.11.12 - Administrator Reference
13. Error and Status Codes
192
Table 102: VACMAN Controller Error Codes – Authentication and
Administration (continued)
Code Message
310
311
312
313
314
307
308
309
315
316
317
302
303
304
305
306
272
300
301
209
210
211
206
207
208 sign sync error invalid use of onlinesg flag application disabled grace period expired allowed use count reached virtual token not supported invalid wrapped key user database open error token database open error log open error dgpparms open error token database update error user database update error token database pointer invalid user database pointer invalid token database insert error user database insert error database eof reached token database locate error user database locate error token database getnext error user database getnext error dgpparms update error dgpparms pointer invalid dgpparms insert error
IDENTIKEY Appliance 3.11.12 - Administrator Reference
13. Error and Status Codes
193
Table 102: VACMAN Controller Error Codes – Authentication and
Administration (continued)
Code Message
405
407
408
400
401
402
403
404
322
323
324
318
319
320
321
500
501
505
409
410
412
413
414
506
507 dgpparms locate error dgpparms getnext error dgpparms erase error token database erase error sglog database open error sglog database pointer invalid sglog database insert error response only codeword not found signature codeword not found challenge response codeword not found application table is empty requester table is empty application not found tokentype not found wrong application count wrong requester count wrong requester application number invalid checksum invalid base64 format invalid checksum hsm init key not verified bad init key length serial checkdigit invalid invalid cinit handle pointer invalid cini hdr pointer
IDENTIKEY Appliance 3.11.12 - Administrator Reference
13. Error and Status Codes
194
Table 102: VACMAN Controller Error Codes – Authentication and
Administration (continued)
Code Message
532
533
534
535
536
523
530
531
537
538
539
517
518
520
521
522
514
515
516
511
512
513
508
509
510 invalid header record invalid cini data pointer invalid digipass data pointer invalid serial number pointer invalid authmode pointer invalid data record invalid digipass info pointer invalid digipass type pointer invalid key set pointer invalid property value invalid property required parameter not found required parameter empty license not verified keyword not found invalid qa data pointer invalid qa security level invalid qa data length invalid userid pointer invalid userid length invalid qa nb invalid encrypted qa data invalid staticvector pointer invalid alea pointer invalid snsuffix pointer
IDENTIKEY Appliance 3.11.12 - Administrator Reference
13. Error and Status Codes
195
Table 102: VACMAN Controller Error Codes – Authentication and
Administration (continued)
Code Message
556
557
558
551
552
553
554
555
544
545
550
540
541
542
543
564
565
600
559
560
561
562
563
601
602 invalid qakey pointer invalid index list invalid hash list invalid dp4web blob invalid activation code length invalid static vector length null master key label pointer null master key kcv pointer null derivation seed pointer null derivation key kcv pointer null tlv data pointer null auth mode pointer null master key reference null encryption key reference null encryption key kcv pointer invalid seed length null output buffer
Invalid matrix card sequence number
Invalid row number
Invalid column number
Invalid security level
Invalid static vector in dpx file invalid gordian root information invalid gordian today information invalid gordian tomorrow information
IDENTIKEY Appliance 3.11.12 - Administrator Reference
13. Error and Status Codes
196
Table 102: VACMAN Controller Error Codes – Authentication and
Administration (continued)
Code Message
810
811
812
813
814
807
808
809
900
901
902
802
803
804
805
806
706
707
801
703
704
705
603
701
702 invalid gordian stimulus information invalid input buffer pointer invalid hash buffer pointer invalid hash algorithm invalid hash length invalid hash format invalid data buffer pointer invalid data length pointer static pwd not supported change pwd mandatory new pwd too small new pwd too long pwd not equal static pwd chg not supported serial not equal invalid appl count
Encrypted Static Password Not Supported unlock authentication failure invalid unlockauthcode pointer invalid unlockauthindex unlockauthcode too small unlockauthcode too long hsm null session hsm invalid state hsm invalid session fm
IDENTIKEY Appliance 3.11.12 - Administrator Reference
13. Error and Status Codes
197
Table 102: VACMAN Controller Error Codes – Authentication and
Administration (continued)
Code Message
910
911
912
913
916
917
1002
1003
907
908
909
903
904
905
906
1006
1007
1008
1009
1018
1019
1025
1039
1040
1100 hsm key id fm hsm max session fm hsm initialisation failed hsm opensession failed hsm not initialized hsm key not found hsm invalid slotid hsm invalid command in reply hsm invalid key kcv hsm invalid blob status hsm invalid key property pkcs11 find process error key type inconsistent compression hdr too big compression src too big tlv length too long tlv invalid tag tlv invalid length tlv invalid tot len tlv invalid item pointer tlv missing mandatory item buffer too small invalid response length with DP algorithm invalid host code length with DP algorithm function not supported
IDENTIKEY Appliance 3.11.12 - Administrator Reference
13. Error and Status Codes
198
Table 102: VACMAN Controller Error Codes – Authentication and
Administration (continued)
Code Message
-206
-207
-301
-302
-401
-203
-204
-205
-508
-509
-510
-143
-151
-152
-201
-202
-106
-107
-108
-102
-103
-105
1101
1103
-101 emv not supported
Unlock Version 2 Not Supported
Challenge Too Small
Challenge Too Long
Challenge Check Digit Wrong
Challenge Minimum Length Not Allowed
Challenge Maximum Length Not Allowed
Challenge Number Wrong
Challenge Character Invalid
Change PIN Mandatory
CESPR Too Small
CESPR Too Long
Response Length Out Of Bounds
Response Too Small
Response Too Long
Response Check Digit Wrong
Response Character Not Decimal
Response Character Not Hexadecimal
Response Character Set Not Specified
Time Most Execution Failed
Time Next Execution Failed
Event Most Execution Failed
Token Type Not Supported
Response Type Not Allowed
Invalid Record
IDENTIKEY Appliance 3.11.12 - Administrator Reference
13. Error and Status Codes
199
Table 102: VACMAN Controller Error Codes – Authentication and
Administration (continued)
Code Message
-511
-1501
-2201
-2202
Wrong Record CRC
Memory Allocation Failed error sernumber not alpha error deskey parity
Table 103: VACMAN Controller Error Codes - DIGIPASS record import
Code Meaning
-23
-24
-30
-20
-21
-22
-11
-12
-13
-14
-15
0
100
107
-10
Success
Success – token complete
Success – end of file reached
Error null pointer
Error bad argument
Error DPX clear failed
Error des calculation
Error InitKey length
Error InitKey value
Error file open failed
Error file close failed
Error file rewind failed
Error file not open
Error file not closed
Error fatal error
IDENTIKEY Appliance 3.11.12 - Administrator Reference
13. Error and Status Codes
200
Table 103: VACMAN Controller Error Codes - DIGIPASS record import (continued)
Code Meaning
Error file has errors
Error too many errors
Error too many info
Error void text
Error truncated text
Error no DF records
Error unexpected record
Error bad record type
Error unexpected content
Error line exhausted
Error missing quotes
Error missing field name
Error bad field name
Error bad field type
Error field size
Error line size
Error DH file content
Error DH date content
Error DH version content
Error DH created by content
Error DC HSH content
Error DC DEL content
Error HSH value
Error DEL value
-49
-50
-51
-44
-45
-46
-47
-48
-41
-42
-43
-31
-32
-33
-40
-200
-201
-202
-203
-52
-100
-101
-102
-103
IDENTIKEY Appliance 3.11.12 - Administrator Reference
13. Error and Status Codes
201
Table 103: VACMAN Controller Error Codes - DIGIPASS record import (continued)
Code Meaning
-803
-804
-900
-503
-504
-800
-801
-802
-500
-501
-502
-300
-301
-400
-401
-1503
-1504
-1505
-1506
-901
-902
-1500
-1501
-1502
Error DF fieldname
Error DF descriptor
Error DA record
Error DA field
Error DP field value
Error DP descriptor
Error DP unknown descriptor
Error DP record redefinition
Error DP record overflow
Error CT field type
Error CT name redefinition
Error CT fieldlength
Error CT fieldname
Error CT too many entries
Error DE def records content
Error DE data records content
Error DE tokens content
DPX cannot allocate memory
DPX null handle
DPX null handle context
DPX null handle key
DPX invalid handle context eyecatcher
DPX invalid handle key eyecatcher
DPX invalid selected application
IDENTIKEY Appliance 3.11.12 - Administrator Reference
13. Error and Status Codes
202
Table 103: VACMAN Controller Error Codes - DIGIPASS record import (continued)
Code Meaning
-1514
-1515
-1516
-1517
-1518
-1519
-1520
-1521
-1507
-1508
-1509
-1510
-1511
-1512
-1513
-1527
-1528
-1530
-1531
-1522
-1523
-1524
-1525
-1526
DPX null selected application
DPX null init key
DPX null file name
DPX application not define
DPX null appli count
DPX null appli names
DPX null token count
DPX null serial number
DPX null DPX type
DPX null authentication mode
DPX nullDIGIPASS data
DPX null key name
DPX null key KCV
DPX invalid static vector length
DPX null output buffer
DPX invalid static vector
Invalid response length with DP algorithm
Invalid return host code length with DP algorithm
DPX unlock mixed versions
DPX invalid unlock challenge length
DPX invalid unlock code type
DPX invalid unlock code length
DPX EMV HSM not supported
DPX EMV SSM not supported
IDENTIKEY Appliance 3.11.12 - Administrator Reference
13. Error and Status Codes
203
13. Error and Status Codes
13.4. Console Wizard Error Codes
The error codes in the table below are returned by IDENTIKEY Appliance's console wizard. This is to enable development of software relating to the console wizard.
Table 104: Console Wizard Error Codes
Code Message
3
4
1
2
0
1
0
The wizard was correctly initialized, however errors could have occurred.
Either the terminal was not sufficiently large enough (80 x 24) or the command line was invalid.
Wizard completed successfully.
Internal error or missing file
Internal error
User supplied invalid data on a page
Internal Error
5
6
Internal Error
DNS Failure
7
9
License could not be found or does not match installation.
Page failed to complete required configuration process
10 Invalid or missing answers file
11 User aborted
12 Failed to parse command line switches
13 Terminal does not meet minimum requirements (80 x 24)
14 This error can occur if the user is trying to keep an old cert during an upgrade process but the cert does not exist.
Name eRS_SUCCESS eRS_MISSING_PAGE eRS_PAGE_INVALID eRS_DISPLAY_ERROR eRS_TRANSFER_ERROR eRS_NETWORK_ERROR eRS_LICENSE_ERROR eRS_ACTION_FAILED eRS_ANSWERS_READ_
FAIL eRS_USER_CANCELLED eRS_BAD_
COMMANDLINE eRS_BAD_TERMINAL eRS_MISSING_CERT
Any other error codes are invalid and caused by unknown circumstances.
Be aware that some operating system command shells will convert the error code to an unsigned char i.e. (256 + code) mod 256
IDENTIKEY Appliance 3.11.12 - Administrator Reference
204
13. Error and Status Codes
13.5. Status Codes
Table 105: Status Codes List
Status
Code
Status Message
0
<all negative codes>
1000 STAT_INVCREDENTIALS
1002 STAT_GROUPCHK
1004 STAT_EXP_CHALLENGE
1005 STAT_PERMISSION
1006 STAT_LOCALAUTH
Description Notes
No error
<Error Code>
The credentials were invalid
The user failed the Windows Group
Check
The challenge has expired
The user does not have permission to perform the specified action
The status codes from -1 downwards match to a corresponding error code.
General-purpose failure due to invalid user name or password, when a more specific status is unavailable.
The IDENTIKEY Authentication Server rejected an authentication request due to the Windows Group Check failing. This can occur when the effective Windows Group Check option is Authenticate listed groups, reject others.
Note that the effective setting is the effective setting of the policy, unless the DIGIPASS user account overrides the policy.
A response to challenge has been given, but the expiration time for the challenge has expired. The default expiration time is one minute, however this can be configured in the configuration file VASCO/Challenge-
Cache/Max-Age setting (in seconds).
General-purpose failure of an administration command when the administrator does not have sufficient privileges to carry out the command.
The DIGIPASS Authentication Library is not responsible for this authentication
IDENTIKEY Appliance 3.11.12 - Administrator Reference
205
13. Error and Status Codes
Table 105: Status Codes List (continued)
Status
Code
Status Message
1007 STAT_LOCKED
Description
The user account is locked
1008
1009
1010
1011
1012
1013
Notes
STAT_REPLAY
STAT_DISABLED
STAT_USER_UNKNOWN
STAT_LOCAL_PASSWORD_
MISMATCH
STAT_OTP_INCORRECT
STAT_CHALLENGE_INVALID
The one-time password has already been used
The user account is disabled
No user account was found
The static password was incorrect
The one-time password was incorrect
The challenge was invalid
The DIGIPASS user account is locked. This is normally due to consecutive login failures, as determined by the policy setting User Lock
Threshold. Alternatively, the administrator can actively lock the account.
To unlock the user account, an administrator has to uncheck the Locked check box on the user record.
This status code occurs specifically when an
OTP is rejected because it has already been used. It may also occur when the OTP has not been used but is older than the most recently used OTP.
This can sometimes happen when an authentication request is re-sent automatically.
The DIGIPASS user account is disabled. This may be because the administrator has actively disabled the account, or because the corresponding Windows user account has become disabled or expired.
An authentication request was rejected because no DIGIPASS user account was found and the policy requires local authentication.
As part of local authentication, verification of the static password failed.
Verification of the OTP failed. More specific details may be found in the VACMAN Controller error code and message.
A response to a challenge was given, but the challenge was not the latest one issued for that DIGIPASS. This is controlled by the Check
Challenge Policy setting.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
206
13. Error and Status Codes
Table 105: Status Codes List (continued)
Status
Code
Status Message
1014 STAT_GRACE_PERIOD_
EXPIRED
Description
The DIGIPASS grace period has expired
1015
1016
STAT_BVDP_NOT_ALLOWED Backup Virtual DIGIPASS is not allowed
STAT_DIGIPASS_NOT_
AVAILABLE
The DIGIPASS is not available
Notes
A user attempted to log in with their static password, but their grace period had already expired. They have to use a DIGIPASS to log in.
If they do not have their DIGIPASS yet, the administrator will have to allow them more time by modifying the Grace Period End date on their DIGIPASS record.
A user attempted to request a Backup Virtual
DIGIPASS OTP, but they were not permitted.
This would normally occur when either: n n
The effective Backup Virtual
DIGIPASS Enabled setting is Yes –
Time Limited, and the DIGIPASS
Backup Virtual DIGIPASS Enabled
Until date is the current date or before.
The DIGIPASS Backup Virtual
DIGIPASS Uses Remaining counter has reached 0.
In both cases, administrator intervention is required to permit the user to continue to use
Backup Virtual DIGIPASS. The Enabled Until or Uses Remaining limits need to be increased to permit this.
Note that the effective setting is the effective setting of the policy, unless the DIGIPASS record overrides the policy.
A user attempted Self-Assignment, but the
DIGIPASS they requested either could not be found within the search scope or was already assigned to someone else.
This may occur because of a mistyped Serial
Number. Otherwise, the search scope may be incorrect, or the DIGIPASS may not be in the correct location to be made available to the user. See the DIGIPASS Records Location section in the IDENTIKEY ApplianceProduct
Guide .
IDENTIKEY Appliance 3.11.12 - Administrator Reference
207
13. Error and Status Codes
Table 105: Status Codes List (continued)
Status
Code
Status Message
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
Description Notes
STAT_INVALID_MDC_
SETTINGS / STAT_INVALID_
VDP_SETTINGS
STAT_VDP_PASSWORD_
MISSING
STAT_CONFIRM_PASSWORD_
MISMATCH
STAT_LOCAL_AUTH_REJECT
STAT_BACKEND_PWD_
EXPIRED
STAT_BACKEND_REJECT_
STORED_PASS
STAT_BACKEND_REJECT_
SUPPLIED_PASS
STAT_PASSWORD_FAIL_
STRENGTH_CHECK
STAT_DIGIPASS_EXPIRED
STAT_PASSWORD_EXPIRED
The user account has no mobile number for Virtual DIGIPASS
No password was supplied for a Virtual
DIGIPASS login
The new password confirmation failed
Local authentication failed
Back-end authentication reported that the password has expired
Back-end authentication failed
A user requested a Primary or Backup Virtual
DIGIPASS OTP, but it could not be delivered because the user account had no mobile phone number. In Active Directory this is the first mobile number in the record.
A user attempted a Virtual DIGIPASS login, but did not enter a password in the second stage of the login. For more information, refer to Section
10.2.4. 2-Step Virtual DIGIPASS
In a password change request, the new password was not confirmed correctly.
General-purpose failure of Local Authentication when a more specific status code is not available. Additional information should provide more specific details.
Back-End Authentication (e.g. Windows) failed because the password was correct but it has expired.
Back-End Authentication (e.g. Windows) failed. A specific error code and message will accompany this record.
Back-end authentication failed with supplied password
The static password failed to comply with the strength rules of IDENTIKEY
Authentication Server. Please check your policy settings.
The following are violations of the password strength rules: n n n n
Password length is incorrect.
Password does not contain a sufficient number of unique characters.
The same password has already been used (too) recently.
The password does not comply with any other of the password policy requirements.
The DIGIPASS authenticator has expired.
The static password for local authentication in mode DIGIPASSor Password has expired.
The user attempted to login but the static password has expired.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
208
13. Error and Status Codes
Table 105: Status Codes List (continued)
Status
Code
Status Message
1030 STAT_INVALID_POLICY
Description
The policy was invalid
1031
1032
1033
STAT_SELF_ASSIGN_
DISABLED
STAT_HASH_PWDS_
DISALLOWED
STAT_DIGIPASS_MUST_BE_
USED
Notes
The policy does not allow a self-assignment attempt
Hashed passwords cannot be verified by
Windows
A DIGIPASS must be used
An authentication request was rejected because the applicable policy had invalid settings or failed to load. This should not occur, but is possible due to the delay in Active Directory replication for example. The two main ways in which a policy can become invalid are:
One or more choice list settings are Default in the policy, and its parent policy if it has one.
A circular chain of Policies has been created, for example: Policy A inherits from Policy B;
Policy B inherits from Policy C; Policy C inherits from Policy A.
The policy must be fixed for authentication to be permitted using that policy.
A user attempted Self-Assignment, but it is not permitted under the policy.
An authentication request could not be processed successfully because Back-End
Authentication using Windows was required, but the user's password was hashed. It is not possible to verify hashed passwords with Windows. This can occur when a CHAP-based protocol is used – this includes CHAP, MS-CHAP, MS-CHAP2, EAP-
MD5 and other more complex protocols that utilize a one-way hash of the password entered by the user.
Note that the effective back-end authentication setting is the effective setting of the policy, unless the DIGIPASS user account overrides the policy.
The effective Local Authentication setting is
DIGIPASS Only and the user tried to log in with a static password.
Note that the effective setting is the effective setting of the policy, unless the DIGIPASS user account overrides the policy.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
209
13. Error and Status Codes
Table 105: Status Codes List (continued)
Status
Code
Status Message
1034 STAT_NO_CHALLRESP_FOR_
CHAP
Description
Challenge/Response is not supported by
CHAP-based protocols
1035
1036
1037
1038
1039
Notes
STAT_NO_CHALLRESP_FOR_
W2K / STAT_NO_CHALLRESP_
FOR_W_2_K
Challenge/Response is not supported by
Windows 2000
STAT_1STEP_CR_DISABLED /
STAT_1_STEP_CR_DISABLED
STAT_AUTOLEARN_DISABLED
STAT_SOURCE_LOCATION_
MISMATCH
STAT_ADMIN_SESSION_
STOPPED
1-Step Challenge/Response is disabled
Password Autolearn is disabled
The administration session ID is not known at this location
The administration session is no longer active
Challenge/Response is only supported in
RADIUS using the PAP protocol. An attempt was made to generate a challenge using a
CHAP-based protocol – this includes CHAP,
MS-CHAP, MS-CHAP2, EAP-MD5 and other more complex protocols.
This status code can only occur in the
DIGIPASS plug-in for Microsoft Internet
Authentication Service. For Windows 2000 a product limitation inhibits the support of the
Challenge/Response mode. This will occur if the user has attempted to request a challenge.
A request was made to generate a random challenge for 1-step Challenge/Response, but the applicable policy does not have 1-step
Challenge/Response enabled or does not specify the challenge length and check digit indicator.
A request was made to update a user's stored password, but Password Autolearn is disabled, so the update is not permitted. Password Autolearn must be enabled for the password update request to be processed.
An administration command has been received, but the internal session ID is not recognized at the location from which the command came. This can only occur by attempting to reuse a session ID from another location.
An administration command has been received, but the session has stopped or is unrecognized. This can occur due to an idle timeout, a maximum session length timeout or a restart of the IDENTIKEY Appliance.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
210
13. Error and Status Codes
Table 105: Status Codes List (continued)
Status
Code
Status Message
1040
1041
1042
Description Notes
STAT_NO_CHALLRESP_FOR_
PWDPROXY
STAT_DIGIPASS_NOT_FOUND
STAT_NO_BACKEND_FOR_
SELF_ASSIGN
Back-end authentication returned a Challenge that cannot be handled
No DIGIPASS was found for the given
Serial Number
Self-Assignment was attempted but
Back-End Authentication did not occur to authenticate the static password
This can occur when the IDENTIKEY Appliance forwards a request to a RADIUS Server and the RADIUS Server responds with an
Access-Challenge. An Access-Challenge can only be handled when the IDENTIKEY Appliance forwards the password unmodified to the RADIUS Server. If the IDENTIKEY Appliance 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 a Microsoft IIS Module. In that case, Access-Challenge is not supported from the RADIUS Server.
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.
Self-Assignment is not allowed without Back-
End Authentication. This is required to validate the static password.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
211
13. Error and Status Codes
Table 105: Status Codes List (continued)
Status
Code
Status Message
1050 STAT_REACTIV_NOT_
ALLOWED
Description
Reactivation is not allowed
1051
1052
1053
1054
STAT_TOO_MANY_DIGIPASS
STAT_NO_PROV_
PASSWORD_DEFINED
STAT_NO_DP_FOR_ASSIGN
STAT_GEN_ACTIVATION_
CODE
Notes
Multiple DIGIPASS found where a single
DIGIPASS was required
The user account has no static password to encrypt the activation code
No DIGIPASS was available for assignment
Error generating activation code
A reactivation attempt was refused for one of the following reasons: n n n
The DIGIPASS has already been activated from the maximum number of allowed locations. This limit is controlled by the configuration setting Max Locations of the provisioning scenario.
The maximum number of allowed activation attempts has already been reached. This limit is controlled by the Provisioning Scenario configuration setting Max
Attempts.
The minimum time interval required between activation attempts has not yet been reached since the last activation attempt.
This limit is controlled by the configuration setting Min Interval of the provisioning scenario.
An activation attempt was made where the user had two or more DIGIPASS that could be used. The activation request did not specify which DIGIPASS should be used to handle the request.
If no Local Authentication or Back-End
Authentication is done during an activation request, a static password is required from the DIGIPASS user account. The password is used to encrypt the activation code.
No available DIGIPASS was found for the Provisioning Register request. The DIGIPASS must be capable of activation and meet the
DIGIPASS restrictions in the policy settings if any.
Generation of an activation code for provisioning failed. More specific details may be found in the
.
1055 STAT_READING_SVF Error reading SVF data
IDENTIKEY Appliance 3.11.12 - Administrator Reference
212
13. Error and Status Codes
Table 105: Status Codes List (continued)
Status
Code
Status Message
1060 STAT_SIGNATURE_
INCORRECT
Description
The Signature failed validation
1061
1062
STAT_SIGNATURE_REPLAY
STAT_DP_NOT_HOSTCONF_
CAPABLE
Notes
The Signature has already been used
A Host/Confirmation Code is required but the DIGIPASS Application is not able to generate it
Verification of the signature failed. More specific details may be found in the
.
This status code occurs specifically when a signature is rejected because it has already been used. It may also occur when the signature has not been used but is older than the most recently used signature.
This behavior depends on the effective
Online Signature Level Policy setting.
For an authentication request, a host code was required to be returned. The DIGIPASS
Application for which the OTP was validated was not capable of generating a host code.
For a signature validation request, a confirmation code was required to be returned.
The DIGIPASS Application for which the signature was validated was not capable of generating a confirmation code.
The .dpx
file that was used to import the
DIGIPASS Application controls whether the host or confirmation code can be generated.
1070
1090
1100
1101
1102
1103
STAT_CHANGE_ENCRYPTED_
PASSWORD
STAT_MISSING_BACKEND_
PROTOCOL
STAT_ERROR_GENERATE_
REGISTRATION_ID
Error while process changed encrypted static password
INPUT missing: Back-End Protocol ID
STAT_ERROR_GENERATE_
ACTIVATION_PASSWORD
STAT_REGISTERID_NOT_IN_
CACHE
STAT_FAIL_ENCRYPT_
ACTIVATION_CODE
The DIGIPASS Software Advanced Provisioning Protocol (DSAPP) server failed to generate the registration identifier.
The DIGIPASS Software Advanced Provisioning Protocol (DSAPP) server failed to generate the activation password.
The matching registration identifier could not be found in the provisioning system cache.
The DIGIPASS Software Advanced Provisioning Protocol (DSAPP) server failed to encrypt the activation data.
The back- end server group is missing a back-end protocol ID.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
213
13. Error and Status Codes
Table 105: Status Codes List (continued)
Status
Code
Status Message
1104
1105
STAT_FAIL_VERIFY_SERVER_
NONCE
STAT_FAIL_BIND_DEVICE
1107
1120
1121
1122
1123
1124
3001
STAT_FAIL_BIND_DEVICE_
NOT_SUPPORTED
STAT_NOTIFICATION_
DELIVERY_FAILED
STAT_USER_SYNC_FAILED
STAT_BACKEND_
PASSWORD_FAIL_
STRENGTH_CHECK
STAT_DATA_RECORD_
VERSION_UNSUPPORTED
STAT_DATA_RECORD_
MIGRATION_FAILED
STAT_DP_CHALLENGE
Description Notes
The encrypted server nonce received from the client could not be validated.
This status code is returned in those cases: n n n
The DIGIPASS authenticator is already bound to a device.
The device cannot be bound.
The activation data cannot be generated.
The DIGIPASS authenticatordoes not support device binding.
A notification for delayed activation could not be sent, because no destination attribute is specified in the user account.
In addition, an audit message W-009002 is recorded.
User information attribute synchronization failed.
In addition, an audit message W-016004 is recorded.
The password does not comply with the strength rules of the back end.
The following are violations of the password strength rules: n n n n
Password length is incorrect.
Password does not contain a sufficient number of unique characters.
The same password has already been used (too) recently.
The password does not comply with any other of the password policy requirements.
In addition, an audit message E-013004 is recorded.
Data migration is enabled, but the migration subsystem is unable to handle the data record. This usually happens if the record data version is unsupported.
Data migration is enabled, but the migration subsystem cannot migrate the data record. This usually happens if the data migration failed due to an error.
A DIGIPASS Challenge was returned
In addition, an audit message E-013003 is recorded.
This status code is the standard code when a challenge is issued and does not indicate any kind of error.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
214
13. Error and Status Codes
Table 105: Status Codes List (continued)
Status
Code
Status Message
3002
3003
5001
5002
5003
Description Notes
STAT_NO_CHALLENGE No challenge was identified for the authentication
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.
STAT_BACKEND_CHALLENGE Back-end authentication returned a Challenge
This occurs when a RADIUS Server responds with an Access-Challenge, in a case where
IDENTIKEY Appliance can handle it.
STAT_NOT_IN_GROUPS The user failed the Windows Group
Check
IDENTIKEY Appliance 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.
STAT_NO_LOCAL_OR_
BACKEND_AUTH
STAT_DP_EXIST_AS_DIFF_
TYPE
Neither local nor back-end authentication was done due to policy and/or user settings
DIGIPASS exists as different DIGIPASS type
IDENTIKEY Appliance 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.
The DIGIPASS authenticator used exists as a different DIGIPASS type in the system.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
215
14. Tracing
14. Tracing
The level, method and location of tracing for the IDENTIKEY Appliance can be configured using the Configuration
Utility. Tracing information is saved to one or more text files.
14.1. Tracing Message Types
Tracing Messages are divided in to the following types:
Table 106: Tracing Message Types
Message Type
Code
Notes Examples
[CRITC]
[MAJOR]
Critical error/warning
Major error/warning
[MINOR]
[CONFG]
[ALERT]
[INFO]
[VINFO]
[DATA]
[TEMP]
[RESRC]
Minor error/warning
Configuration/initialization
Alerts
Informational messages
Verbose informational messages
Data tracing
Temporary data values
Resource usage
[MAJOR] > Failed to execute command. Error <Action denied:The static password was incorrect>
[MINOR]> Cannot get License Key from Component record
[CONFG] > ODBC Database audit plugin is successfully loaded
[CONFG] > Component cache configured as: max age : 900 max size : 1000 clean threshold : 800 min clean interval : 60
[ALERT] > disconnecting from server.
[INFO ] > Audit: {Info} {Initialization} {I-002002} {The DIGIPASS
Authentication library has been initialized successfully.}
[INFO ] > Creating DIGIPASS object.
[VINFO] > Event log source is < 3 {Application}>
[VINFO][ODBCConnection::OpenConnection] > Established connection to ODBC database
[DATA ] > Prepared SQL statement "SELECT vdsDomain, vdsDescription, vdsCreateTime, vdsModifyTime FROM vdsDomain ORDER BY vdsDomain"
[TEMP ] > Updated list is <APPLI 1>
[RESRC] > Socket <0> Bound to <10.2.2.33 : 20006>
IDENTIKEY Appliance 3.11.12 - Administrator Reference
216
14. Tracing
Table 106: Tracing Message Types (continued)
Message Type
Code
Notes Examples
[DEBUG] Debugging (useful for support purposes)
[DEBUG] > Registering Binary <D:\Program
Files\VASCO\\Bin\dpaudit.dll> with Event log <Application> for Source < 3 {Application}>
[DEBUG] > Committed transaction
[SECUR]
[LOCAT]
Security messages, messages that may contain security sensitive data
Stack location [LOCAT][0x00000000][ODBCStatemend::BindString]>
Encoding of string: UTF-16LE
[COUNT] Reference count
14.2. Tracing Levels
There are three tracing levels available when configuring tracing from the Configuration Utility – Basic, Full, and
Debug. The message types recorded by each level are shown in the table below.
Note
Debug tracing level is only for use when VASCO Customer Support have specifically requested its use.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
217
14. Tracing
Table 107: Tracing Message Levels
Basic Full
CRITC CRITC CRITC
Debug
MAJOR MAJOR MAJOR
MINOR
CONFG
ALERT
INFO
DATA
TEMP
RESRC
DEBUG
SECUR
MINOR
CONFG
ALERT
INFO
VINFO
DATA
TEMP
RESRC
DEBUG
SECUR
LOCAT
COUNT
MINOR
CONFG
ALERT
INFO
VINFO
14.3. Tracing Messages
Basic and Full tracing levels output different amounts of information in trace messages.
Table 108: Tracing Message Contents
Trace Level Message Contents
Basic
Full
Debug
[date_time] [thread ID] [level code] message
[date_time] [thread ID] [level code] [internal function name] message
[date_time] [thread ID] [level code] [key] [internal function name] message
Note
Any timestamp that appears in a Tracing Message is in UTC time, not local time. The letters UTC appear after the timestamp in the tracing message.
IDENTIKEY Appliance 3.11.12 - Administrator Reference
218
15. Support Procedure
15. Support Procedure
If you have problems with or questions about a VASCO product, follow the steps below:
1. Check if your problem has been resolved in the online knowledge base at http://www.vasco.com/support .
2. If you are unable to solve your problem with the Knowledge Base, please contact the company which sold you the VASCO product.
3. If your supplier is unable to solve your query, they will automatically contact the appropriate VASCO expert.
If necessary VASCO experts can access your IDENTIKEY Appliance remotely to solve any problems. Remote support and access to your IDENTIKEY Appliance are achieved through the VASCO Customer Portal.
For more information about remote support and the VASCO Customer Portal, refer to the IDENTIKEY Appliance
Product Guide .
IDENTIKEY Appliance 3.11.12 - Administrator Reference
219
Index
Index
A
ADUCE alea
Audit System
Audit Viewer
Autolearn
Password Autolearn
B
Back-End Protocol
C
Challenge/Response
1-Step Challenge/Response
2-Step Challenge/Response
CHAP
Check Digit
Cleartext Separate
Communicator cryptographic signature
CSV
Secure Auditing file plugin
D data fields dictionary
RADIUS
E
EAP effective settings
EMV-CAP event-based event counter
G
Group Check
H
HTTP header
X-Forwarded-For (XFF)
I
IIS module
L
License Key
Licensing load balancer
Login Permutations
M
Microsoft Point-to-Point Encryption (MPPE) monitoring
Net-SNMP
Performance Monitoring tool system monitoring targets
MS-CHAP
MS-CHAP2
Multi-Mode
P
PAP
Password
Policy
PEAP
Policy login settings ports open ports on firewall proxy server
R
RADIUS
Attributes character encoding dictionary
S
Serial Number
55, 76, 87, 94, 138, 153-154, 189, 207
Serial Number Separator
static passwords
IDENTIKEY Appliance 3.11.12 - Administrator Reference
Index
System Monitoring targets
T targets
System Monitoring
V
Virtual DIGIPASS
2-Step Virtual DIGIPASS Login
W
Windows Group Check
Index
IDENTIKEY Appliance 3.11.12 - Administrator Reference
Download
Advertisement
Key features
Authentication Management
Provisioning Control
Security Configuration
Audit and Logging
System Monitoring
Remote Administration
Certificate Management
Frequently asked questions
IDENTIKEY Appliance is a device used for managing and monitoring authentication requests. It controls access to various resources and systems within a network. The appliance ensures secure authentication by verifying user credentials and enforcing access policies.
The configuration is done through the IDENTIKEY Appliance Configuration Tool. The tool provides an interface for setting up parameters such as network settings, logging, notifications, and security configurations.
IDENTIKEY Appliance supports various authentication methods, including RADIUS, SOAP, and SEAL. It also allows for offline authentication and provisioning of DIGIPASS devices.
The appliance comes with performance monitoring capabilities. You can configure it to track system metrics and generate reports that highlight potential issues or performance bottlenecks.