POST /api/source/loadEntitlements

Identity Security Cloud (ISC) Non-Public API Deprecations
,
42

“Import-BetaEntitlements” is the correct one, just a bit outdated

It points to /entitlements/aggregate/sources/{id}

After commenting out some pre-populated stuff in the SDK file BetaEntitlementsApi.ps1, Import-BetaEntitlements works like a charm :slight_smile:
Therefore I am just waiting for an SDK update

# HTTP header 'Content-Type'
#$LocalVarContentTypes = @('multipart/form-data')

<#if (!$CsvFile) {
            throw "Error! The required parameter `CsvFile` missing when calling importEntitlements."
        }
        $LocalVarFormParameters['csvFile'] = $CsvFile
        #>

This is what I can run and it will import newly created entitlements to IDN and I could also make sure it has completed by checking status in a loop looking for “SUCCESS” before next step.

# Get specific source
$Source = Get-Sources -Filters $('name eq "' + $EntitlementSourceName + '"') | Select-Object Name,Id

# Start entitlement aggregation
$Aggregation = Import-BetaEntitlements -Id $Source.id

# Check aggregation status
$Status = Get-BetaTaskStatus -Id $Aggregation.id
$Status.completionStatus
43

Thanks Colin. This issue with the API where descriptions are not updating from AD, and unoptimized aggregation is not available, has been opened as support case CS0293994.

1 Like
44

Hi all,

This remark is related to importing entitlements from a csv file.

We get a 400 Bad Request error when calling POST beta/entitlements/aggregate/sources/:id in production with error message The request was syntactically correct but its content is semantically invalid..
Also when trying to import the csv through the UI (which, we saw, uses the undocumented endpoint POST /beta/sources/:id/load-entitlements), we receive the same error (both when the UI calls this API or when we call the API manually).

We then tried the endpoint POST /cc/api/source/loadEntitlements/:cloudId and that was the only one that worked in production.

Using the same CSV file was working in our sandbox environment using all APIs (tried on a source with the same entitlement types and schemas).

Also, the API suggested by Colin at the top of this post lacks documentation on how to select the entitlement type. Sources can have multiple entitlement types after all, so when importing a CSV file, we should be able to tell the API which entitlement type corresponds to the csv file we send.

Kind regards,
Angelo

45

Just checked. The issue is still there. Anybody else noticing problems for uploading and entitlement CSV file for new sources using the new API?

I think it has to do with the fact whether or not your source type is Delimited File or DelimitedFile. Only the latter works. Even though the first one is a completely valid source type to have. I believe many organizations have sources where the type contains a space.

46

The issue mentioned above by Angelo is still occuring, but now also the CC api doesn’t give us anything.

So currently, we do not have an option for adding entitlements to our Delimited File sources.

47

Hi All,

@colin_mckibben to bring an new issue relevant to Entitlement groups ?
while running aggregation - it removed the existing groups from the source in IDN
and the response by sailpoint support is this

undefined
undefined1788×68 60 KB

from 25th june did sailpoint included new parameter “updated-at” that is not pulling the existing groups ?
then coupa product team shared this info from their end what they see in logs

image
image1788×678 136 KB

can we have any ambassador share

thanks
osman

48

it seems to be a connector issue and connector team is working to debug it
thanks
osman

49

@bthompson555, is there any update on AD entitlement description update issue. We are running entitlement aggregation every day, but it not able to update entitlement description if there is any change from AD side.

50

Hi Osman,

We saw similar issue that entitlements got deleted due to entitlement aggregation since after 25th June.

Did you get any resolution regarding this?

51

Just checking to see what that status is for running an unoptimized entitlement aggregation.

I’m using v2024 /entitlements/aggregate/sources/:id