As Airlock IAM grows and new features are added, the database schema evolves. Airlock IAM does not self-migrate the database schema, i.e., you have to upgrade the database schema manually when upgrading the IAM version.
Schema migration SQL files are available starting with IAM 7.1. See 6.2.1. Relational databases for IAM.
Instructions on how to migrate the schema from IAM 7.0 to IAM 7.1 are listed in the table below.
Database schema history (IAM 7.0 to IAM 7.1)
SQL schema definitions
The table describes the changes but does not provide the actual SQL schema definition. The SQL schema definitions for all supported databases can be found here: 6.2.1. Relational databases for IAM
Added in Version | Affected Features | Affected DBs | Description | New/affected Database Objects* |
7.1 |
| all | New index in token data model. Prevents potential performance issues. |
|
7.1 |
| all | Changes in technical clients tables for all database types. |
|
7.1 |
| mysql | MySQL Schema:
|
|
7.1 |
| MariaDB | MariaDB Schema (new): To support more specific collations, a separate Maria DB schema has been introduced. |
|
7.1-pre1 |
| all | New database tables used to store technical clients and their authentication tokens. |
|
7.1-pre1 |
| H2 MariaDB mysql | DB schema fixes:
|
|
7.1-pre1 |
| all | New field to store number of failed password-reset attempts. |
|