Forced encryption on attachments

Kim Sullivan
Tera Guru
 

Since upgrade to Utah, all our attachments are being encrypted.  In Tokyo and before there was a checkbox here to choose to encrypt.  That is now gone and none is not the default option.

ServiceNow support says this is OOB, but I can't believe this was intended. 

2023-07-20_8-49-50.png

#encryption

#crypto

#attachments

1 ACCEPTED SOLUTION

Kim Sullivan
Tera Guru

HI told me to post on community and this was an OOB setting.  I spent another 3 hours on it and figured this out -- 

update the optional_attachment_encrypt UI macro.

OOB config:

OOB.png

 

Updated: 

Updated.png

 

You also need to comment out these lines:

KimSullivan_0-1690491092953.png

 

View solution in original post

24 REPLIES 24

Hi Sadrudeen, how did you disable the table & type from " Encrypted Field Configurations" table. I tried opening this table & I am getting a blank page no Table or type option.

 

Also, do we need to modify the macro also after disabling Incident & RITM from this EFC table?

1. Elevate your Role
2. Set Value 'false' for the system property - com.glide.encryption.enable_attachment_key_ui
3. Go to "sys_platform_encryption_configuration" table and add an entry for the attributes Table and Type.

this should work. 

ServiceNow released a KB on this although the code isn't accurate (they left the choiceValue variable in the fixed code populated with the jvar_current_encryption_model):

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1560873 

 

But I do have a question...why do we need to comment out lines 34-36?  It seems to work fine without that commented out.


Please mark this response as correct and/or helpful if it assisted you with your question.
Steven

In my instance, a default encryption is being applied for all my users.  I needed to comment out those lines, so that wouldn't happen.


If it works for you without... great!

Ahh gotcha!  Thanks for the very quick reply.  Apologize about my first post as that came off as rude...I was frustrated with ServiceNow's own KB having the code wrong (see my previous post as I've updated it).


Please mark this response as correct and/or helpful if it assisted you with your question.
Steven