Airlock IAM instance configuration
Some fundamental settings of an instance cannot be configured in the Config Editor. These are referred to as "application parameters". They are configured in the instance properties file or using the environment. Note that application parameters are only applied on startup. Changing their values requires Airlock IAM to be restarted.
The file instance.properties can be found in the instance directory (e.g., <configuration-dir>/instances/auth/instance.properties).
The following instance settings can be configured in the instance.properties file:
- Log directory and level (see Logging configuration)
- Activated modules (see IAM modules and databases/directories)
- Web server ports, URL paths, and TLS settings (see Securing Airlock IAM with HTTPS)
- Environment ID (see Configuration environments)
- Settings of the Config Editor itself, such as the configuration activation timeout or whether configuration variables are editable in the Config Editor (see Configuration activation timeout and Step 1 – Define configuration variables, respectively). The instance property
iam.config-editor.enabledallows to disable the Config Editor. In this case, the Config Editor will not be started upon startup of the Adminapp. For this, set the propertyiam.config-editor.enabledto false (the default is true).
It is possible to enable UI customizations using the iam.*.layout.dirs properties. This is intended for layout customizations only, but it does not prevent overriding other product-specific files (i.e. web.xml).
Customers that use this mechanism for customization beyond the intended purpose are responsible to maintain these customized files, especially when updating the product. There is no guarantee that such customizations will be supported in future releases.
Please refer to the documentation in the file for detailed information. See also Application parameters.
To get an up-to-date template including documentation and current default values run:
iam default-parameters