Account linking persister
17.7.3.6.1. Configuration of account linking persister and consistency

Account linking requires its own persister to store data of the linked accounts per user.

The persister is configured only once and it is used for all clients.

To avoid insistencies with the persister, a User Change Event Listeners must be configured. This listener guarantees that changes on a user, e.g. username, are correctly propagated to the persisted account link data.

Note that account linking is only supported for relational databases (no LDAP plugins available).

Account Linking introduces a new database table account_link to the IAM schema. Please check if your database has this table before using this feature. SeeĀ 6.2.1.6. Database schema history up to IAM 7.1 for details.

Create Account Link Persister

  • 1.
    Go to:
    Loginapp >> OAuth 2.0/OIDC Client
  • 2.
    Account Link Persister: create an Account Link Database Repository plugin.
  • 3.
    Go to:
    Account Link Database Repository
  • 4.
    SQL Data Source: configure a JDBC Connection Pool.
  • 5.
    Table Name: optionally configure the database table name for the account links.
  • Airlock IAM is configured to store account links.

Create an Account Link Consistency User Change Listener

  • 1.
    Go to:
    MAIN SETTINGS >> Data Sources >> User Data Source
  • 2.
    User Change Event Listeners: create an Account Link Consistency User Change Listener plugin.
  • 3.
    Go to:
    Account Link Consistency User Change Listener
  • 4.
    Persister Config: select the Account Link Database Repository
  • Airlock IAM will ensure that changes on the user will be automatically updated in the account links as well.

Account link management in the Adminapp

The user's account links can be displayed and managed by the administrator in the user management section of the Adminapp.

To enable this, connect the Account Link Database Repository in Adminapp >> Users >> Account Link Management.