Replaced by
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.
2 Likes
Agree with @angelo_mekenkamp.
We are also awaiting a new endpoint for this API as well as the updateCorrelationConfig API.
1 Like
@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.
@colin_mckibben Can we anticipate the endpoint to be available by March 31st?
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.
Hi @colin_mckibben , I don’t understand why there’s no actual endpoint to update correlation config…
When inspecting through the browser as to what is being called, it’s going to a /diana/sources/sources/:id/updateCorrelationConfig endpoint, with a perfectly human readable/interpretable payload.
Can you indicate if this will be coming any time?
It’s a bit strange there’s no API for this crucial part of a source…
We need to onboard over 1000 applications in bulk and we can set everything via API except the correlation config.
To me it seems like the API is already there, but only used internally through the UI?
I think there’s a quick gain by just making this public as-is.
4 Likes
At this time it is a matter of prioritization with making public endpoints for the other deprecated endpoints that have a bigger impact on customers. However, I have forwarded your use case to the product team for consideration.
1 Like
+1 for making this a higher priority.
3 Likes
Hi @colin_mckibben , request to prioritize this API end point . It is much needed . With this , we can automate source creations , which satisfies all its functionalities .
Thank you !
+1 for raising priority.
This is the only missing API when bulk onboarding sources using scripts.
Hi Sharvari! 
I believe it is not the only missing API (although it is the most crucial). There is also no API available to schedule automatic account/entitlement aggregation right?
You’re right, it’s just for our requirements …this was the only one pending to get a new endpoint 
No API for scheduling aggregations yet. We are running it using scheduled script.
A beta API for updating the correlation config has just been released. Please see the first post for the link.
2 Likes
That is really great news, thank you for this!
I can’t wait to try out this new API 
1 Like
The new API is working! 
Some remarks below. They are insignificant to the fact that we now have this API available, but for completeness sake I have nevertheless added them below.
- This API is only for account correlation, not for manager correlation. This is completely fine as the two are quite different subjects and for the most sources, there is no need for manager correlation. However the API end point is
/correlation-config, and not/account-correlation-config, which is slightly ambiguous and inconsistent. Perhaps this can be changed as the type in the source json is alsoACCOUNT_CORRELATION_CONFIG. And maybe in the future it makes sense to also have an API like/manager-correlation-config - The name of the account correlation can not be changed, which is fine as it is completely tied to the source. However, if we rename the source, the account correlation logic name will not be updated, even after we update the account correlation logic. Therefore the account correlation configuration name can be confusing.
- It is good to know that you can assign the same account correlation configuration object to multiple sources by updating the source JSON. We don’t do this as it gives unexpected behaviors in the UI. We prefer to copy the object if multiple sources use the same correlation.
Kind regards,
Angelo
2 Likes
Thanks, this is good news.
Perfect!
Just for my information with the new API versioning strategy, will it not come in the v2024 API release with an Experimental tag?