Hello, I’ve been trying to setup a webservices connector in our tenant and I’m having difficulty with the account/entitlment aggregation that doesn’t make any sense compared to previous configurations. Wondering if anyone else has ever had this problem, or if it’s a thing I should open a support ticket for due to buggy behavior.
To start I have a standard webservices connection setup for our FTP product. I am able to aggregate accounts just fine, however, there is no entitlement endpoint, the entitlements are just on the get user endpoint, so i have been trying to get the entitlements from just scanning accounts. however even though the accounts come in just fine entitlements are not.
if you look at the account in the identity they are mapping correctly to the schema.
but when you click on an entitlement,
I have tried multiple troubleshooting steps, resetting source, unoptimized aggs, schema deletes, changing the entitlement type, going as far as to make a second source to test that it was not a source issue, the same thing is happening, the account aggreagtion is a 2 step agg, first is a get users call to return the list of ids, the child endpoint is then calling get user with the $response.id$.
here is a payload example
here’s the response mapping
here’s the account schema
to me, everything looks correct, the mappings are obviously correct because the accounts list the entitlements, but identityNow is not picking up on them as entitlements to be assigned.
