GoSign Service - ADSS-Admin-Guide

Home > Global Settings > Advanced Settings > Services Level Settings > GoSign Service

GoSign Service

Property	Description
Hand signature font name	Hand signature font when it is taken as Text in Go>Sign Document Viewer. Default value: susie.ttf APPEARENCE_FONT_NAME = susie.ttf
Signature field size	Default Height/Width for creating new signature field in Go>Sign Document Viewer. FIELD_LENGTH_UNIT = 100
Client session timeout	Number of minutes of inactivity to terminate the session with client application. CLIENT_SESSION_TIMEOUT = 10
Debug logging for applet	When enabled, Go>Sign Applet writes the debug logs in the user's home directory for any communication with Go>Sign Service. CREATE_DEBUG_FILES = FALSE
Go>Sign request forwarding	Protocol to redirect the request among load balanced instances of Go>Sign Service. Possible values are HTTP & HTTPS GOSIGN_FORWARD_PROTOCOL = HTTP Port to redirect the request among load balanced instances of Go>Sign Service. Possible values are 8777, 8778 & 8779 GOSIGN_FORWARD_PORT = 8777
Go>Sign Desktop request forwarding	Default port for Go>Sign Desktop to hash and sign locally on: non-TLS GOSIGN_DESKTOP_HTTP_PORT = 8781 TLS GOSIGN_DESKTOP_HTTPS_PORT= 8782
Signature Padding Scheme	Define the signature padding scheme to be used by the Go>Sign service while performing signing operations. The default parameter value is: SIGNATURE_PADDING_SCHEME = PKCS1 Possible values are PKCS1 and PSS Note: Click here for more details on limitations when PSS padding scheme is used.
Transaction logs settings	Transactions can be stored either directly or delayed for better performance. The following properties are used for logging: TRANSACTION_LOG_MODE = LAZY Used to decide whether the transactions are kept in memory before these are stored in the database (LAZY logging) or directly stored in the database (EAGER logging). Possible values: LAZY, EAGER In case of LAZY logging the transaction logs are kept in memory upto the number of seconds configured in TRANSACTION_LOG_LAZY_INTERVAL or number of transactions configured in TRANSACTION_LOG_LAZY_RECORD_COUNT whichever is reached first TRANSACTION_LOG_LAZY_INTERVAL = 2 When LAZY logging is configured, transactions are kept in memory upto the configured time or if the configured TRANSACTION_LOG_LAZY_RECORD_COUNT is reached before it TRANSACTION_LOG_LAZY_RECORD_COUNT = 50 When LAZY logging is configured, transactions are kept in memory until the configured number of transactions is reached or if the configured TRANSACTION_LOG_LAZY_INTERVAL is met before it.