3. GlobalID Client Troubleshooting, v5.0

The configuration of the GlobalID client is stored in registry, under HKEY_LOCAL_MACHINE\SOFTWARE\Liga\GlobalID

 

Attribute

Syntax

Description

CardDevice

REG_SZ

The configured card reader’s device name. The card reader is used for all card processes in the client with desktop mode and all non Fargo printing processes in the kiosk mode.

CardDevicePrinter

REG_SZ

The configured card reader’s device name for issuing processes in kiosk mode.

CardPrinter

REG_SZ

The configured printer for Card print, can be left blank if no printer is configured.

DefaultLanguage

REG_SZ

Default language in the Kiosk Client, if not set default is EN.

Currently supported is:

EN = English

DA = Danish

FargoTimeOut

REG_SZ

TimeOut in seconds for Fargo movement. If movement is not finished within the interval the running process will result in error.

GlobalIDAPIApplication

REG_SZ

NOTE: Encrypted value in registry

 

The API Key and API application is used to identify the client on the GlobalID server and controlling what rights the Key+Application has on GlobalID.

GlobalIDAPIKey

REG_SZ

NOTE: Encrypted value in registry

 

The API Key and API application is used to identify the client on the GlobalID server and controlling what rights the Key+Application has on GlobalID.

GlobalIDRESTURL

REG_SZ

The URL for communication with the GlobalID server.

 

https://<host:port>

or

https://<host:port>/<path>

KioskMode

REG_SZ

0 = the client will start in Desktop Mode (Window)

1 = the client will start in Kiosk Mode (Full-Screen)

PrintTimeout

REG_SZ

TimeOut in seconds for the printing operations. If printing is not finished within the interval the running process will result in error.

Proxy

REG_SZ

If the network communication require a http proxy this setting must be set.

If no proxy is required this setting must be left blank.

RestTimeout

REG_SZ

TimeOut in seconds for all REST and HTTPS communications. If communication is not finished within the interval the running process will result in error.

SOPIN

REG_SZ

NOTE: Encrypted value in registry

 

Security Office PIN – can be used as backdoor to unlock a smartcard. When the client initialize a new card profile the SOPIN is set.

 

If SOPIN is left blank a random SOPIN is generated on each card initialization, the random generated SOPIN is not stored anywhere. This is equal to disable the SOPIN functionality.

UseFargoMover

REG_SZ

0 = Don’t use fargo feeder, movement and ejection

1 = Use Fargo for card feeder, movement and ejection

 

GlobalID Client Troubleshooting

 

Every event on the client is logged - to the Windows EventLog, to the connected GlobalID server and to a local file.

All client events are reported back to the GlobalID server and are visible and searchable there.

Windows EventLog

 

When installing the GlobalID Client an EventLog is created for all client events.

If Windows Event logging is not preferrable, the GlobalID Eventlog can be deleted and the client will not log to the Windows EventLog.

GlobalID Client EventLog

 

The central client event log can be accessed using the web-based AdminUI at the section Logs / Client Events.

Client Log files

 

In the user's temp folder a GlobalID5.Log is created and contains the same information as the EventLog and central logging. Even if the GlobalID server is not available logging is recorded locally.

The file is stored in “%temp%\GlobalID5.log”.