The SAKA software comes with many customizable properties that do not need to be changed for most sites. However, some properties must be customized for each site, and sites may want to customize some based on their security policies. The following table presents a list of all the properties used by this release of SAKA.

Configuration properties are divided into either Immutable or Mutable properties. Immutable properties, as their definition implies, may not be changed at any time as this will impact SAKA operations. Mutable properties, however, may be modified as needed to meet business, operational, technical, and/or security requirements.

All SAKA server properties are bundled in the resources folder of the strongkeyliteEJB module in the SAKA application. This file provides the central configuration for the system. Properties used by client applications—such as the SAKA Domain Administration Console Tool (DACTool) or the SAKA Key Custodian SetPIN Tool applications—are bundled within the client applications and should not be modified at all.

SAKA server properties can be modified in one of two ways:

1. By modifying the properties file—strongkeylite-configuration.properties—in the STRONGKEYLITE_HOME/etc directory. Changes made to this file override the configuration properties bundled in the application module, and thus, apply to all encryption domains in SAKA. An editor (gedit, nano or vi) may be used to edit this file; the application server (or SAKA) must be restarted for the changed properties in this file to take effect.

2. By using the DACTool and modifying the configuration properties though the graphical console. Changes made in the DACTool are persisted in the SAKA internal database and apply only to the encryption domain where the modification is made. The application server or the SAKA does not require a restart for these changed properties to take effect. They are effective immediately after they are saved to the internal database.