Prepare your instance for GlideEncrypter deprecation

  • Release version: Australia
  • Updated March 12, 2026
  • 1 minute to read

    • Use an instance scan script to find and remove GlideEncrypter API calls on your instance. Removing these calls is a necessary step in deprecating 3DES encryption on your instance.

    Before you begin

    Role required: admin

    The GlideEncrypter API is planned for deprecation as of the Zurich release of ServiceNow. Removing GlideEncrypter calls from your script is also a necessary step before deprecating 3DES encryption on your instance.

    Procedure

    1. Navigate to All > Instance Scan > Suites.
    2. In the Suites list, select GlideEncrypter to identify the records with GlideEncrypter usages.
    3. In the Suites record, select Execute Suite Scan.
    4. In the Scan Suites Now window, select Full Instance, then select Execute Scan.
      The suite scan executes. During the scan execution a Execute Test Scan, a window displays the progress of the scan.Scan progress window
      Note:
      This scan checks only records that have been created or modified by the customer.
    5. When the scan is complete, select Go to Result to view the Scan Result record.
      Completed scan with one finding
    6. In the Scan Result record, select the Count field on the Scan Findings list to navigate to a record.
      Completed scan
    7. Modify any scripts in the record that uses the GlideEncrypter API.
      For details on alternatives to GlideEncrypter, see Alternatives to deprecated GlideEncrypter APIs.
      Note:
      You do not need to modify base system (out-of-box) records if you have not made any changes to them. These records are handled by ServiceNow.
    8. After removing GlideEncrypter calls from your scripts, run the scan again to ensure that there are no remaining calls to the API.

    What to do next

    Deprecate GlideEncrypter usage of 3DES for password2 fields