Event subscribers

Event bus instantiation

Airlock IAM emulates a centralized event bus for Loginapp/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:

  • Email Event Subscriber (Loginapp)
  • Email Event Subscriber (Adminapp)
  • SMS Event Subscriber (Loginapp)
  • SMS Event Subscriber (Adminapp)

Currently, only Loginapp/Adminapp modules 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.

SMS Event Subscriber

The SMS Event Subscriber sends SMS notifications 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 available mobile phone numbers including the replaced mobile phone number.

User Locked event

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.