Getting started
6.3.4. Getting started after installation

This page describes the next steps after a successful installation of Airlock IAM

Starting and stopping IAM instances

Please refer to 7.1. Starting and stopping Airlock IAM (system service integration) for details about starting and stopping IAM instances.

If installed using the installer (see 6.3. Installation on a Linux host system), the default instance "auth" is started and stopped using:

# Start IAM instance "auth", typically as root
systemctl start airlock-iam-auth
systemctl status airlock-iam-auth

# Stop IAM instance "auth", typically as root
systemctl stop airlock-iam-auth

Upload a license

After the installation, Airlock IAM does not yet have a valid license and is thus in an unlicensed mode. In this state, only access to a basic version of the Adminapp is possible.
In order to enable all licensed features, logon to the Adminapp and navigate to License. Here you can upload a valid license by pasting it into the input field. The license is validated and some feedback is displayed. If the license is valid, it can be activated by clicking on the "Activate" button.

The Adminapp will reload itself and access to all configured features will be available. Note that an open browser tab for the Config Editor needs to be reloaded manually to see license changes.


Choose a config template

Config templates are a predefined set of configurations to help configuring an Airlock IAM instance for a specific use case.

Open the Config Editor to see your current configuration. By clicking on "New", a dialog with available config templates is shown. For each template, a small description of the configuration and license requirements can be seen by selecting it. Choose one that matches your desired use case. Note that a template is normally only the basis for further customization. 


A template has many preconfigured settings and some blanks that need to be configured by the administrator, e.g. connection details for the local database. Look for Config Editor validation indicators or on the "Errors" tab in the bottom panel, to see which settings require additional information.

Choosing a template usually defines where user data is stored (LDAP, AD, Database, ...). Please refer to 6.2. Data sources (databases, directories) for further information about the right choice of a user directory.

The "Demo Configuration" templates contains many pre-configured features and a lot of examples. If using it as basis for a productive system, it is essential to go through the whole of the configuration to disable unneeded features!

Activate the configuration

When all blanks of the config template are filled in and the configuration passes validation, it can be activated by clicking the "Activate" button.