64 docs tagged with "connectivity"

Create account on the source.

Intercept the account create command.

Remove account from a source.

Intercept the account delete command.

Disable an account on the source.

Intercept the account disable command.

Dynamically determine account schema from the source.

Enable an account on the source.

Intercept the account enable command.

Aggregate all accounts from the source into Identity Security Cloud.

Intercept the account list command.

Aggregate a single account from the source into Identity Security Cloud.

Intercept the account read command.

Lock and unlock an account on the source.

Intercept the account unlock command.

Update an account on the source.

Intercept the account update command.

Calling API endpoints sequentially for hundreds or thousands of accounts is slow. If several API calls are required to build a user’s account, then it is recommended that you use asynchronous functions to speed up this task.

Build and upload connectivity customizers.

Details on using the card item

Change password for an account on the source.

Intercept the change password command.

Using the CLI to properly test and debug your connector in Identity Security Cloud

These are the CLI commands most commonly used when building SaaS Connectors.

Build and expand ISC connectivity.

Connectivity customizers can customize out of the box SaaS connectors.

All commands available to implement in a SaaS Connector.

The connector spec file tells ISC how the connector should interact between ISC and the custom connector. It is the glue between ISC and the connector, so understanding the different sections are key to understanding how to build a custom connectors.

Identity Security Cloud will throw an error if your connector does not send a response in 3 minutes. For connector commands that might take longer than 3 minutes, make sure to send data at regular intervals to prevent a timeout.

Available connectivity customizer commands.

The config object in a customizer

An easy way to debug locally is to use console.log() to print debug information to your console.

Gather a list of all entitlements available on the source.

Intercept the entitlement list command.

Fetch a single entitlement’s attributes from the source.

Intercept the entitlement read command.

If the code fails due to validation issues, connectivity, or configuration errors, you can handle the error and provide the user with information about what went wrong.

Here are a few example connectors that were built for you to download and learn from.

Full connectivity customizer example.

Get started with connectivity customizers.

Rate limiting for SaaS Connectivity.

How to use the sourceConfigInitialValues field

Create an IP Address Allow List​.

Details on using the key value item

This describes certain limits that are in place when running a SaaS Connector

Link connectivity customizers to sources.

Automatically check your connector source code for programmatic and stylistic errors.

Details on using the list item

You can use this feature to read the logs of your connectors.

Use the following Postman Collection file to run tests for each of the commands locally.

These are some prerequisites you must have before you start building SaaS Connectors.

Details on using the Radio item

Cloud-based connectivity without VAs.

Details on using the select item

Discover potential source data types.

Intercept the source data discover command.

Read source data.

Intercept the source data read command.

Ensure the connector can communicate with the source.

Intercept the test connection command.

As you implement command handlers, you must test them. The connector SDK provides some utility methods to locally run your connector to test, build, and deploy.

Testing SaaS Connectivity.

Test and debug connectors with customizers.

Helpful videos on using SaaS connectivity