Loglevel FATAL

For operational purposes, Airlock IAM will create log entries with priority FATAL if a required 3rd party service is not responding or if a configuration error will prevent IAM from regular operation.

Overview of FATAL log

Airlock IAM will log a message with priority FATAL in the following situations:

Issue type	List of possible 3rd party systems
Connection unavailable to essential 3rd party system	Database Redis LDAP Active Directory SMS Gateway Email Server Futurae Server Radius Server AWS KMS
Invalid Configuration	Failure during configuration activation.
License issues	License could not be activated.
Local dependencies failures	Lua library required for Scriptable Step could not be loaded. Cronto library could not be loaded.
Application fails to start	Failure during the startup of a configured application (Loginapp, Adminapp, ...)

Migration from releases before IAM 8.4

The following log messages have been modified by changing the priority of these log messages to meet the new definition of FATAL priority:

Error Situation	Modified log messages now logged as priority FATAL
Invalid configuration	Message: “An exception occurred during config activation. The config has not been activated.”
AWS KMS connection error	Message: “An error occurred while retrieving the public key from AWS KMS: [...]” Message: “An error occurred while encrypting with AWS KMS: [...]” Message: “An error occurred during symmetric decryption with AWS KMS: [...]” Message: "An error occurred during asymmetric decryption with AWS KMS: [...]"