Prepare your instance for GlideEncrypter deprecation

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 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 Deprecated APIs
    3. In the Suites record, select Deprecated API: GlideEncrypter from the Checks related list.
      The Column Type Check displays. This record contains a description of the check, and information on and links regarding how to update the records found by the check.
    4. In the Column Type Check record, select Test Check to run the scan.
      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.
      In the Scan Result record, the Scan Findings list displays a list of records on your instance that are using the GlideEncrypter API.
    6. Select the Count field on the Scan Findings list to navigate to a record.
    7. Modify any scripts in the record that uses the GlideEncrypter API.
      For details on alternatives to GlideEncrypter, see Alternatives to deprecated GlideEncrypter APIs.
    8. After removing GlideEncrypter calls from your scripts, run the scan again to ensure that there are no remaining calls to the API.
      Completed scan with no errors, warnings, or findings

    What to do next

    Deprecate GlideEncrypter usage of 3DES for password2 fields