Edge Encryption Rules

[AnirudhKumar]

Hello folks,

Background:

We have enabled Edge Encryption in our instance.

In the Encryption Configuration we have created some records. (for simplicity, consider one Encryption Configuration for short description field on a custom table)

We are trying to create records in the custom table through a Scripted REST API.

Issue:

We observe that ServiceNow prevents the record creation because it sees a non-encrypted value being set in an encrypted field.

What we found so far:

On debugging we came across 2 great resources on Encryption Rules.

- https://docs.servicenow.com/bundle/utah-platform-security/page/administer/edge-encryption/concept/...

- https://docs.servicenow.com/bundle/utah-platform-security/page/administer/edge-encryption/concept/...

In the page, we found the below script which we think may solve our trouble:

function SampleAction1() { 
    request.postParams.text.valueFor('incident', 'description');
}

Question: Our custom encryption rules don't seem to do anything (testing with gs.info).

All OOB encryption rules are present in a scope called ServiceNow Edge Encryption which is a private scope.

Any ideas??

[emaasalmi · Accepted solution]

Hi,

check this for logging Encryption rules. gs is not available, and your logs are printed to the wrapper log.

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

[rant]

I've been working with a customer with Edge for a few years now, and we've had loads of issues with it lately. Beware using the Configurable workspace with Edge. Initially we couldn't even get the values in clear text in list views in Configurable workspace. Took months to get a workaround to just display the values correctly, which is as basic use case as there should be. Then we noticed that you can't filter/sort Edge encrypted values in Configurable workspace even when they are encrypted using order preserving encryption. Got a response from ServiceNow that this will not be fixed. All theses work just fine in the "old default UI".

Now the latest problem after upgrading to Utah is that we are unable to update variables with the OOB widgets through the portal. Waiting eagerly so that I can once again explain to HI support what Edge encryption is, as they don't tend to even know what it its.

Edge is fine when it works, but when it doesn't, you're in trouble. Good luck 🙂

[/rant]