You are here

Migrating Custom System Settings to Airlock 5

Affects version(s): 
5.x

Migrating custom system settings

This article describes how to convert custom system settings to Airlock 5.

Please refer to the general Airlock 5 Upgrade Guide for a detailed description of how to upgrade an Airlock node.

Customized events

To migrate the customized event configuration copy the file logsurfer.conf.user.custom from backup to the directory /opt/airlock/custom-settings/taclog/ and restart the service:
service restart geneventd
service restart logsurfer
For more information about event customization see this article.

Additional Configuration Center user

To migrate the Configuration Center users and their permissions, copy the files password.properties, roles.properties and assertion_key.properties from backup to the directory /opt/airlock/custom-settings/mgt-auth (overwrite the existing files) and execute the following commands:

# mv assertion_key.properties assertion-key.properties
# chmod 040 assertion-key.properties
# chown fown:alec assertion-key.properties

Customized Configuration Center authentication

To migrate a custom configuration for the Configuration Center authentication, copy the authentication.properties file from the backup to the directory /opt/airlock/custom-settings/mgt-auth and change the global.logFile property to:

global.logFile=/var/log/airlock/mgt-tomcat/auth.log

Change also the following file paths to:

/opt/airlock/custom-settings/mgt-auth/password.properties
/opt/airlock/custom-settings/mgt-auth/assertion-key.properties
/opt/airlock/custom-settings/mgt-auth/roles.properties

Read-only User

How to create the additional read-only user for automatic backup is described here. 

System-level differences between Airlock 4.2 and 5

For an overview of the relevant system-level changes (e.g., directory structure, log files, commands, service management), please consult the Command Line Cheat Sheet.

Knowledge Base Categories: