Reliable event delivery

1. Specify the outbox settings, for the Loginapp, the Adminapp, and the Service Container. For details, see Specifying the outbox settings.
2. In the Service Container, configure the Event Outbox Processor Service. This service forwards events from the outbox to a message broker. This step includes:
3. • Selecting a message broker. Currently (Q2 2026), only Azure and Kafka are supported.

   • Note: It is possible to route different event types to different brokers, if required.

   • Specifying optional delivery settings, such as the batch size and sending interval. If nothing is configured, the default values are used.

4. For details, see Configuring the Event Outbox Processor Service.

Perform the next steps:

0. In the Config Editor, go to
   Loginapp >> Event Settings >> Outbox Settings section
1. In the Outbox Repository field, create and edit an Outbox Repository plugin as follows:
2. 1. Enter a suitable name for the plugin in the Display Name field, for example “Event Outbox Repository”.
   2. In section Basic Settings, in field SQL Data Source, create and edit a JDBC Connection Pool plugin. This plugin is used to connect the IAM modules to the outbox. Configure the plugin in line with your DB setup and requirements.
   3. • For more information on relational DBs, see Relational databases for IAM.
   4. Specify the optional settings in Advanced Settings, if required.
3. • You have now configured the Outbox Repository plugin for reliable event delivery.
4. Now go to
   Adminapp >> Event Settings >> Outbox Settings section
5. In the Outbox Repository field, select the Outbox Repository plugin defined previously for the Loginapp. In our example, this is the “Event Outbox Repository” Outbox Repository plugin.
6. Next, go to
   Service Container >> Event Settings section
7. In the Outbox Repository field, select the Outbox Repository plugin defined previously for the Loginapp. In our example, this is the “Event Outbox Repository” Outbox Repository plugin.
8. You have now specified the outbox repository for all modules.
9. Next, set the additional outbox options in the Outbox Settings section (Loginapp/Adminapp) or Event Settings section (Service Container), respectively. The table below lists the configuration options per IAM module.

10. IAM Module	Additional configuration options	Description
    Loginapp	Include Generic Step Result Events checkbox	Enable this checkbox to also store events generated by generic steps. However, before also including generic step result events, consider the following: Generic step result events occur more frequently than other event types, and they are usually of less interest to external event consumers.
    	Custom Outbox Data list	Defines value map providers that add additional data to the events stored in the outbox repository. Currently, the following value map providers are available: Authentication Data Map: Provides data on the successful authentication of the current end-user. Context Data Map: Provides all context data of the current end-user. HTTP Request Information Map: Provides information about the current HTTP request. Roles Provider: Provides a list of roles. User Identity Map: Provides identity information on the current end-user. User Statistics Map: Provides some login statistics of the current end-user.
    Adminapp	Add Context Data checkbox	Enable this checkbox to add context data on the managed end-user to the events stored in the outbox repository.
    Service Container	User Store field	Defines a user store from which context data values will be added to the stored events. Note that these values might contain sensitive information such as email addresses or phone numbers. If required, select the user store relevant for your setup.

12. You have now configured the outbox settings for all modules.

1. In the Config Editor, go to Service Container
2. In the Basic Settings section, in the Services list, create and edit a new Service plugin.
3. In the Service plugin, in the Service field, create and edit a new Event Outbox Processor Service plugin, as follows:

4. Event Outbox Processor Service plugin

   0. In section Basic Settings, in the Outbox Repository field, select the Outbox Repository plugin previously created for the IAM modules that write events in the outbox (see Specifying the outbox settings; in our example, this is the “Event Outbox Repository” Outbox Repository plugin).
   1. In section Basic Settings, in the Message Broker Selectors list, define a list of message brokers to which to forward the events. Currently (Q2 2026), only Azure and Kafka are supported. You can route different event types to different brokers, if required.
      Per message broker, create and edit a Message Broker Selector plugin, as follows:

   2. Message Broker Selector plugin

      • In the Event Type Pattern field, specify the event types to be sent to the message broker configured here.
      • • To send all event types to the current broker, enter the regular expression .*
        • To send only specific event types to the current broker, enter the relevant event type codes in the field as a regular expression. For example:
        • • AIRLOCK_2FA_DEVICE_ACTIVATED
          • USER_.*
          • AIRLOCK_2FA_DEVICE_ACTIVATED|AIRLOCK_2FA_DEVICE_DELETED|USER_.*

        • For the complete list of event types (and corresponding event producers), go to Event producers.

      • In the Message Broker field, specify the relevant message broker. Currently, only Azure and Kafka are supported. Create and edit the corresponding Message Broker Connector plugin as follows:
      • • For an Azure message broker, select the Azure Message Broker Connector plugin. This connector sends the events to the Azure Event Hub. For details on the setup and configuration of an Azure Event Hub as well as the required authentication infrastructure, see Azure Event Hub documentation.
        • For a Kafka message broker, select the Kafka Message Broker Connector plugin. This connector sends the events to a so-called Kafka topic. Each entry in the topic is called a record. The connector uses the Apache Kafka Java client library to produce the records and forward them to the Kafka topic. For details on the setup and configuration, see the Kafka producer configs documentation.
      • Return to the Message Broker Selectors list in the Event Outbox Processor Service plugin. If required, create and edit additional Message Broker Selector plugins.
   3. Go to the Advanced Settings section of the Event Outbox Processor Service plugin to specify optional settings of the event message delivery. If nothing is configured, the default values are used.

   4. Available options:

      • Batch Size property: Defines the number of processed events during each run. One run includes reading from the repository, forwarding the messages and cleanup. The default batch size is 1000.
      • Min. Interval [ms] and Max. Interval [ms] properties: Define the time range between batch transmissions. If a batch finishes within the minimum interval, the system waits for the remaining time before starting the next. If processing takes longer than the minimum interval, the next batch begins immediately.
        Error handling: If a batch fails entirely, the wait time doubles (exponential backoff) until it hits the maximum interval. Upon the first successful message delivery, the interval resets to the minimum value.
        Default values: 500 ms. for Min. Interval [ms], 10000 ms. for Max. Interval [ms].
5. • You have now specified the Event Outbox Processor Service plugin. Return to the Service plugin.
6. Enable the Auto Start checkbox in the Service plugin to automatically start the Event Outbox Processor Service upon server start.
7. You have now configured the Event Outbox Processor Service.