Hey Team!
I am trying to set up a Web Service Connector that only uses internal ISC API’s. I am getting the following error:
Not sure why I’m getting this, however, is it possible that I am required to use a Web Services SaaS connector instead? Saas works, however, getting other errors there and I would like to use connector rules…
Hi @Swegmann
I have configured this using web service connector and it worked fine for me. Can you please check the authentication part if that is configured properly.
Also worth to see if the API call is getting triggered in VA logs.
Thank You.
Regards
Vikas.
Hi Vikas,
I’m not seeing anything else but the error in the VA, could you perhaps share your connection settings?
Seems the source itself was just corrupted… Recreated the source and now it works!
Now I’m getting a different error when Aggregating Accounts…
Just using the regular v3/accounts API
Mapped it exactly the same as my Saas source (that is working).
Hi @Swegmann
Looks to me like there is a field in your identity profile which is being treated as boolean. May be coming in the v3/accounts response like “true” but is being stored in account schema as Integer.
Can you please try first with few attribute mapping to see if that helps.
Thank You.
Regards
vikas.
Yea that was my first thought, but now only trying with 1 attribute mapped that is a string in the source and in the account schema. Still getting the same error…
The strange thing is that I have the exact same setup in my Web Services SaaS connector and it works there perfectly.
May be try to run un-optimized aggregation ? Just a thought not sure if that will solve the issue.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
