Notifications

30 views

Issue

Symptoms

Failed to authenticate Edge Encryption proxy after upgrade to Madrid. The proxy is shown as "Online" but "Unauthenticated". When we click the Authenticate button, it goes to pending then back to Unauthenticated.

Release

After Madrid Upgrade

Cause

Pre-Jakarta proxy_version (on the table 'sys_encryption_proxy') was defined as decimal(20,2).
With Jakarta, the proxy_version is changed from decimal(20,2) to varchar(40).

Up until Madrid, there was no validation for the Proxy version in ServiceNow and "proxy_version" on the table 'sys_encryption_proxy' value was still in the format supported by decimal(20,2).
From Madrid, the proxy versions are being compared for Authenticating the Proxy and version value is not two digit decimal anymore.
This is preventing Proxy Authentication for all upgraded Madrid instances with Edge Encryption Plugin installed before Jakarta.

Resolution

  1. Click Execute Now Scheduled Job "Update sys_encryption_proxy.proxy_version type to string if decimal" to convert "proxy_version" to STRING 

    URL to the JOB: https://<instance_name>.service-now.com/nav_to.do?uri=sysauto_script.do?sys_id=7ad007c077232300d1ced0adda106159 

  2. Wait for the above job to complete and make sure that the "proxy_version" field is now string.

  3. Restart Edge Encryption Proxy and proxy is should now "authenticated" 

Article Information

Last Updated:2019-08-02 20:43:01
Published:2019-05-22