Study guide

2.3 Creating Extended Attributes and the Objects That Support Them

SailPoint Certified IdentityIQ Engineer Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: The IdentityIQ Engineer Exam

1.1 Exam Format, Official Blueprint, and Study Strategy

2 Chapter 2: Infrastructure, Installation, and Extended Attributes

2.1 IdentityIQ Infrastructure Components 2.2 Installation Steps and Procedures 2.3 Creating Extended Attributes and the Objects That Support Them

3 Chapter 3: Build, Deployment, Patching, Access, and Email

3.1 Ongoing Build and Deployment 3.2 Installing Patches and Performing Upgrades 3.3 Configuring End-User Access 3.4 Email Server Settings and Email Redirection

4 Chapter 4: Lifecycle Manager Configuration, Provisioning Policies, and Workflows

4.1 Configuring Lifecycle Manager 4.2 Identity Provisioning Policies 4.3 Configuring LCM Workflows

5 Chapter 5: Lifecycle Events, QuickLinks, Batch Requests, and Rapid Setup

5.1 Lifecycle Events and Their Workflows 5.2 QuickLinks and QuickLink Populations 5.3 Configuring and Using Batch Requests 5.4 Rapid Setup in Lifecycle Events and Identity Operations

6 Chapter 6: Certification Campaigns and Certification Rules

6.1 Configuring and Scheduling Certification Campaigns 6.2 The Purpose of Common Certification Rules

7 Chapter 7: Policies and Policy Violations

7.1 Configuring and Leveraging Policies 7.2 Responding to Policy Violations

8 Chapter 8: Reporting, Advanced Analytics, and Auditing

8.1 Executing and Leveraging Reports 8.2 Leveraging Advanced Analytics 8.3 Configuring and Using Auditing

9 Chapter 9: Rules, Rule Libraries, and the SailPoint API

9.1 The Purpose and Use of Rule Libraries 9.2 Rule Input and Output Arguments 9.3 Common SailPoint API Objects and Methods

10 Chapter 10: Workflow Development

10.1 Workflow Variables, Transitions, and Step Conditions 10.2 Workflow Steps That Generate Work Items 10.3 The Different Workflow Step Usages 10.4 Leveraging Sub-Workflows

11 Chapter 11: Email Templates, Branding, and Localization

11.1 Customizing and Using Email Templates 11.2 Branding the SailPoint User Interface 11.3 Localizing the SailPoint UI

12 Chapter 12: Application Definitions, Connector Settings, and Rapid Setup Aggregation

12.1 Configuring Application Definitions 12.2 Configuring Common Connector Settings 12.3 Configuring Rapid Setup Aggregation Settings

13 Chapter 13: Data-Loading Tasks and Application and Connector Rules

13.1 Scheduling Tasks for Data Loading and Processing 13.2 Common Application Rule Types 13.3 Common Connector Rule Types

14 Chapter 14: Debugging with log4j, Syslog, and the IdentityIQ Console

14.1 Configuring and Leveraging log4j 14.2 Configuring and Leveraging Syslog 14.3 Leveraging the IdentityIQ Console for Debugging

15 Chapter 15: Debug Pages and the Administrator Console

15.1 Leveraging the Debug Pages for Debugging 15.2 Leveraging the Administrator Console for Debugging

16 Chapter 16: Role Model and Identity Attribute Mappings

16.1 Default Role Models and Role Types 16.2 Configuring Roles and Role Options 16.3 Configuring Identity Attribute Mappings

17 Chapter 17: Data Objects, Relationships, and Group Types

17.1 Common IdentityIQ Data Objects 17.2 Relationships Between Common Data Object Models 17.3 The Difference Between Group Types

2.3 Creating Extended Attributes and the Objects That Support Them

Key Takeaways Explain This Topic AI

Identity (Identity), account (Link), Application, role (Bundle), entitlement (ManagedAttribute), and CertificationItem are the common objects with extended attributes, each described by an ObjectConfig.

Extended attributes are defined on Global Settings pages: Identity Mappings, Account Mappings, Application Attributes, Role Configuration, and Entitlement Catalog Attributes.

A searchable extended attribute needs a database column: a numbered extendedN column or a named column declared in the object's Extended.hbm.xml file.

Extended attribute names must be unique and must not duplicate any application schema attribute name, or aggregation may not update values correctly.

Customized .hbm.xml files live under WEB-INF and are overwritten on upgrade, so keep copies and reapply them.

Last updated: September 2026

Creating Extended Attributes and the Objects That Support Them

Blueprint objective 1.3 asks you to demonstrate knowledge of creating extended attributes . Objective 7.4 asks which common IdentityIQ objects can have extended attributes . The two go together: you create an extended attribute on one of those objects, and where it is stored decides whether you can search on it.

