MariaDB as Airlock IAM database

This page describes how to use a MariaDB database with the Airlock IAM database schema. In order to use Airlock IAM with this database, a JDBC connector/driver library is required.

  • The chosen data layer has to be well managed and monitored. IAM is not responsible for the operation and backup/recovery. For production usage, the data layer should be clustered.
  • In order to use Airlock IAM with this database, a JDBC connector/driver library is required.

Compatibility

MariaDB version 10.2 or higher is required for full compatibility with the IAM database schema.

Database settings

The following MariaDB database settings may be useful:

Purpose

Command Line

my.cnf

table names are used case-insensitive

Note: use this option to avoid issues with older Demo Configurations using table names in upper case

--lower_case_table_names=1

[mysqld]
lower_case_table_names=1

Schema creation and upgrade

SQLs scripts for MariaDB databases are available here:

SQL File

Description

Creates tables used for Airlock IAM.

Upgrades IAM 8.2 database schema for release IAM 8.3.

See note below.

Upgrades IAM 8.1 database schema for release IAM 8.2.

Upgrades IAM 8.0 database schema for release IAM 8.1.

Upgrades IAM 7.7 database schema for release IAM 8.0.

See DB Schema Migration IAM 8.0.

Upgrades IAM 7.6 database schema for release IAM 7.7.

Upgrades IAM 7.5 database schema for release IAM 7.6.

Inserts an administrator "admin" with password "password" (works with demo configuration).

For performance tuning hints, see: Performance tuning and scaling best practices

Improtant note on schema migration from IAM 8.2 to IAM 8.3

Note that the schema upgrade from IAM 8.2 to IAM 8.3 contains a change to the collation of oauth2_session table.

Applying this change will cause a database index to be rebuilt. If the table contains a lot of records, this change may take a long time to complete.

Applying the change is recommended but optional.

Further information and links