UpdateUser

Updates user information.

A single record of the following fields is returned.

Method	string	The operation that requested this response.
TransactionID	decimal	The unique message ID for this message.
ErrorMessage	string	If blank, no error was returned.
ErrorLocation	string	If blank, no error was returned.

Hashing Algorithm

With release 6.2, K2 has adopted the SHA-256 hashing algorithm for secure authentications. Previously the standard was SHA-1. See the Changing Passwords Used by External Applications topic of System online help for a general introduction to this enhancement.

A newly created or reset password is hashed using SHA-256.
Legacy passwords that have not been reset continue to require SHA-1.
The HashingAlgorithm parameter in Authenticate defaults to SHA-1, if left blank.
The Sample API C# Application and Sample API ASP Page provide an option to switch the hashing algorithm between SHA1 and SHA-256.
VSA passwords can only be reset using the VSA application, not by the API.
Warning: Changing a password used by a legacy external application will disable the integration until either the external application is updated to use the required SHA-256 hashing algorithm or a new SHA-1 credential is created and implemented. Ensure passwords used by external applications are not changed before the update is implemented. See Creating a New SHA-1 Credential for a Legacy External Application below.

Best Practices

To ensure a smooth migration from prior releases to this release, Kaseya recommends web services API client code be written or modified to attempt authentication using SHA-256 first, then SHA-1 second, in succession. This will ensure that the client code will be compatible with passwords created under current and prior versions of the VSA.

Set the HashingAlgorithm parameter in the Authenticate request to SHA-256. Ensure the password is hashed using SHA-256. Issue the Authenticate request. Check to see if a valid session ID was returned.
- Authentication is successful if the SessionID parameter returns a non-zero value and the ErrorMessage parameter is blank.
- Authentication is not successful if the SessionID parameter returns a zero value. Perform step 2.
Set the HashingAlgorithm parameter to SHA-1. Rehash the password value using SHA-1. Re-issue the Authenticate request. Check to see if a valid session ID was returned.