Genetec ClearID Connector


:spiral_notepad: Description SaaS Connector for Genetec ClearID
: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-genetec-clearid: SaaS Connector for Genetec ClearID
: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

This is a Genetec ClearID connector.

Requirements

Guide

Supported Operations

2 Likes

Hello, has anyone had any recent success with this custom connector in ISC?

Hi Danielle,

It’s been a while since I created this connector so it may be broken due to changes on SaaS Connectivity and ClearID. I would need help understanding the latest changes in ClearID. If this is important to you, we could work together so I update the connector to a working version.

I look forward to your feedback.

I am attempting to use this connector.

It appears to read accounts successfully, but I haven’t seen it successfully sync attributes, and I’m just getting into acountCreate - but so far that’s failed, too.

Hi David, I’ve had success syncing attributes after updating the attribute names in ISC. I believe during the initial source aggregation the attributes pull in as companyData.departmentName for example. However, adding a new attribute in ISC with name “departmentName” & adding this to the create account config allows me to sync this attribute.

Can someone assist me with the proper config settings for this connector? Looking to keep the schema as minimal/default as possible in order to automate employee badge terms. Struggling with getting a generic API error. Can’t tell where we’re going wrong. After hitting test connection, we’re getting

 
Test Connection Failed

We have detected an error from the managed system.

Error Received:

[ConnectorError] error receiving response from connector: stream client connection is broken (connector process may have crashed) (requestId: 21c1643b8403407f8711964c226ed184)

What did ya’ll have to configure after uploading and creating a new connector from this? Is it possible the api endpoints went from a microservice model to the simple api.* unified model, causing a break?

Hi Aaron, please see what I told Danielle. This connector is outdated and it needs significant work. I cannot do it alone. If you’re willing to help me by testing it, providing feedback, etc., please contact me directly.

Thanks a ton for replying! I’d love to help you. You may need to message me, as I can’t message you on here yet it seems.

Hey Fernando - interested in pursuing this if you have the time. We use SP for thousands of users and could benefit from this. Feel free to contact me at aaron.glass@group1001.com - there does not seem to be a way for me to message you directly on here.