Study guide
12.1 Configuring Application Definitions
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
12.1 Configuring Application Definitions
Key Takeaways Explain This Topic AI
A connector is the template for talking to a kind of system; an application is a configured instance with its own name, connection parameters, and schema.
Marking an application Authoritative makes aggregation create an identity for each account; non-authoritative accounts are correlated to existing identities.
The application owner reviews access in owner certifications and approves entitlement requests by default; the Revoker, if set, receives revocation work instead.
Maintenance Enabled skips the application in aggregations and returns retry status for provisioning until the window ends.
Application names cannot start with a number or exceed 31 characters, and XML edits should be made on an exported copy, not in the Debug pages.
Last updated: September 2026
Configuring Application Definitions
Objective 5.1 asks you to configure application definitions . Every system IdentityIQ governs, such as HR, Active Directory, a database, or a SaaS application, is represented by an Application object, configured on Applications > Application Definition .
Connectors vs. Applications
A connector is a template for talking to a type of system. It knows how to connect, read, in many cases write, and turn source data into normalized ResourceObjects .
An application is a configured instance of a connector. It has a unique name, connection parameters for one specific system, and a specific schema.
You can create many applications from one connector. For example, ten Delimited File applications can each read a different file with a different schema. Applications can be read-only or read-write , depending on whether the connector supports provisioning. IdentityIQ also has activity-type connectors that collect activity data instead of accounts.
The Details Fields
Field What it controls
Name Unique name. It cannot start with a number or exceed 31 characters .
Application Type The connector. This decides which configuration options appear. Some connectors may not be enabled in your instance.
Owner The business owner, an identity or preferably a workgroup . It reviews access in application owner and account group certifications and, by default, approves entitlement requests for the application.
Revoker Receives revocation requests from certifications and policy violations. If blank, the owner gets them.
Description Can be multi-language when enabled (section 11.3)
Proxy Application Another application that aggregates and provisions on this one's behalf, for example multiplexed applications split by a build map rule, legacy provisioning systems, or a Cloud Gateway for a remote network
Profile Class Groups applications for role modeling, so one role profile can match privileges on any application with that class
Scope Only visible when scoping is enabled. Only the owner or users controlling the scope can work with the application.
- Authoritative Application Aggregation creates an identity for every account
- Case Insensitive Case-insensitive comparison of account attribute values when evaluating provisioning policy
Native Change Detection Detects changes made directly on the target, by chosen operations and attributes (entitlements or user-defined). Feeds Native Change lifecycle events.
Maintenance Enabled / Expiration Takes the application offline . Aggregations skip it with a warning, and provisioning returns retry . With no expiration, maintenance lasts until someone clears it.
Authoritative vs. Non-Authoritative
An authoritative source, typically HR, is the most trusted record of who people are . Aggregating it creates identity cubes and supplies attributes such as name, department, manager, and status. A non-authoritative source, such as Active Directory or an ERP, has accounts that must be correlated to existing identities. An organization can have several authoritative sources , for example employees from HR and contractors from a vendor system. When a non-authoritative account matches no identity, it becomes an uncorrelated account . You can fix correlation logic or manually correlate it on the Identity Correlation page. Manual correlations are kept permanently and are not changed by later aggregations.
The Edit Application Tabs
Tab Purpose
Configuration Settings (connection, partitioning, merging, delta), Schema , Provisioning Policies , and object types (section 12.2)
- Correlation Attribute-based and condition-based account correlation, plus manager correlation
- Accounts The aggregated accounts, after the application is saved
- Risk Application risk score components
- Activity Data Sources Collectors that read activity logs
- Unstructured Targets Permission targets such as file shares
- Rules Aggregation, provisioning, schema, and connector rules (sections 13.2 and 13.3)
Password Policy Password rules for this application, such as length, character types, history, dictionary, and identity-attribute checks
Tiers Logical applications only
The documentation warns: do not edit the same application in multiple browser tabs . Saving in one can overwrite changes made in the other.
Correlation Configuration in Brief
Attribute-based – for example, the account attribute mail equals the identity attribute email . This is the usual approach.
Condition-based – for accounts without identifying attributes, such as a Unix root account assigned to the application owner. These configurations can be saved and shared across applications.
Rules – a Correlation rule for complex logic (section 9.2).
Manager correlation – pairs an application attribute, such as managerEmail , with an identity attribute, such as email , to set each identity's manager.
Onboarding Checklist for a New Application
Pick the connector type and create the application with a clear name, an owner workgroup, and a revoker if different.
Fill in the connection settings and run Test Connection .
Define or discover the account schema (and group schema), and set the identity, display, entitlement, and managed attributes (section 12.2).
Configure correlation , for accounts and managers.
Add provisioning policies if the application is read-write.
Create an Account Aggregation task (and Account Group Aggregation), run it in a sandbox, and review uncorrelated accounts.
Add rules only where configuration cannot do the job (sections 13.2 and 13.3).
Optionally, hand business onboarding to Rapid Setup (section 12.3).
Changing an Application Safely
Reconfigure changes an application's type without losing history . For example, a Delimited File application for AD can become Active Directory – Direct, or a JDBC application can become a direct connector. It works best when account and group identity attributes have the same format in both types.
XML edits. Some connector options exist only in the application XML. The documentation advises checking out the single application ( checkout application "<name>" file.xml ), editing it outside IdentityIQ, testing it, and importing it. Avoid direct Debug-page edits, which have no rollback .