The PW is encrypted by the server when the record is saved....have you tried, and it failed, to simply push a known value to the password field for the particular users and got an error?
Yes, I have updated the password field via the API and the account was not able to login. I need to encrypt the password first, so I need to know what encryption is needed of if BMC allows the password to be updated via the API.
what are the versions of the API and Server you are working with? I ask because if your versions are mis-matched, it can cause that problem. Remedy 9.x changed the encryption algorithm used, so previous versions of the API might not properly update the password, but as I understand it, you should be able to do it through the API
versions are the same, we are on 18.05.
I believe it should work and I've tested it using driver against a 9.1 server. What is the API call that you are using? I did a SetEntry against the User form and set fieldid 102 to the character value "remedy" and was then able to login using that password for the appadmin (record with request ID 6) user.
Number of Items in EntryId ? (1): 1
Entry Id: 000000000000006
Field/value pairs to set:
Number of field/value pairs (0): 1
Field id: 102
coords/view/display (0-14, 30-34, 40-43) (0): 4
Char Value (): remedy
Time of Get operation (0):
SetEntry option ? (0):
Status List : 0 items
I am trying the C API and using UpdateAsync(). what API are you using that worked?
We've got some crossed wires here :-)
What product are you using and where do the passwords you are trying to set reside? The example I gave is for using the Remedy AR System API to reset the password of a user that is stored as a record in a Remedy server.