Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
This property allows the use of 3DES encryption for deprecated APIs, impacting how data is encrypted and decrypted within the system. |
| What area does it affect? |
Encryption and decryption APIs |
| What does the default mean? |
The default value is "false", which means this behavior is disabled by default. |
| When should you review it? |
Review this property when maintaining legacy systems or assessing encryption compatibility. |
Out of the box property record
Raw metadata from the property record.
| Property name |
glide.security.3des.encryption.allow |
| Sys ID |
4116901b5d58221022636b635df26deb |
| Type |
boolean |
| Application |
Global |
| Default value |
false |
| Description |
Allow to support 3DES based deprecated APIs for encryption, decryption |
| Updated |
2025-07-23 23:57:59 |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... 3DES is now banned for encryption in federal systems. Going forward, TDES can only be used for historical purposes, such as decrypting old messages, key unwrapping, and MAC verification. The glide.security.3des.encryption.allow system property controls whether 3DES encryption is enabled on your instance, however there are several steps which may need to be taken to verify that your instance is ready for ...
Related properties