Issues with Identity Fusion Connector

[kburetta (Kevin Burett)]

I’m currently having some issues deploying this connector from the CoLab: Identity Fusion Connector

The guides for it don’t effectively explain which “.zip” file should be downloaded and then how it should be added into your SailPoint environment.

What I’ve discovered so far through experimentation….

The CoLab > SaaS Connectors category page itself doesn’t have any option to download the connector code. If you follow from the category page to the actual connector wiki page, and then to the backing github repo (identity fusion github), one can there download the source code as a .zip file, but that instruction is not clearly stated in any of the guide materials.

Further, I discovered that based on other topics in the community space that there is an additional ‘build’ step that is required before uploading the connector to your Sailpoint environment. First, you need to have nodejs, npm, and several other dependencies already installed on your system, and then you must use the code downloaded from github, unzip it, and build your deployable connector .zip file using the “npm install” and “npm pack-zip” commands. These steps would be really helpful to include in either the install guide on the wiki page, or the one on the github installation notes.

Despite figuring out all of the above, I managed to get the connector added to my SailPoint ISC environment and then configured it with some account sources to attempt an aggregation.
I then ran into some errors according to the debug logs:

“Command failed with [ConnectorError] command inactive for 10m0s: std:account:list, for connector version 1.output_count=0 keep_alive_count=0 state_count=0. Elapsed time 600007ms”

This error occurs in the logs after the connector is paginating through a source with 20000+ records. Then a couple minutes later, I get these two:

“FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory”
“Command failed with [ConnectorError] error receiving response from connector: stream client connection is broken (connector process may have crashed): std:account:list, for connector version 1.output_count=0 keep_alive_count=0 state_count=0. Elapsed time 161369ms”

Really trying to be optimistic about the potential value of using this SaaS connector, but getting off to a rocky start with it. Any help would be very appreciated. Connector debug logs attached
Fusion-Debug-Clean.log (44.7 KB)

[philip-ellis]

I’m doing a demo of the fusion connector on Wednesday, with a new release of the fusion connector. I’m guessing you are still using the original connector which is missing a lot of enhancements as well as features that should make it work a lot better. It might be worth attending: Livestream: Duplicate Detection with the SaaS Fusion Connector

[kburetta (Kevin Burett)]

Hey Philip, thanks for the reply. I’m going to try to attend your livestream on Wednesday to learn more.

How does one get access to the new release of version of the connector with the enhancements as you mentioned? Is it just one of the other github branches?

[kburetta (Kevin Burett)]

I’ve downloaded, built, and deployed the new v0.0.5 version of the connector but still have the same errors when attempting an aggregation action.

[2025-02-18T14:32:19.493-08:00] INFO  | connectorMessage ▶︎ {"commandType":"std:account:list","invocationId":"d15e72e4-f094-48be-bb5a-0cb79a9e66db","message":"Paginating call, offset = 4500\n","requestId":"2aefc15c14de4ca78f23933c7292452d","version":1}
[2025-02-18T14:32:19.636-08:00] INFO  | connectorMessage ▶︎ {"commandType":"std:account:list","invocationId":"d15e72e4-f094-48be-bb5a-0cb79a9e66db","message":"Processing existing identities.","requestId":"2aefc15c14de4ca78f23933c7292452d","version":1}
[2025-02-18T14:33:28.059-08:00] INFO  | commandOutcome   ▶︎ Command failed with [ConnectorError] command inactive for 10m0s: std:account:list, for connector version 1.output_count=0 keep_alive_count=0 state_count=0. Elapsed time 600027ms
[2025-02-18T14:33:51.811-08:00] INFO  | connectorMessage ▶︎
[2025-02-18T14:33:51.811-08:00] INFO  | connectorMessage ▶︎ <--- Last few GCs --->
[2025-02-18T14:33:51.811-08:00] INFO  | connectorMessage ▶︎
[2025-02-18T14:33:51.811-08:00] INFO  | connectorMessage ▶︎ [207:0x7f485d165340]    90549 ms: Mark-sweep 3624.4 (3688.7) -> 3623.6 (3688.9) MB, 6433.8 / 0.0 ms  (average mu = 0.485, current mu = 0.000) allocation failure; scavenge might not succeed
[2025-02-18T14:33:51.811-08:00] INFO  | connectorMessage ▶︎ [207:0x7f485d165340]    98542 ms: Mark-sweep 3624.6 (3688.9) -> 3624.1 (3689.2) MB, 7990.3 / 0.0 ms  (average mu = 0.256, current mu = 0.000) allocation failure; scavenge might not succeed
[2025-02-18T14:33:51.811-08:00] INFO  | connectorMessage ▶︎
[2025-02-18T14:33:51.811-08:00] INFO  | connectorMessage ▶︎
[2025-02-18T14:33:51.811-08:00] INFO  | connectorMessage ▶︎ <--- JS stacktrace --->
[2025-02-18T14:33:51.811-08:00] INFO  | connectorMessage ▶︎
[2025-02-18T14:33:51.811-08:00] INFO  | connectorMessage ▶︎ FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
[2025-02-18T14:33:51.981-08:00] INFO  | commandOutcome   ▶︎ Command failed with [ConnectorError] error receiving response from connector: stream client connection is broken (connector process may have crashed): std:account:list, for connector version 1.output_count=0 keep_alive_count=0 state_count=0. Elapsed time 98951ms
[2025-02-18T14:36:18.121-08:00] INFO  | commandOutcome   ▶︎ Command failed with [ConnectorError] command inactive for 10m0s: std:account:list, for connector version 1.output_count=0 keep_alive_count=0 state_count=0. Elapsed time 600009ms

Any chance this issue could be related to deploying this connector in a sandbox tenant?