Current date in delta aggregation on webservice connector

[ssaptashwa (Sumit Saptashwa)]

Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.

We have inhouse Auth source integrated with webservice connector. We need to configure delta aggregation for which we need to pass startDate and endDate in request body. Aggregation API expects key/value pair as below in request parameters
startDate:20240601
endDate:20240602

I understand we can use “lastAggregationDate_account” in application context as endDate which supports delta aggregation. I already went through the documentation
I have some queries understanding this–

1. Will the Auth source needs to update API to consume $application.lastAggregationDate_account$ if added to request param or as URL filter?
2. Also how it is different from aggregation scheduled which is optimized anyway.
3. Is there any way to add current date or now as the startDate to get the delta accounts aggregated from auth source.

[enistri_devo (Emanuele Nistri)]

Hi @ssaptashwa,

i am not sure what you want, but for me is better using the webservice filter.
You can configure a normal aggregation filtered with today date.
Also, you can use the delta of IDNOW without problem.

[bcariaga (Braden Cariaga)]

Hello @ssaptashwa.

If you use the lastAggregationDate_account, the API must support this parameter to be passed in. Depending on the API you are using this may not be supported right out of the box without adjusting the pattern of the parameter. You can adjust the pattern using the connector_dateTimePattern & connector_serverTimeZone.

By using the lastAggregationDate_account, this puts the delta in control of the API and expects that the API will send a smaller payload with only the changes to the accounts - unchanged accounts are not expected to be sent to IdentityNow (although it doesn’t cause issues if unchanged accounts are sent). The normal optimization will have a full payload from the API and complete the processing within the IdentityNow tenant.

Per my knowledge, I am not aware of a way to capture current date during an aggregation with the configuration alone. You can implement a Web Services Before Operation rule which alters/appends the current date to the request endpoint before it is sent by IdentityNow.

Here is an example of how you could do todays date as start date and tomorrows as end date in a Before Provisioning rule (this is untested and just a quick example):

import java.util.HashMap;
import java.util.Map;
import connector.common.Util;
import sailpoint.connector.webservices.EndPoint;
import sailpoint.connector.webservices.WebServicesClient;
import sailpoint.object.Application;
import sailpoint.object.ProvisioningPlan;
import java.text.ParseException;
import java.text.SimpleDateFormat;
import java.util.Date;
import java.util.TimeZone;

log.info("[RULE] Running Rule...");

Map body = requestEndPoint.getBody();
String jsonBody = (String) body.get("jsonBody");

Map jsonMap = JsonUtil.toMap(jsonBody);
if (jsonMap != null) {
    TimeZone centralTimeZone = TimeZone.getTimeZone("America/Chicago");
    SimpleDateFormat dateFormat = new SimpleDateFormat("MM-dd-yyyy");
    dateFormat.setTimeZone(centralTimeZone);
    Date startDate = new Date();
    String startDateString = dateFormat.format(startDate);

    Calendar cal = Calendar.getInstance();  
    cal.setTime(dateFormat.parse(startDateString));  
    cal.add(Calendar.DAY_OF_MONTH, 1); 
    String endDateString = dateFormat.format(cal.getTime());

    jsonMap.put("startDate", startDateString);
    jsonMap.put("endDate", endDateString);
}

String finalBody = JsonUtil.toJson(jsonMap);
body.put("jsonBody", finalBody);
requestEndPoint.setBody(body);


log.info("[RULE] Finished Running Rule.");
return requestEndPoint;

[ssaptashwa (Sumit Saptashwa)]

Thanks @bcariaga . This helped. I was able to get the current date and set it URL query parameter.