Changing database user credentials
This request packet sets new password for the database user identified by ID 61.
<packet version="1.4.2.0">
<database>
<set-db-user>
<id>61</id>
<password>a1b2c3d</password>
</set-db-user>
</database>
</packet>
A positive response from the server can look as follows:
<packet version="1.4.2.0">
<database>
<set-db-user>
<result>
<status>ok</status>
<id>61</id>
</result>
</set-db-user>
</database>
</packet>
A negative response from the server can look as follows:
<packet version="1.4.2.0">
<database>
<set-db-user>
<result>
<status>error</status>
<errcode>1013</errcode>
<errtext>Database user does not exist</errtext>
</result>
</set-db-user>
</database>
</packet>
Changing credentials for multiple database users
This request packet sets new login names and passwords for the database users identified by ID=61 and ID=68.
<packet version="1.4.2.0">
<database>
<set-db-user>
<id>61</id>
<login>testUser</login>
<password>a1b2c3d</password>
</set-db-user>
<set-db-user>
<id>68</id>
<login>secondUser</login>
<password>abc2c3d</password>
</set-db-user>
</database>
</packet>
If the user with ID 61 was not found on server, and the user with ID 68 was successfully updated, the response packet looks as the follows:
<packet version="1.4.2.0">
<database>
<set-db-user>
<result>
<status>ok</status>
<id>61</id>
</result>
</set-db-user>
<set-db-user>
<result>
<status>ok</status>
<id>68</id>
</result>
</set-db-user>
</database>
</packet>