Upgrade the Delinea Credential Resolver

Delinea recommends always using the latest version of the Delinea Credential Resolver. After every install or upgrade, administrators must run the Setup Utility (CLI or UI) to ensure all parameters in config.xml are correctly generated. Skipping this step can result in parameter mismatches that prevent the resolver from functioning correctly.

Versions 5.0 and Above

Upgrading from a pre-5.2.0 version: If you upgrade the Credential Resolver JAR to v5.2.0 or later, you must regenerate oauth2_grant.json using the v5.2.0 Setup Utility (DelineaMidServerUIUtility-5.2.0.jar or DelineaMidServerCLIUtility-5.2.0.jar). Grant files generated by older utilities do not contain a refresh_token field, so the automatic token refresh will not work and you will see repeated Platform token expired. Cannot refresh. Please regenerate token manually messages in wrapper.log.

For credential resolver versions 5.0, 5.0.1, 5.2.0, and later, administrators must run one of the following Setup Utilities:

  • DelineaMidServerCLIUtility-5.2.0.jar (command-line interface)

  • DelineaMidServerUIUtility-5.2.0.jar (graphical interface)

Any Setup Utility version 5.0 or above is compatible with all resolver versions 5.0 and later.

Parameter Stability

Parameter names are unchanged from version 5.0 onward. Future releases may introduce new parameters, but existing parameter names remain the same. This means administrators do not need to reconfigure existing parameters when upgrading between 5.x versions, though running the Setup Utility is still required to pick up any new parameters.

Older Versions (4.5.1 Through 4.6.0)

Parameter names changed between versions 4.5.1 and 4.6.0. Administrators upgrading from these versions may encounter compatibility issues due to mismatched parameter names in config.xml.

To resolve these issues, administrators must run the Setup Utility version that corresponds to the target resolver version. This regenerates config.xml with the correct parameter names.

For details on the specific parameter changes introduced in version 5.0, see Decryption / Parameter Issue (Config Mismatch).