Database Management

DPA REST API password rotation fails after upgrade (HTTP 500 with refresh token)

DPA REST API password rotation fails with HTTP 500 after upgrade when using refresh tokens.

First published date

3/25/2026 5:33 PM

Last published date

7/29/2026 4:40 PM

Overview

After upgrading DPA to 2025.2, existing automation that rotates the DPA SQL monitoring service account password via the DPA REST API stops working.

Product section

Database Performance Analyzer

Cause

This has been identified as a known issue in the DPA REST API handling of tokens when the refresh token is generated for an LDAP-authenticated user, leading to the server-side exception Cannot set this token to trusted and resulting HTTP 500.

Resolution

Workarounds / Mitigation

Option 1 – Use DPA local (non-LDAP) user for refresh token
- Generate refresh and access tokens using a DPA local user instead of an LDAP user, then update scripts accordingly.
Option 2 – Manual operations until the fix is applied
- Temporarily perform password rotation and/or annotation operations manually in DPA UI or via alternative methods while waiting for a fix.

Permanent fix:

Upgrade DPA to 2025.4 or any later supported version following the standard DPA upgrade procedure documented in the product guides and release notes.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.