For the complete documentation index, see llms.txt. This page is also available as Markdown.

ServiceNow Credential Resolver 1.0.0

Released on July 20, 2026

The Keeper External Credential Resolver for the ServiceNow MID Server reaches 1.0.0 with Yokohama-and-newer support and the ability to coexist with other vendors' resolvers.

Improvements

KSM-1093: New FQCN resolver class com.keepersecurity.secretsManager.CredentialResolver for Yokohama (Patch 7+) and newer lets the Keeper JAR coexist with other vendors' resolvers (CyberArk, HashiCorp, Delinea) on the same MID Server. Two JAR variants ship per release:

  • fqcn: Yokohama Patch 7+, Zurich, Australia. If FQCN does not work on Yokohama 1.0.0, use v0.1.0 as a fallback.

  • legacy: Utah, Vancouver, Washington DC, Xanadu (shared com.snc.discovery.CredentialResolver class)

  • KSM-610, KSM-1093: Added Yokohama (Patch 7+), Zurich, and Australia MID Server support; dropped end-of-life Rome, San Diego, and Tokyo.

  • KSM-1093: Fixed the resolver failing with Serializer for subclass 'pamSettings' is not found when PAM records are shared to the same Secrets Manager application. The bundled KSM SDK is now pinned to 17.3.0 and skips records it cannot parse instead of failing the whole fetch.

  • KSM-1104: Credential field improvements:

    • Actionable diagnostics in agent.log: warns on likely mid_-prefix typos and on unprefixed labels that match a recognized field name

    • pamUser records now resolve username and password from the standard Login/Password fields

    • config() logs an actionable error instead of a NullPointerException when ksm_config is not set

Resources

Last updated