Any idea why SailPoint decided to restrict .toXml() method. Already we can’t see much of the stuff in INow as opposed IIQ. This is just another hassle during the development to see the ProvisioningPlan and debug the issues.
Hi @ashishbhatia
If you are using the WebService connector you can try using webhook to debug the ProvisioningPlan
Hi @rajeshs, can you please provide me more details, I know we can use event triggers and add the URL of webhooks, but in this where exactly I need do the same?
SailPoint didn’t give any reasons behind prohibiting the usage of these statements. I can understand your situation, it would be easy to debug by printing all the objects using toXml method.
However, Instead of printing entire object, extract the data from plan. I use to fetch all the data from Plan, Account Request and Attribute Requests. I agree that it’s a bit more coding and not as flexible as in IIQ, but we need to adopt.
Hope this helps you.
Thanks
Krish
Hi @ashishbhatia ,
I believe SailPoint restricted .toXml() method to restrict/avoid XML based attacks like XXE. Since it’s a SaaS platform, security takes precedence over usability at times.
I am not 100% sure as it’s not mentioned in the IDN documentation but I believe it’s a security standard followed by most SaaS products these days.
All the best!