Viewing Requests in Audit

Navigate to Secrets > Audit > Application Request to review password retrieval requests. The response message and HTTP status code identify whether the request succeeded or why it was rejected.

Figure – Application Request audit records

Troubleshooting Application Token Requests

Client IP Does Not Match with Application IP

This response indicates that the request source IP is not included in the Application Network Address Range of the AAPM Application Token. Add the application server IP address or the applicable subnet to the token configuration, then retry the request.

Figure – Client IP does not match with application IP on the AAPM account

Token Cannot Be Empty

This response indicates that the token query parameter was not supplied. Include the Application Token value in the request and send the request again.

Figure – Token cannot be empty response

Application Token Is Not Valid

This response indicates that no AAPM Application Token was found for the supplied value. Verify that the token was copied correctly and that it is the token defined for the intended application.

Figure – AAPM Account not found by token response

Requested Vault Account Is Not Bound to the Token

This response indicates that the selected Vault Account is not included in the AAPM Application Token definition. Bind the intended Vault Account or Account Group to the token, then resend the request.

Figure – Requested Vault Account is not included in the AAPM Application Token

Vault Account Does Not Exist for the Specified Path and Name

This response indicates that the sapmAccountPath and sapmAccountName values do not identify an existing Vault Account. Verify both values against the Vault Account definition, including the exact path and account name.

Figure – Vault Account path and name validation response