API Key Not Updating in ServiceNow Configuration Page – Still Shows Old Value
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2025 12:30 AM
Hi all,
I’m running into an issue where the API key value in ServiceNow is not updating correctly.
Here's what's happening:
I updated the API key in a system property or credential record.
However, on the configuration page, it still shows the old key (either masked or decoded depending on the field).
I’ve tried clearing the cache and even restarting the instance, but the configuration page continues to display the outdated key.
The new key is saved correctly in the record when I check directly via the table or script.
Has anyone experienced this before?
Is there a known caching mechanism or UI-specific behavior that causes the config page to retain the old value?
Would appreciate any insights or solutions to ensure the updated API key reflects properly across the UI and is used during integration calls.
Thanks!
- Labels:
-
Container Vulnerability Response