Study guide
12.2 Configuring Common Connector Settings
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.2 Configuring Common Connector Settings
Key Takeaways Explain This Topic AI
The Settings tab holds connection parameters, Test Connection, and the partitioning, merging, and delta aggregation options that the connector supports.
Every application needs an account schema with an Identity Attribute (the unique account ID) and a Display Attribute.
A group schema is linked to accounts by setting the account entitlement attribute's Type to the group schema's Native Object Type.
Entitlement marks an attribute as access to track; Managed puts values in the Entitlement Catalog so they can have owners, descriptions, and be requestable.
Applications support one each of the Create, Update, Delete, Enable, Disable, Unlock, Change Password, CreateGroup, and UpdateGroup provisioning policies.
Last updated: September 2026
Configuring Common Connector Settings
Objective 5.2 is configure common connector settings . Connectors differ, but most applications share the same three sub-tabs on Configuration : Settings , Schema , and Provisioning Policies .
Settings: Connecting and Reading
The Settings tab holds the connection parameters for the connector type. Use Test Connection to verify them. Settings also hold the connector's options for partitioning , data merging , and delta aggregation , where supported.
Example: Delimited File
Setting Notes
File Path , File Encoding The file to parse. With no encoding set, the server default is used.
File Transport Local, FTP, FTPS, SCP, or SFTP, with host, port, and credentials. The account running the application server needs read access for Local.
Parsing Type Delimited (with a delimiter such as \\u0009 for tab) or Regular Expression (groups define tokens)
File has column header on first line / Columns Columns are required for regex parsing, or when there is no header, or to rename columns used by the BuildMap rule
Fail on column length mismatch Fail when a line lacks columns
Filtering Lines to skip, filter empty objects, a comment character, and a Filter String (for example, department == "Manufacturing" ) that drops matching objects
Merging For objects spanning multiple lines: Index Column , whether data is sorted by it (otherwise an in-memory merge is built), ignore case, and which columns to merge
- Iteration Partitioning Auto (calculated) or Manual (objects per partition)
- Example: JDBC
Connection settings include the database URL , JDBC driver , and credentials. You also define the account SQL statement or stored procedure . If one account spans several rows , enable merging with index columns, and the SQL must include ORDER BY on those index columns. The JDBC connector supports aggregation, delta aggregation , partitioning, account and group management, and provisioning rules , either one rule for every operation or a separate rule per operation (Create, Modify, Delete, Enable, Disable, Unlock).
Schema: What Gets Read
Every application needs an account schema . Many also have group (account group) schemas, and some connectors support multiple object types , each with its own schema. Use Discover Schema Attributes where supported, then Preview to test.
- Schema field Meaning
- Native Object Type The object on the target, such as User and Group, or DBA_USER and DBA_ROLES
Identity Attribute (required) The unique identifier of the object on the source. It becomes the account's native identity . Do not change it on connectors with predefined schemas.
- Display Attribute (required) The name shown in the UI
- Instance Attribute Identifies a specific instance of a multi-instance application
- Include Permissions Adds directPermissions for connectors whose feature string includes DIRECT_PERMISSIONS
- Group: Description Attribute Fills the ManagedAttribute description during group aggregation
Linking accounts to groups: set the Type of the account schema's entitlement attribute (for example, memberOf ) to the Native Object Type of the group schema (often group ). Account values then map to the group schema's identity attribute.
Attribute Properties
Property Effect
Entitlement Tracked as access. Used in certifications (additional entitlements), role profiles, account group certifications, and LCM.
Managed Values become ManagedAttributes in the Entitlement Catalog , where they can be requestable and have owners, display names, and descriptions. Group aggregation adds all groups to the catalog automatically.
- Multi-Valued Stored as a list, even with one value
- Correlation Key Used only for activity and unstructured-data correlation, not account correlation
- Minable Returned to role mining and profile creation
- Remediation Modifiable Certifiers can change the value during a review: Select , Free text , or Readonly
Schema rules to remember: attribute names cannot begin with IIQ_ (reserved), and they must not duplicate extended attribute names (section 2.3).
Delta Aggregation, Partitioning, and Features
Delta aggregation is enabled in the aggregation task, but it works only if the connector supports it . Some connectors need extra settings on the application, such as a delta table or change-tracking column for JDBC. Delta aggregation can be partitioned only if the connector implements partitioning. Otherwise it runs single-threaded.
Partitioning must be configured on the application (Settings) and enabled in the task. If the connector cannot partition, IdentityIQ falls back to generic (task-level) partitioning at the database level (section 2.1).
Features. Each connector advertises what it can do, such as provisioning, enable/disable, unlock, password changes, direct permissions, and delta. UI options appear only when the feature is present. That is why a provisioning policy type or an Include Permissions checkbox may be missing for some applications.
Provisioning Policies: What Gets Written
For read-write applications, provisioning policies list the attributes each operation needs. The types are Create , Update , Delete , Enable Account , Disable Account , Unlock Account , Change Password , CreateGroup , and UpdateGroup . Only one of each type is allowed, and not every object supports every type. Fields calculate values from literals, scripts, or rules, such as return identity.firstname , or ask a person (section 4.2). Review Required makes the approver review a calculated field. Some connectors ship predefined Create policies that you can modify.
Application Dependencies say a user needs an account on another application first. If it is missing, IdentityIQ adds an account request for it, and dependent field values can be read from that application. Dependencies are enforced on Create operations only.