Good day all,
I was taking a closer look at the payload properties that gets displayed in the logs when the subscription is called and noticed that my encrypted values are getting displayed in plain text in the logs. Can anyone confirm if they are seeing that in their environment please?
Thanks
Steve
Or...j/k, I already had a subscription and scriptable task ready and waiting. So, yes, I confirm your observation.
Output in the log for a scriptable task that writes out all properties:
Chip.EncryptedProp01: VMware1!
Not good.
What version?
7.3
Can you give me something specific to test? I'll check it out on my end.
Thank you that would be great. Create a encrypted property for a VM that will trigger a subscription. When the subscription runs the scriptable task that receives the payload will log all the values as well as the looping and logging all the virtual machine properties. I am looking to see if you see the same results that I am in that the encrypted property you configured gets presented in the System.log as plain text.
Thanks for taking the time
Ok, I'll whip up a test and get back to you. May be tomorrow morning, though.
No worries!! Thank again for your time
Or...j/k, I already had a subscription and scriptable task ready and waiting. So, yes, I confirm your observation.
Output in the log for a scriptable task that writes out all properties:
Chip.EncryptedProp01: VMware1!
Not good.
OK thank you for the confirmation on this. I am going to see if I can get some attention to this issue. Thanks again for you help
vRO does this too, if you run a System.log on a SecureString type it will put it in clear text in the log. To me it's obfuscated and not actually encrypted.
Secure string is just like a password field, nothing to do with encrypting the string. just making it less readable over shoulders etc.
I faced the same issue. I was thinking about encrypting the value with vRO and push it back by EBS with virtualMachineAddOrUpdateProperties
Any other suggestions?