During the upgrade to Airlock IAM 8.0, scripts attempt to configure and migrate outdated user trail logging settings to the new defaults (logging into a database). Although fresh installations of IAM 8.0 and later will solely use logging into the database by default, upgraded installations will keep on logging into the medusa-usertrail.log
file in parallel until configured otherwise (see Step 4).
- The upgrade migration does not automatically import old log messages from the
medusa-usertrail.log
into the database. After successful automatic migration, proceed with Step 3 to check the logging functionality before importing old log messages into the database as required (see Step 5). - When the automatic migration fails, the log list in Adminapp >> Users >> Activities tab remains empty because the logging database is not configured as required. In this case, user trail logs are still stored in the outdated
medusa-usertrail.log
file, and user activities can be looked up in the Logs menu for each IAM module.
- Requirements for automatic migration:
- A single SQL Data Source is configured under MAIN SETTINGS >> Database User Persister.
- No LDAP or Active Directory Database User Persister is configured. If this is the case, the user trail logging target database must be configured manually.
- A custom plugin is available in the plugin tree. If this is the case, the migration must be done manually.
This article describes how to set up and configure the default logging into a database for Airlock IAM 8.0 and later. Depending on the actual IAM configurational state before the upgrade to 8.0, some of the steps may already be prepared and ready to use (e.g., a global data source is already configured), but the migration failed anyway.
If the migration fails partly, needed changes are displayed. Proceed with the matching configurational steps of the instructions in this article.