Hi, is there a way to aggregate data from sources in a publisher-subscriber (queue-based) model from connected sources, such that whenever there are updates to a user’s accounts, they are asynchronously pulled in by IDN? I’m working on an integration where I need to aggregate a risk score from a connected web service app that I would want to get near real-time. Right now I have a scheduled aggregation that runs, but I wanted to explore ways to do this asynchronously and only for the users that have an update.
Depending on the Source, to trigger aggregation of the entire source, you can call:
GET
https://{{tenant}}.api.identitynow.com/cc/api/source/loadAccounts/{{source-cloud-id}}
There also appears to be a reload API that is used by the Actions on a user’s Accounts tab if the source is capable.
POST
https://{{tenant}}.api.identitynow.com/cc/api/account/reload/{{account-id}}
Both of these are /cc so there may be replaced by the end of the year.
@ethompson Thanks, but this is still just the usual single account or a full aggregation (delta or otherwise). This is initiated from the IdentityNow side, so the updates will be pulled in when IdentityNow initiates it. What I’m referring to is an asynchronous update, like a queue based model where target systems write to a queue if there are updates to one or more user accounts, and those just get pulled in when needed by IdentityNow when it polls the queue. The initiation here happens from the target system.
I’m just not entirely sure if this is possible at the moment on IdentityNow for all sources, so wanted to check. There’s something very similar the Oracle HCM Atom Feed does, and I’m guessing this might be something the direct connector might be able to do (not sure). It would be interesting to see if this is possible for other sources as well.
You can make your authoritative source on the IdentityNow side to be a CSV source and use the /v3/accounts API endpoint to have your source push creates/updates.
That’s what we do for our authoritative source for personnel data. We have personnel data that comes from both SAP SuccessFactors and FieldGlass (for non-employees) and some middleware (Mulesoft) that combines the two source feeds into one “output” that sends to our CSV source.
Make sense?
2 Likes
@mcheek That’s interesting!
Correct me if I’m wrong: You’re saying that the middleware (Mulesoft) is configured to run V3 Account APIs to update the info on IDN asynchronously. You do not have to rely on scheduled aggregation for your source (say through the file upload utility) to get updates. Is that right?
Also I have another unrelated question on V3 Account APIs here. Let me know if you have some background on that thread.
Correct, but I think we might be actually using the v2/accounts API method. I’ll have to check. It’s notable because an account ID doesn’t appear to be required to use the PUT method for accounts in v2, but it is for v3
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.