Delta Aggregation Settings and Common Configuration

Feedback Documentation Feedback Connectivity Documentation Feedback
1

In the Connection Timeout (in seconds) field, enter the connection timeout value in seconds.

This is the companion discussion topic for the documentation at https://documentation.sailpoint.com/connectors/webservices/help/integrating_webservices/delta_aggregation_settings_and_common_configuration.html
2

Please update the original document to include this information, it may save people hours of troubleshooting erorrs with privatekeys.

To convert the .key file to a compatible RSA PEM file you may need to add
-traditional to the end of the command.
openssl rsa -in currentprivatekey.key -out newprivatekey-with-rsa.pem -traditional

As per this post
(ssl - How to convert a private key to an RSA private key? - Stack Overflow)

Newer versions of OpenSSL say BEGIN PRIVATE KEY because they contain the private key + an OID that identifies the key type (this is known as PKCS8 format). To get the old style key (known as either PKCS1 or traditional OpenSSL format) you can do this:

openssl rsa -in server.key -out server_new.key

If you are using OpenSSL 3, you need to add -traditional

openssl rsa -in server.key -out server_new.key -traditional

Alternately, if you have a PKCS1 key and want PKCS8:

openssl pkcs8 -topk8 -nocrypt -in privkey.pem
3

THe Delta Aggregation and Common Configuration sections should be split into their own sections to follow your existing pattern, and to make the Common Configuration easier to find, since it is not related to Delta Aggregation.

4

Can you expand the Common Configuration examples for using a Boolean Value, assuming it still works.

We have an client who has configured a Boolean Attribute in their schema, ie. “accounttIsActive”, and set the “Account Enable Status Attribute” to be “accounttIsActive=true”. However, after aggregating the values, the Account “Status” attribute still shows as “Enabled” in the UI for all users, even those with “accounttIsActive=false”.

Questions I would have:

  • Do Boolean values require a different format?
  • Do the boolean values require case-sensitive formatting? If so, which?
  • Is there something else needed for this to be processed? If this is set after the initial aggregation, is an unoptimized Aggregation required?
5

Just tried the API call to aggregate with disableOptimization set to true, and it did not change the value.

6

In the Common Settings section, the Note under #3 has the following line under the 3rd bullet point:

This feature’s supported types are string , integer , and Boolean .

Screenshot 2025-06-02 at 11.22.38 AM
Screenshot 2025-06-02 at 11.22.38 AM1992×558 94.4 KB

This should probably be part of the primary information in the #3 bullet point, or at minimum, it’s own bullet point under the note (ideally first, if this is the case.)

8

Hi Geoff! Thank you for all your input. I’ve created a Jira issue to track the effort for all of this and I’ll update the comment thread when it’s been addressed: CONDOCS-6931