we are unable to disable the crypto module from the service now instance

[Ashokbabul]

Hi Folks,

We have upgraded to Vancouver, and as a result, the crypto module has appeared in the development instance but not in the production and test environments.

After carefully reviewing all the community posts related to disabling the properties controlling the crypto module visibility in the instance, we attempted to change the value of the properties "com.glide.kmf.global" and "glide_encryption.cle_replatforming_with_kmf sys_prop" to empty, as they are currently set to opt_in.

However, when attempting to change the value of the above properties to empty, an error message appeared stating that changing the value to empty is not safe. We also tried to do this using a background script and setting system auto fields to false, but the output still indicated that changing the value is unsafe.

We kindly, request your advice on how to disable the crypto module in the service now instance.

Thanks & Regards,

Ashok Babu

[Robert Bracken]

Hello, 

were you able to find an answer or resolution to this? 

[Ashokbabul]

Hi Robert ,

No we have not found the solution yet.