Hello,
We use SECKFMChangePassword to change user password. However, if we put a new password that is already been used, we recieve an error message (password in history, or something like that). Do you know how can programmatically (not using server’s policy configuration etc) remove this history checking ?
TIA,
Anton.
Subject: Password history
There’s no capi-way to achieve this.
Lowlevel functions to achieve this have not been documented or exported.
You have to set it to a specific password, so just adding (1, or 2, 3) is no acceptable workaround?
Since history-entries are limited you could just at the beginning put e.g. if max-history-entries=32 32 dummy passwords, after that your needed password should be accepted. sounds a bit odd, but…
Markus Seitz