Issues Related Password Fetch Request by Applications

1 min

Errors related to the Application Token (AAPM) and their possible solutions are provided in the table below.

Issue - Error Code	Possible Solutions
AAPM Account not found by token: XXX	The AAPM Token used when sending a request must be verified. The relationship between the AAPM Token and the Password Vault account must be verified via the Kron PAM interface.
SAPM account doesn't exist with sapmAccountPath = XXX and sapmAccountName = XXX	The Password Vault Account Name and Path Name sent in the request must be verified.
There are multiple SAPM Accounts / SAPM Groups related to this token, you should add SAPM Account Path and SAPM Account Name parameters to URL!	There are multiple Password Vault Accounts associated with the AAPM Token. Therefore, when sending a request, the Account Name and Path must be used together.
	Check AAPM Token that used to request the password.