Hi Folks, we are integrating a rest api application which works something like this.
send body to end point A, on success it generates a unique id and returns that as response
use this id to make second call, (GET) which returns all the values for the user,
as part of the second call, the unique id is also retrived, i can see it in the raw response map and added it to the hash map which was return in the after operation rule of connector… but this attribute still doesn show up on user link in identity warehouse.
yes the attribute is there in Schema, funny thing is , if i run aggregation its brining in that attribute for existing users, but when i create new user (post and get call) it doesnt update on link then
Thanks for sharing the application.xml and after rule. After going through it quickly, few attributes which are not mentioned in the application schema the rule looks good.
Normally if the response of Create account contains the required attributes including the identity attribute, the account object would be created, and account link would be displayed under the identity.
Also check the resourceobject and the API response during the aggregation. Ideally, the account should be updated with Aggregation.
Just one bit of information not sure if it works, the After Operation rule returns updatedAccountOrGroupList which gets set to “connectorStateMap”, try using application.getAttributeValue(“attributeName”);
Hi jarin, so the issues it not with link not getting created. link is getting created well. just that one particular attribute is missing, i printed the updateInfoMap object as well… it does contain the id attribute. Not sure why link doesnt show it.
If i run the full aggregation, link is re updated with all the information. I cannot make it run everyday as the user base is around 400k users.
