glide.crypto.core.config.cache
ServiceNow property description:
Contains a cache (revalidated daily) containing the state of each platform crypto component w.r.t. cryptography. A value of true indicates that the component is routed through the internal unified cryptography backend, while a value of false indicates that the component is using the legacy direct connection transport. Instances are gradually onboarded into the new backend.
Attributes
- Sys ID: 85941101c3232210fc6e5fedd401316b
- Type: string
- Application: Global
- Default value: {"config":{"REGION":"aus-ord-pdi"},"features":{"KMF_KEY_WRAPPING":true,"KMF_CERT_GENERATION":true,"KMF_CERT_LOOKUP":true,"KMF_KEY_GENERATION":true,"KMF_SELF_CONFIGURATION":true,"CLOUD_ENCRYPTION":true,"KMF_STORAGE_ENCRYPTION":true},"dbUrl":"jdbc:mysql://db160027.ord191.service-now.com:3308/","instanceId":"e6d136fd1bf1f1d09377eb9b2d4bcbf1"}
AI generated property description:
The ServiceNow property glide.crypto.core.config.cache stores a cached configuration that reflects the cryptographic state of the platform’s components. This cache is revalidated daily and indicates whether each component is routed through the unified cryptography backend (true) or still using legacy direct transport (false). Its default content includes metadata such as region, instance ID, database URL, and enabled cryptographic features like key wrapping, certificate generation, and storage encryption. Administrators typically do not modify this property manually, as it is managed by ServiceNow during gradual onboarding of instances into the unified backend. Altering or misconfiguring it could disrupt cryptographic operations, so it primarily serves as a system-level status reference rather than a tunable setting.
Source