Peloton Landview Connector

[mcheek (Mark Cheek)]

	Description	SaaS Connector for Peloton Landview
	Legal Agreement	By using this CoLab item, you are agreeing to SailPoint’s Terms of Service for our developer community and open-source CoLab.
	Repository Link	https://github.com/sailpoint-oss/colab-saas-conn-peloton-landview
	New to SaaS connectors in the CoLab?	Read the getting started guide for SaaS Connectors in the CoLab.
	Supported by	Community Developed

Overview

This connector is built for Peloton’s LandView product. It currently only supports managing entitlements as group membership, and not individual user permissions. Permissions must be assigned to groups for this to work properly.

Requirements

• SailPoint Identity Security Cloud Subscription
• Peloton LandView Instance
• LandView API token that operates as an Admin user
• SailPoint CLI
• Node.js >= 16.2.0
• TypeScript >= 4.4.3

Guide

Getting Started with SaaS Connectors in the CoLab

Use this category to view and download Identity Security Cloud (ISC) SaaS Connectivity connectors built by the community. Download the Connector To download a connector from the CoLab, follow these steps: Download the connector you want from the SaaS Connectors category. Use the SailPoint CLI to create a new connector: sail conn create "my-connector-name", where my-connector-name is the name that will show up for your connector in the SailPoint CLI. Use the SailPoint CLI to upload the connect…

Supported Operations

• Test Connection
• Account Create
• Account Enable
• Account Disable
• Account List
• Account Read
• Account Update
• Entitlement List
• Entitlement Read

[mcheek (Mark Cheek)]

Noted changes for version 0.2.0

• Added the capability for permissions to be aggregated as child entitlements of groups, see below note on additional steps to enable
• Added better logging and specified connector name in all log statements to play nicer with other connectors

Additional work required for parent/child entitlement hierarchy
You must update the group schema using the update-source-schema API endpoint, with the following request body

[
  {
    "op": "replace",
    "path": "/hierarchyAttribute",
    "value": "groups"
  }
]

This will ensure that the groups/permissions are in a parent/child relationship hierarchically.