Hi Jodi,

There may be several reasons for the failure:

  1. QG does not pick up this new authentication record for your scan or, ip/username/password is not correctly set;

  2. Scanner may not have access to the Safe. For example, scanner is not in safe's authorized area;

  3. Your Vault account may not be the owner of the safe where password file resides; you have to manually add the safe to the account after you create it;

  4. You may not uncheck the “User Must Change Password at Next Logon” check box, when you first create the account;

  5. Your Vault account may not have “Retrieve files from safe” privilege for the particular safe, you have to manually grant the privilege to the new created account.

If you can, please check your scan result. In information gathered section, you should see “Unix|Windows Authentication Failed” entry, in case you were scanning windows or unix targets. The error message can help us narrow the problem down. The message looks like:

Error Message: Vault:,*.*.*.* Port:****, Safe:***, Error:Errorwhileloggingonwithlogonfile./.cyberark-auth-23731-23930.ini(Code:9, Error:ITATS203EPasswordhasexpired.)Authentication RecordCyber-Ark

For the password truncation issue, I didn’t see it in my scan. My Vault account has 10 characters password and I can use it to have a successful authentication scan.

Thanks