---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Sign the Existing Messages

# Sign the existing REST and SOAP messages {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Sign and validate the existing REST and SOAP messages by enabling the Code Signing in
protected and trusted instances.

## Vorbereitungen

Role required: sn_kmf.cryptographic_manager

## Prozedur

1. In the trusted instance, configure the KMF signing job to sign the UI actions.
   1. Navigate to KMF Signature Configuration.
   2. On the form, fill these values.  
      {#rest-soap-code-sign__table_ckd_nl4_spb__entry__2}

      | Field | Description |
      |-|-|
      | Table Name | Glide table name. For example, select UI Actions \[sys_ui_action\]. |
      | KMF Signature Purpose | Purpose of signing the records. Select ECC Queue. |
      | Signature Generation Fields | Fields in the data source that you want to sign. If any changes are made to the values in one or more of these fields, the previously generated signature becomes invalid. Select Name and Script. |
      | Signature Generation Filter | Filter criteria that must be met to sign the records. |
      | Sign Attachment | Option to sign the attachment in the glide record. |
      | Instance Key | Option to use the instance key. |
      [Tabelle : 1. KMF Signature Configuration form]

      {#rest-soap-code-sign__table_ckd_nl4_spb}
   3. Right-click the form header and click Save.
   {#rest-soap-code-sign__substeps_erq_dm4_spb}
2. In the trusted instance, sign the required records.
   1. Navigate to System SecuritySecurity JobsAll.
   2. Click New.
   3. On the form, fill these values.  
      {#rest-soap-code-sign__table_jpp_cwp_spb__entry__2}

      | Field | Description |
      |-|-|
      | Name | Name to identify the record. |
      | Type | Type of the encryption job. Select Mass Sign Records. |
      | Table | Table from which the records should be signed. Select UI Action. |
      [ ]

      {#rest-soap-code-sign__table_jpp_cwp_spb}
   4. Click Export Code Signing job to production.  
      Two locally signed update sets are created.
      * One update set for the UI action configuration.
      * Another update set from the encryption job to export the code signing job.
      {#rest-soap-code-sign__ul_pqr_cxp_spb}
   {#rest-soap-code-sign__substeps_t1j_5vp_spb}
3. In the trusted instance, export the local update set to an XML file.
   1. Navigate to System Update SetsLocal Update Sets.
   2. Open the update set you had created for mass signing the records.
   3. Click the Export to XML related link and save the XML file.
   {#rest-soap-code-sign__substeps_ecc_ycv_5pb}
4. In the protected instance, import the update sets.
   1. Navigate to System Update SetsRetrieved Update Sets.
   2. Click the Import Update Set from XML related link to import the update set that is exported from the trusted instance.  
      For more information, see Import and commit the quick-start update set.  
      The update set is committed successfully.
   {#rest-soap-code-sign__substeps_mvy_3xp_spb}
5. In the protected instance, run the encryption job you had earlier created in the trusted instance by selecting Start.  
   A confirmation message is displayed mentioning that the records are signed.