IdentityNow Orphan Accounts Connector

CoLab SaaS Connectors
, ,
21

I download the project again from your repo and then :

  • remove package-lock.json,
  • npm -i (2 high severity)
  • npm run dev → error TS2353: Object literal may only specify known properties, and ‘jsonPatchOperation’ does not exist in type ‘AccountsApiUpdateAccountRequest’.
  • npm audit fix → 2 high severity remain

Do you have an idea ?

22

Funky stuff between Axios and AxiosRetry libraries. Error is gone. Let me know if you find any more issues.

23

I have another new error after npm run pack-zip, uploading zip in source :

Error: upload failed. status: 400 Bad Request
body: {“detailCode”:“Bad Request”,“trackingId”:“ee29ab2e55254c6e8aff749b42cf0d59”,“messages”:[{“locale”:“en-US”,“localeOrigin”:“DEFAULT”,“text”:“connector-spec.json file is not found”}]}

24

Try deleting the connector placeholder and source and start from scratch. I doubt is a problem with the latest code changes.

25

Found the issue : the file connector-spec.json is not at the root of the project

Moving it at the root path, upload the zip file works.
But we have an error during aggregation :
log.txt (6.2 KB)

26

I’ll do some testing myself and get back to you

27

It aggregates fine for me now. Please give it a try.

Fernando de los Rios Sanchez
Advisory Solutions Consultant
mobile: +34 647669581
[email protected]
Join the #SailPointCrew | My LinkedIn

28

Hello Fernando, Thank you so much for this connector :slight_smile:

I’m also reproducing same issues reported by @julien_mitard2

Indeed, I’m unable to upload the connector by using GitHub - fernando-delosrios/IdentityNowOrphanAccounts: IdentityNow Orphan Accounts custom connector except if I move the file “connector-spec.json” to the folder’s root. However, the aggregation fails.

Any idea how to solve this ? Thank you

29

Sorry, I forgot to push the latest fix. Tell me if v0.3.2 works for you.

Fernando de los Rios Sanchez
Advisory Solutions Consultant
mobile: +34 647669581
[email protected]
Join the #SailPointCrew | My LinkedIn

2 Likes
30

This time I think we are good :slight_smile:
You can push updates in the main repo :+1:

31

Hello Fernando,
I would like to be able to aggregates only active accounts to avoid to have too many accounts aggregated and because we don’t need to act on disable accounts… I tried to implement a source filtering in the connector attributes like :

[
  {
    "op": "replace",
    "path": "/connectorAttributes/filterString",
    "value": "(enabled == true)"
  }
]

Unfortunately, it seems not be supported. Is it possible for you to give this possibility ? Or maybe my filterString is not correct ?

32

Try enabled == “false” and let me know if that works.

33

It doesn’t work, but I added the feature to the connector. Download 0.3.3 from my personal repo.

34

Download the version 0.3.3 but I can see new feature in the source configuration and the filterstring is still not working … Where should I find the feature ?

35

There’s a dedicated setting to filter out disabled accounts. It’s not a filterstring.

36

OK then it doesn’t appear.
First try by updating the connector, second try by removing/creating a new connector.

37

image.png1873×1394 112 KB

1 Like
38

Also, I have another question : when I list all accounts from Orphan account source by API, the disabled attribute is false even is the attributes.enabled is false. Is it normal ?

image
image264×952 51.5 KB

39

I believe I sync it now with the update I just pushed.

40

Connector works as expected now ! Only enabled accounts can be aggregated and attributes are now sync (disabled and attributes.enabled).

I will be able to continue my test and integration. I think I will automate the process to add any new sources into the Orphan accounts source but it could be a must have to choose the source to aggregate by a drop down list of current sources.

1 Like