- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2023 08:23 AM - edited 07-27-2023 08:23 AM
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.
#encryption
#crypto
#attachments
Solved! Go to Solution.
- 7,870 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2023 12:15 PM - edited 07-27-2023 01:51 PM
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:
Updated:
You also need to comment out these lines:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2025 10:05 AM
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2025 10:30 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2023 08:22 AM - edited 11-17-2023 08:29 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2023 08:25 AM
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2023 08:31 AM
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