A public replacement will not be available before March 31st. There may be a public replacement after March 31st, but no official timeline is available.
Hi @colin_mckibben,
To me, account correlation configuration and manager correlation configuration are just another set of configuration items to sources (just as configuring things like the name, description, account schema, provisioning policies, attribute sync settings and owner). The fact that you can’t call a single API to create/modify account correlation similarly to how we can call a single API to make any other source related change is the reason why it is not fully possible to manage sources through automation.
I do understand priorities have to be made for the March 31st deadline, but I do hope that a replacement for this API will be made available quickly after, considering that source management is one of the key points of IdentityNow.
1 Like
Agree with @angelo_mekenkamp.
We are also awaiting a new endpoint for this API as well as the updateCorrelationConfig API.
@sharvari @angelo_mekenkamp Are either of you using this endpoint today, or have used it in the past? We are unable to find any indication that this endpoint ever existed, which means I may have mistakenly posted this deprecation for a non-existent endpoint.
Even if it doesn’t exist, we recognize that the functionality is desirable, but we need to know if this is actually a real endpoint so we can support the deprecation first.
We are using the {{api-url}}/diana/sources/sources/{id}/updateCorrelationConfig API and looking for a replacement Or any other direct API call which can help with set or update of correlation configuration for source. (not in favor of using the sp-config api)
Hi @colin_mckibben, I don’t think I have used this API. I did find it in a postman collection of mine, but it could be I was looking for this endpoint (because we do need it) and tried several endpoints expecting such an endpoint to exists (due to lack of cc/api documentation, guessing was a way to find them).
Right now we also use the API @sharvari mentioned.
I believe this endpoint never actually existed, and I mistakenly made a deprecation notice for it. The ability to set a correlation config may be added in the future, but it is not a high priority at this time. Our engineers are focused on delivering public replacements for higher priority private APIs.