We have an existing script rule that uses a settings.json file. We recently noticed that any attempt to edit (download/upload) the settings.json using the Web Policy Editor corrupts the file contents. Even just downloading the file, and immediately re-uploading it causes the issue, so we know it is not related to any text editor. Any ideas on what could be the root cause or where we could find a log, etc. within BeyondInsight that might give an idea of what is going wrong?
Question
settings.json Corrupted
I have seen similar issue with Zscaler corrupting things, would assume that it is plausible for other 3rd party security tools also.
simply just based on the content of your file json or policy xml file uploaded and downloaded to the PM Cloud.
Test on a machine without any 3rd party security tools and validate if you have the same issues, might even have to be off your company network.
This is on-premises version of BeyondInsight and Privilege Management. No Zscaler. I believe it is a bug as the file appears to be converted during upload/download from UTF-8 to UTF-16 LE
I hope that you have raised this with BT, I think a PGCaptureConfig from the client along with a copy of the policy exported from BI.
Then do test on a client that you have excluded from all the other different 3rd party security DLP, AV and others.
Hi
I believe it is a bug as the file appears to be converted during upload/download from UTF-8 to UTF-16 LE
this is a known issue that is being worked on. In the KB article KB0020516 it is mentioned as a note under the Create Script section. We will update the KB to include workarounds or fixes once the information is available.
Login to the community
No account yet? Create an account
Login with the BeyondTrust Identity Service
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.