The IQService supports customization of the functions by allowing integrating before/after scripts implemented in languages like PowerShell and Batch. Scripts can be used to automate any required actions that cannot be automated using current source functionalities. Scripts called before processing the request are referred to as native before scripts and scripts called after processing the request are referred to as native after scripts.
Hello,
It seems the documentation is not up to date with the current requirements.
The examples illustrate deserializing the application environment variable, then directly accessing the password for the application. This is not currently valid, the passwords contain an HTML newline character in the middle of the base64 encoded string, and this gets expanded when deserialized. After joining the resulting value and base64 decoding it, one must still decrypt the password.
The last example that illustrates the Office365Username use cannot be run, it contains a syntax error in the second line where Add-Type is called with a path that contains a space.
Using the application credentials is a critically important requirement, this prevents storing the credentials on the IQService server and managing them there after.
Hi Joseph! Thank you for your input. We’ve created a Jira issue to track the effort and we’ll update the comment thread when it’s been addressed: CONDOCS-5361