Delimited File SaaS Connector


:spiral_notepad: Description Delimited File SaaS Connector
:balance_scale: Legal Agreement By using this CoLab item, you are agreeing to SailPoint’s Terms of Service for our developer community and open-source CoLab.
:hammer_and_wrench: Repository Link GitHub - sailpoint-oss/colab-saas-conn-delimited-file · GitHub
:open_book: New to SaaS connectors in the CoLab? Read the getting started guide for SaaS Connectors in the CoLab.
:hospital: Supported by Community Developed

Overview

The ISC SaaS Delimited File Connector enables seamless integration between Identity Security Cloud and a delimited source. This connector is designed to provide a robust set of operations for managing accounts and entitlements.

The ISC SaaS Delimited File Connector offers capabilities such as:

  • Create and modify accounts in delimited file-based applications
  • Provision and deprovision entitlements within the delimited file source
  • Long-term storage of identity-related information
  • Provides a structured way to maintain identity data for reporting purposes.

Requirements

Guide

Supported Operations

  • Test Connection
  • Account Enable
  • Account Disable
  • Account List
  • Account Read
  • Entitlement List
  • Schema Discovery
5 Likes

Hi @atarodia,

Could you please provide a few use cases when to use this custom saas connector over the generic delimited file based source?

Hey Animesh,
thanks for adding this connector. But can you please explain the functionality of this connector and additional information on setting this connector up in ISC?

Hi @TheOneAMSheriff & @shiva_Idm19,

With this connector, you can:

  1. Provision accounts directly to the Delimited File source
    – No need to manually upload CSV files or invoke APIs.
  2. Enable/Disable accounts
    – Supported if the IIQDisabled attribute is added to the schema of the Delimited File source.
  3. Delete accounts
    – Supported through a Before Provisioning Rule.
2 Likes

Does this connector also generate a manual work item for manual provisioning/deprovisioning to downstream systems by a source owner?

what scope(s) are required for the token to be granted to run this?

Hi @daveboisvert,

This connector do not generate manual work item on delimited file source but updates the attribute directly on delimited file source if sync is enabled.

The scopes that are required are as follows:

  1. idn:accounts:read
  2. idn:accounts:manage
  3. idn:accounts-state:manage
  4. idn:source-schema:read
  5. idn:source-schema:manage
  6. idn:entitlement:read
  7. idn:entitlement:manage

I did my testings through sp:scopes:all, please test again with the above mentioned.

Oh bummer. I have several applications where the app owner won’t be willing to keep updating us with files so this would be awesome to use, except the app owner still needs to do the work on the backend to manually provision/deprovision accounts (and would need to be notified of this).