Delimiter File Connector / Flat File Connector overview
This is the OOTB Connector which comes with the Sailpoint IdentityIQ Application and supports Aggregation of both the Accounts and Group object (Entitlement).
Connector Supports
- Reading data from a file which can be located locally or which is accessible from the application via FTP or SCP .
- Connector Supports files separated by a comma, semicolon, pipe or regular expression
- Supports different filtering options on the Files
- Supports the merging functionally like how multiple records can be merged into the single
- The connector also supports partition like how much records batch which will be created.
Create the 2 Sample file (Account file &Entitlement file ) sunAccount.csv and sunRole.csv before on boarding any delimiter type application.
Navigate to Applications -->Application Definition -->Add New Application
Select Application Type as DelimitedFile and set the other mandatory Attributes
2. Adding group object
Navigate to Configuration -->Setting-->Add object type
3. Account and Group Source File Information
Configure the File Path, File location, Delimiter Type and other different setting based on the file need to be on-bordered for both account and group object. refer to the below as shown in the screenshot.
4.Configure Account and Group Schema
Click on Discover Schema Attribute which will automatically populate the schema attribute for both the Account and Group Object type, this values will be populated from the Account and Group files. Make sure identity Attribute is populated this attribute is used to decide the uniqueness of the object/.
Since we have an entitlement file and the account contains the group, make sure the Role attribute on account object is set as type Role and of type entitlement and multi-valued.
5.Correlation Configuration
Click on New and create a new Correlation rule by selecting USERNAME Attribute from the account file = name attribute from the user identity, make sure that once the rule is saved it will be visible in attribute-based correlation.
6.Aggregation Task
Creating a Group Aggregation Task
Setup -->Tasks --> New Task --> Account Group Aggregation
Make sure the Task is created with the proper selection of different options available in the task definition.
Creating an Account Aggregation Task
Setup -->Tasks --> New Task --> Account Aggregation
Make sure the Task is created with the proper selection of different options available in the task definition.
7.Confirming Correlations and Accounts
Navigate to Application --> Entitlement Catalog and see if the Entitlement is getting loaded from the Role file.
Click on New and create a new Correlation rule by selecting USERNAME Attribute from the account file = name attribute from the user identity, make sure that once the rule is saved it will be visible in attribute-based correlation.
6.Aggregation Task
Creating a Group Aggregation Task
Setup -->Tasks --> New Task --> Account Group Aggregation
Make sure the Task is created with the proper selection of different options available in the task definition.
Creating an Account Aggregation Task
Setup -->Tasks --> New Task --> Account Aggregation
Make sure the Task is created with the proper selection of different options available in the task definition.
7.Confirming Correlations and Accounts
Navigate to Application --> Entitlement Catalog and see if the Entitlement is getting loaded from the Role file.
Same way validate the Account and Entitlement of the user which is being loaded, Open the user identity from Identity warehouse and check the Application and Entitlement details of the user
Error: To parse the file you must specify either a delimiter or a regular expression, both options cannot be specified.
ReplyDeleteAny Advice??
Make sure you have you are properly configuring "Parsing Type" and "Delimiter" in Configuration -->Setting Tab
DeleteI am also facing the similar error i.e. "To parse the file you must specify either a delimiter or a regular expression, both options cannot be specified."
ReplyDeleteI have configured the Parsing Type as "Delimited" and "," as delimiter. But still facing the same issue
you need to put character based on which you have separated your data in the file in the textbox field for Delimiter.
Deleteyou need to put a punctuation marks comma in the textbox field for Delimiter. Hope this helps
ReplyDeleteme too faced d same issue....Can anyone help on it
ReplyDeleteyou need to put character based on which you have separated your data in the file in the textbox field for Delimiter.
DeleteThe "To parse the file you must specify either a delimiter or a regular expression, both options cannot be specified." is a bug it seems
ReplyDeleteTo parse the file you must specify either a delimiter or a regular expression, both options cannot be specified.
ReplyDeleteANYONE HELP THIS ISSUE
mee to faced the same issue......
ReplyDeleteMake sure that, when you want to select Parsing type as 'Deliminated' at that time text box is empty for Parsing type as 'Regular Expression'
ReplyDeleteThank You Rakesh !
DeleteGood information.
ReplyDeleteSo the issue here I found that the SailPoint UI autofills the regular expression field even when it's not selected... Like Rakesh Patil has said, you need to make sure one of the fields is empty before saving the configuration.
ReplyDeleteThank You Szymon .
DeleteThis happened to me because I had saved my password for autofill. Remove that and it shouldn't do that anymore.
ReplyDeleteThank You Jan !
DeleteHi Vishal,
ReplyDeleteWhat is the difference configuring Delimited File as Authoritative and Non-Authoritative application? I know Authoritative is to create identities and Non-Authoritative is to create Accounts for Identities. But, after configuration I could see no difference in UI. Can you please help me understand or point to some link where can I find the difference.
Authoritative application is the base application (Ex: HR System/Application), where you have all the Users exist (Employee/ Non Employee) and when you aggregate it, all users gets created on IdentityIQ.
DeleteWhereas Non Authoritative application are the sub-applications and on aggregation, the users belong to it gets correlated with the existing user from the Authoritative application as per the correlation config or correlation rule.
In case the users from non-authoritative application didn't find any match, it still gets created independently without correlating to the existing Identity.
Here the term Identity and User both are synonyms. On IDM domain, we refer user as Identity.
I have implemeted the same and test connection is coming successful But still data is not population up.
ReplyDeleteAre you saying data in not coming up in aggregation?
DeleteHi There,
ReplyDeleteI am done account and group aggregation,identities not appear in identity warehouse but showing in entitlement catalog, what's that problem
Same issue i am facing, no identities are displayed. How to fix it? plz help!
Deleteidentity mappings
ReplyDeleteI am facing the issue of "unable to open the file stream to file "file location". in the beginning while giving the file path..
ReplyDeleteanyone please help me with this..
Yeah bro same here
Delete