When encryption context was changed for a attachment using SysAttachment.changeEncryptionContext API, system corrupts the attachment, when user doesn't have access to encryption context (to which it is being changed to).

Steps to Reproduce

* create 2 encryption contexts: EC1 and EC2
* create an admin user with role that grants access to EC1, but don't grant access to EC2
* add an encrypted attachment to an existing incident -> use EC1
* run script to use changeEncryptionContext API to attempt to change the encryption context to EC2
* after running the script, download the attachment and see that is corrupt


This issue is under investigation. You can Subscribe to this known error article to receive notifications when more information will become available.


Related Problem: PRB1252502

Seen In

There is no data to report.

Intended Fix Version


Fixed In

London Patch 5

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-11-20 16:39:09