# Source Updated Trigger

The source updated trigger is fired when configuration changes are made to a source.

Some uses cases for this trigger are:

  • Provide evidence to show auditors that connector logic and sources are not manipulated outside of proper change control processes.
  • Trigger review of an updated source.

# Getting Started

# Prerequisites

  • An oAuth Client configured with Authority as ORG_ADMIN.

# In This Topic


# Event Context

Source Updated events occur when configuration changes are made to a source.

Use the following command to view the Source Updated Trigger details:

curl --request GET --url 'https://{tenant}.api.identitynow.com/beta/triggers' --header 'authorization: Bearer {access_token}'

# Trigger Type

This event trigger type is a FIRE_AND_FORGET type. When you subscribe to this event trigger with your HTTP endpoint, a response is not expected to be returned.

# Input Schema

The input schema defines what you will receive from the trigger service. Here is input example provided by the trigger if a source is updated by a user:

{
    "modified": "2021-05-04T19:35:43.997Z",
    "id": "8a807dc479004c8b0179004cd87b0252",
    "name": "Arrested AD",
    "type": "Active Directory - Direct",
    "connector": "active-directory",
    "actor": {
        "id": "ee769173319b41d19ccec6cea52f237b",
        "name": "john.doe",
        "type": "IDENTITY"
    }
}

SailPoint periodically updates the Connectors for your Sources. If we make a Connector update that results in a Source Update, you'll see an event that looks like:

{
    "modified": "2021-05-04T19:35:43.997Z",
    "id": "8a807dc479004c8b0179004cd87b0252",
    "name": "Arrested AD",
    "type": "Active Directory - Direct",
    "connector": "active-directory",
    "actor": {
        "name": "SYSTEM",
        "type": "IDENTITY"
    }
}
  • modified - The date and time the source was modified
  • connector - The connector type used to connect to the source
  • name - The user friendly name given to this specific source
  • id - Unique ID assigned to the source
  • type - The connection type
  • actor - The Identity or system that performed the update

# Subscribe to the Source Updated Trigger

To subscribe to the Source Updated Trigger, make a POST call to /beta/trigger-subscriptions with the following headers and body:

Headers:

  • Authorization: Bearer <access_token>

Body:

{
   "triggerId":"idn:source-updated",
   "type":"HTTP",
   "httpConfig":{
      "url":"https://urlOfTheExternalService.com",
   }
}

# Testing Tools

  • webhook.site (opens new window) - This tool creates a temporary HTTP endpoint for you to verify that you are able to successfully subscribe to the Event Trigger. You can receive the event after an access request has been submitted. Copy the "unique URL" from webhook.site and use it in the url field of the POST body to /beta/trigger-subscriptions.
  • localhost.run - This tool creates an endpoint for a HTTP server running on your local machine.