Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

In various scenarios, the email address of a core identity is required. In many cases, the email address that should be used can be found directly on the core identity's mail property. This "How-to" guide provides the configuration steps needed to set this mail property as desired.

Database Table

The table servicedmcore_core_identity_mail_prio_mapping is central to configuring the preferred method for setting the email address. The following configurations are available:

  • core_identity_id
    Multiple core identity types may require different logic to set the correct email address. The ID of the desired core identity type can be specified here.

  • identity_type_id
    Configuration can be refined by adding an identity type ID. If this field is set with the ID of an identity type, the entry will be considered only if the core identity has that specific identity type. This is particularly useful when, for instance, the email address is read from an Active Directory.

  • attribute_id
    This field defines which attribute should be used to map the email address to the mail property. The ID of the desired attribute is required.

  • order_id
    If multiple configurations are added for the same core identity type, an order must be specified to define the sequence in which the system tries to map values from the attributes to the mail property. Order ID 1 is processed first, followed by Order ID 2, and so on.

  • regexp
    A regular expression (regex) can be applied to validate the attribute value. If the email address found in the attribute matches the regex, it will be mapped accordingly. If it does not match, the entry with the next highest Order ID will be used.

  • No labels