Article ID: 121539, created on May 10, 2014, last review on May 10, 2014

  • Applies to:
  • Business Automation 5.4

Symptoms

UserAdd_API request fails with the error:

<?xml version="1.0"?>
<methodResponse><fault>
<value><struct><member><name>faultCode</name><value><i4>-1</i4></value></member><member><name>faultString</name><value><string>SW5zZWN1cmUgYXJndW1lbnQgcGFzc2VkCgo=</string></value></member></struct></value>
</fault></methodResponse>

Cause

User password is specified in insecure form

Resolution

If API request returns an error, the error message is contained in the fault string; which is Base64 encoded. To decode it, please use some external sites like Base64 Decode.

SW5zZWN1cmUgYXJndW1lbnQgcGFzc2VkCgo= means "Insecure argument passed".

It is caused by the fact that user's password is specified without XXX prefix. Please refer to our documentation - UserAdd_API:

Important: Sensitive data is passed to the method. To avoid logging of sensitive data, the Password argument must be escaped as this described in the section Important: Avoid Sensitive Data Logging. Avoiding sensitive data is obligatory, otherwise request will fail.
...
To avoid logging of sensitive data during API calls to PBA, the "XXX" prefix should be added to the relevant arguments.

So it is necessary to add XXX in front of the password value and send API request again.

Search Words

Error creating User for Account using UserAdd_API

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 210d017ddc3a076d22f0f865b1cf0730 92711db0799e8aefe8e51f12dace0496 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF