Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Encryption text fields are not supported by inbound actions - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Encryption text fields are not supported by inbound actions
KB0647661

Encryption text fields are not supported by inbound actions


1682 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Encryption text fields are not supported by email inbound actions 

Problem
Encryption is a process that scrambles information into a format that unauthorized parties cannot decode or use. Encryption text fields enable yoiu to encrypt the data stored on the field. It is available only for users with the role associated to the Encryption context.

Encryped text is not supported by inbound actions

Symptoms
If email inbound actions are set to populate the encrypted text fields, the following symptoms occur:
  • The data could be store in clear text in the encrypted text field but it is not visible on the form.
  • The data could be stored on the fields with the encryption context but null as the encrypted value.
  • System logs could show "Input length must be multiple of 16 when decrypting with padded cipher: javax.crypto.IllegalBlockSizeException: Input length must be multiple of 16 "

  

Cause

Impersonation does not change the encryption contexts available to a user. Even while impersonating, you have only the encryption contexts available to you originally. Because inbound actions follow an implicit impersonation to the users associated to the sender of the email, the encryption context is not available for inbound actions for encryption or decryption.

Resolution

The use of encrypted fields is limited within the context of the associated role. It should not be used on email inbound actions because an implicit impersonation is involved. Consider using different integration methods (for example, REST messages) to populate the encrypted data where the impersonation is not required.

Warning: Impersonation does not change the encryption contexts available to a user. Even while impersonating, you have only the encryption contexts available to you originally.

 


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

Attachments

Attachments

  • 2017-10-30_1300-encryped.png

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.