Event subscribers

Airlock IAM emulates a centralized event bus for the Loginapp and the Adminapp by instantiating one event bus for every incoming request and registering the configured event subscribers.

Airlock IAM currently supports the following types of event subscribers:

Currently, only the modules Loginapp and Adminapp offer the possibility to configure event subscribers. Event requests are handled by Loginapp and Adminapp as exclusive processes.

Running as its own process, it can be necessary to configure the same subscriber twice – once for Loginapp and once for Adminapp. This is to ensure that the event will be processed in all cases. For this reason, event subscribers can be configured under Event Settings, which is top-level in both modules.

The Email Event Subscriber plugin sends email messages with event details. The recipient of the email is defined by the plugin's configuration and may, for example, be the end-user or an administrator.

Event attributes (see Event attributes) can be referenced to include event data in both the email subject and body. Please refer to the plugin documentation in the Config Editor for further information.

The Remote Event Subscriber plugin connects to a remote HTTP endpoint using the configured HTTP Method and Content Type. It can, for example, be used to send event data to a remote REST API.

Event attributes (see Event attributes) can be referenced to include event data in both the request URL and the request body. Please refer to the plugin documentation in the Config Editor for further information.

The SMS Event Subscriber plugin sends SMS messages to all available mobile phone numbers of the end-user. It is not possible to configure a preferred communication mobile phone number.

In case of an MTAN Token Phone Number Changed event, the message is sent to all mobile phone numbers assigned to the user. It is possible to send the message to the old (replaced) phone number as well.

Event attributes (see Event attributes) can be referenced to include event data text message. Please refer to the plugin documentation in the Config Editor for further information.

The User Locked event warrants special treatment by the event subscribers. It is often desirable to send different messages contents determined by the cause of the User Locked event.

To support this behavior the User Locked plugin provides an additional Lock Reason filter. If configured, the event subscriber only handles those User Locked events that match the Lock Reason pattern.

• Event notification settings in the Loginapp
• Event notification settings in the Adminapp