Agent Dropped Secret for Credentials in Agent
Applies to
NetApp Console Agent
Issue
After successfully updating credentials on an Agent, it began failing with “invalid client secret” errors. Attempts to update or re-enter credentials failed, with the following log output observed:
ERROR [WorkingEnvironment] ... [GeneralExceptionMapper:42] {"error": "invalid_client","error_description": ": Invalid client secret provided. Ensure the secret being sent in the request is the client secret value, not the client secret ID, for a secret added to app ''.Cause
The Agent lost its ability to store or retrieve the Azure client secret due to misconfiguration and insufficient system resources:
- The VM hosting the Agent had less CPU, RAM, and disk space than the current minimum requirements.
- An unsupported Docker or Podman version was in use.
These factors led to container failures and possible corruption or loss of the credential cache/database. As a result, the Agent could not persist or validate the client secret, resulting in persistent “invalid_client” errors.
Solution
Deploy a new Agent with supported configuration and re-discover your CVOs.
Partner Notes
partnerNotes_text
Additional Information
additionalInformation_text
Internal Notes
internalNotes_text