What an Extended Attribute Is

Every IdentityIQ object class has standard attributes built into the product, such as an identity's firstname , lastname , email , and manager . An extended attribute is one you add for your organization, such as costCenter on identities, privileged on accounts, or riskTier on applications. The definitions are kept in an ObjectConfig object for the class. The console command oconfig lists every class that has an ObjectConfig and its extended attributes, numbered by their extended column slot.

Which Objects Support Extended Attributes

Object (class) What it represents Where you define the extended attribute Mapping file

Identity The identity cube for a person or non-human identity Global Settings > Identity Mappings IdentityExtended.hbm.xml

  • Link An account on an application Global Settings > Account Mappings LinkExtended.hbm.xml
  • Application An application definition Global Settings > Application Attributes ApplicationExtended.hbm.xml
  • Bundle A role Global Settings > Role Configuration (extended attributes) BundleExtended.hbm.xml

ManagedAttribute An entitlement or account group in the Entitlement Catalog Global Settings > Entitlement Catalog Attributes ManagedAttributeExtended.hbm.xml

CertificationItem A line item in an access review Mirrors the account attributes CertificationItemExtended.hbm.xml

The installation guide also lists TargetExtended.hbm.xml (permission targets) and AlertExtended.hbm.xml (activity alerts). For the exam, focus on the six rows above. Extended attribute questions almost always involve identities, accounts, applications, roles, entitlements, or certification items.

Two Ways to Store a Value

Non-searchable. The value is stored in the object's serialized XML attributes map. It displays and can be used in rules, but it cannot be filtered in searches.

Searchable. The value is copied into a real database column so that searches, filters, populations, and reports can query it. The column must already exist in the Hibernate mapping.

Searchable columns come in two styles:

Numbered columns – properties named extended1 , extended2 , and so on. The Edit Identity Attributes page says the default number of searchable identity attributes is ten . The installation guide lets you add numbered properties up to a maximum of twenty.

Named columns – a property with a meaningful name, such as costCenter . Hibernate turns camel case into a lower-case, underscore-separated database column ( cost_center ). When you map an attribute to a named column in the UI, you enter the .hbm.xml property name , not the database column name.

An example of adding numbered, indexed identity properties to IdentityExtended.hbm.xml : <property name="extended1" type="string" length="450" index="spt_identity_extended1_ci"/>

  • <property name="extended2" type="string" length="450" index="spt_identity_extended2_ci"/>
  • <property name="extended11" type="string" length="450" index="spt_identity_extended11_ci"/>

Adding index="spt_identity_extendedN_ci" creates a case-insensitive index for that column. Identity attributes of type Identity , which point at another identity such as a region owner, are stored in separate extended identity fields. oconfig lists them in their own sub-list.

Creating an Extended Attribute: The Procedure

Plan the columns. Decide which attributes must be searchable. If the default slots are not enough, edit the relevant *Extended.hbm.xml file in WEB-INF/classes/sailpoint/object .

Regenerate and apply the DDL. Run iiq schema to produce new database scripts. On a new install, create the database with them. On an existing install, apply the column changes to the database.

Define the attribute in the UI. Use the matching Global Settings page. Give it an Attribute Name (the name rules use) and a Display Name , choose a type, and select Searchable if it needs a column.

Map its sources. Identity and account attributes take their values from source mappings : application attributes, application rules, or global rules (section 16.3). Application, role, and entitlement attributes are usually entered in the UI and can have allowed values, default values, and a Required flag for string types.

Populate it. Identity attributes are promoted during aggregation and identity refresh. Account attributes are filled from their source mappings during aggregation.

Rules That Produce Exam Traps

Names must be unique. The documentation warns that an extended attribute must not share a name with any attribute in any application schema . If an extended attribute matches a schema attribute, values may not update correctly during aggregation. A standard prefix avoids collisions.

You cannot reuse a standard identity attribute name for an identity extended attribute.

Renaming is risky. Changing an attribute name can make previously aggregated values unrecognizable.

Accounts and certification items move together. If you change the account (Link) extended attributes, make the same change to the CertificationItem attributes. This lets searchable account values be stored on certification items for searching and status icons.

Upgrades overwrite WEB-INF . Customized IdentityExtended.hbm.xml , LinkExtended.hbm.xml , and CertificationItemExtended.hbm.xml files must be saved and copied into the new installation before upgrading the database.

Keep the default mappings. AI-Driven Identity Security (formerly AI Services) needs every default field in the .hbm.xml files. Add columns, but do not remove the defaults.

Account attributes can drive icons. An extended account attribute such as privileged or service can show an icon in certifications and identity pages. You set this with an AccountIconConfig entry in the UIConfig object.