Reserved Values for Custom Attributes - Reserved Values for Custom Attributes - Perceptive Content - OnBase - Other - Identity and Access Management Services - Other/Identity-and-Access-Management-Services/5.3/Identity-and-Access-Management-Services/Configuring-IdS/Configuring-Providers/Configuring-New-User-Attribute-Mapping-For-Custom-Claims/Reserved-Values-for-Custom-Attributes - 5.3 - 5.3

Identity and Access Management Services

Platform
Other
Product
Identity and Access Management Services
Release
5.3
License
ft:lastPublication
2026-10-27T10:02:38.221757
ft:locale
en-US

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 idsconfig.json file. Custom claims configured for a provider cannot be modified from Hyland IdS 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.