Reserved Values for Custom Attributes - Identity and Access Management Services - 4.4 - 4.4 - Ready - Other - external - Other/Identity-and-Access-Management-Services/4.4/Identity-and-Access-Management-Services/Configuring-the-Hyland-IdP-Server/Configuring-Providers/Configuring-New-User-Attribute-Mapping-For-Custom-Claims/Reserved-Values-for-Custom-Attributes - 2024-11-20

Identity and Access Management Services

Platform
Other
Product
Identity and Access Management Services
Release
4.4
License

User attribute mapping as key is considered as custom attribute mapping and is added to the issued tokens. However, the following values are an exception to this behaviour.

  • username
  • email
  • realName
  • name
  • group
  • userid

The following limitations apply when using custom attribute mapping:

  • A maximum of 30 custom user attribute mappings can be added for a provider. If the count exceeds the maximum threshold, then there can be potential performance impact.
  • Custom claim mapping for a provider can only be modified by making changes directly in the idpconfig.json file. Custom claims configured for a provider cannot be modified from Hyland IdP Administration client or through the provider's modification API endpoint.
  • Only single-valued attributes are supported as part of custom user attribute mapping. For example, HireDate to add hire date information.