The size of a 1024-character string within the application. As the name indicates, the string cannot be more than 1024 characters.

1024

The size of a 12285-character string within the application. As the name indicates, the string cannot be more than 12285 characters.

12285

The size of a 16384-character string within the application. As the name indicates, the string cannot be more than 16384 characters.

16384

The size of a 17792-character string within the application. As the name indicates, the string cannot be more than 17792 characters.

17792

The size of a 2080-character string within the application. As the name indicates, the string cannot be more than 2080 characters.

2080

The size of a 32768-character string within the application. As the name indicates, the string cannot be more than 32768 characters.

32768

The size of a 4-character string within the application. As the name indicates, the string cannot be more than 4characters.

4

The size of a 5-character string within the application. As the name indicates, the string cannot be more than 5 characters.

5

The size of a 6-character string within the application. As the name indicates, the string cannot be more than 6 characters.

6

The size of a 65535-character string within the application. As the name indicates, the string cannot be more than 65535 characters.

65535

The size of an 8-character string within the application. As the name indicates, the string cannot be more than 8 characters.

8

The size of a 9-character string within the application. As the name indicates, the string cannot be more than 9 characters.

9

All batch jobs must transfer their files to the appliance (using SFTP, SMB or NFS, etc.) before the web service request for the transaction may be sent to the appliance. This configuration property identifies the root directory of all subdirectories where each encryption domain will transfer XML files in and out, before and after the cryptographic batch job is executed. The default location is /usr/local/strongauth/batchrequests.

/usr/local/strongauth/batchrequests

The prefix of the DN of the signing digital certificate issued to the encryption domain. The unique domain identifier of the encryption domain is appended to this prefix during the creation of this certificate. The SAKA domain's signing certificate keys are used to sign all digital certificates issued by this encryption domain. In that sense, this signing key's certificate represents a “mini” Certificate Authority (CA) whose sole purpose is to issue certificates to resources within its encryption domain. This CA cannot be used for purposes outside SAKA.

CN=SAKA Signing Certificate, OU=Domain ID

The prefix used to distinguish between cryptographic keys within an encryption domain. SAKA uses three types of symmetric keys: 1) for encryption; 2) for generating Hashed Message Authentication Codes (HMAC) of plaintext sensitive data; and 3) for generating HMACs of user passwords in the SAKA internal database. Each of these keys are labeled with a key prefix so they may be uniquely identified for their purpose.

ENC-

The prefix used to distinguish cryptographic HMAC keys within an encryption domain. SAKA uses three types of symmetric keys: 1) for encryption; 2) for generating HMACs of plaintext sensitive data; and 3) for generating HMACs of user passwords in the SAKA internal database. Each of these keys are labeled with a key prefix so they may be uniquely identified for their purpose.

HMAC-

The Java Naming and Directory Interface (JNDI) name for the resource to access the MariaDB database.

jdbc/strongkeylite

Cryptographic keys used by the web service application are changed frequently, based on the policy defined in this property. The policy for the PWD key is to use a new key every year (annual).

annual

The suffix used to label cryptographic keys when symmetric cryptographic keys are used for 24 hours. This property value is concatenated with the key's prefix property to derive the unique label of a cryptographic key. For instance, an encryption key, generated and used on the 1^st day of January in 2010 would have the label ENC-01-JAN-2010, while a key generated and used on the 3^rd day of March in 2010, would have the label ENC-03-MAR-2010. HMAC keys for the same dates would have the labels HMAC-01-JAN-2010 and HMAC-03-MAR-2010 respectively.

dd-MMM-yyyy

The suffix used to label cryptographic keys when symmetric cryptographic keys are used for one week, starting from the second past midnight on a Sunday (Universal Coordinated Time) through the last second of the Saturday the same week.

Since weeks do not have names, the week is indicated by the numeric value of the week—the first week of a year is 1, while the last week of the calendar year would be 52. This property value is concatenated with the prefix property to arrive at the unique label of a cryptographic key. For instance, an encryption key, generated and used on January 5^th, 2010 would have the label ENC-1-2010, while an HMAC key would have the label HMAC-1-2010.

w-yyyy

The cryptographic algorithm used by application tools to digitally sign nonces for authentication, when an HSM is used as the cryptographic hardware module in the SAKA server.

SHA256withECDSA

SAKA converts XML files to Java objects and vice-versa. This URL defines the current XML Schema Definition (XSD) in use by the appliance. The current URL for this version of SAKA is: http://strongkeylite.strongauth.com/SKLES201009

http://strongkeylite.strongauth.com/SKLES201009