[Connector Error] No configuration found for "Add Entitlement-"

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hello All,

I’m about to configure new source via SaaS Web Connector and with the update operation i’m receiving following error.
[Connector Error] No configuration found for “Add Entitlement-”

image
image871×489 19.6 KB

The thing is that i have only one entitlement type (default ‘group’) and HTTP for “Add entitlement” call was created. Whats more this error appears even with simple attribute update.

Ony one of you had this issue before

2

Hi @radoslaw_klimkowski ,
The similar issue is addressed here : No configuration found for 'Group Aggregation'

Thanks
Gourab

1 Like
3

thanks @gourab for fast reply however.
The thing is that we have “Group Aggregation” call and it’s properly retrieving all groups with id’s and names:
Entitlement Schema is configured with two attributes (groupId, groupName)

image
image1033×276 12.9 KB

HTTP call for entitlement update is also configured
image

But whenever i try to sync attibutes i get error like “Add Entitlement-” call is missing. Is that “-” at the end cn be a clue?

4

Hi Radoslaw,

Do you have multiple entitlement types for this source? If so, there will be a dropdown option in the operation type like ‘Add Entitlement-group’ I believe. This lets the connector know what operation to use for different entitlement provisioning.

Thanks,

Liam

5

Hey @liamkokeeffe
Unfortunatelly there only one default entitlement (“group”) and in HTTP call there’s only one “Group Aggregation” option.

6

Interesting, this looks like a connector bug, but I found another dev forum post for a similar issue - Webservice - No configuration found for 'Add Entitlement-underfined.

This user was able to fix their issue by updating their ‘Add Entitlement’ operation type to match the one shown in the error. So in your case you would do a full source update through the API and update the operation type to ‘Add Entitlement-’. Feels like a hacky fix though, maybe reaching out to SailPoint support or re-creating the source would be a good idea as well.

Thanks!

Liam

7

I encountered a similar issue with the WS SaaS connector that we were using to provision an account. To resolve it, I created an operation for “Add Entitlement” where we returned the default group, let’s call it “DefaultAppGroup” used for auto-provisioning the account. I applied a similar approach for “Remove Entitlement” since disabling the account triggers the remove entitlement action. This workaround helped address the issue. Let me know if you need any other information.

1 Like
8

Hello All,

Many thanks for the feedback. At this moment i’ve support inc opened with Sailpoint.
I translated whole web connector into non-SaaS version and everything is running smoothly. I guess this is a backend connector bug

I’ll inform you if Sailpoint support will find anything