Josh,

Someone more knowledgeable than me may respond, but to the best of my knowledge, no, Remedy doesn't allow you to setup password history rules.

yea....ensuring that it's not the same as current is pretty easy, you just compare it to current....but doing a history is a bit more complex, you must store each one used somewhere for the history to work...I don't know where they would store it as I've never seen a storage place

Hi,

the OOB check uses the following command to check the previous password:

$PROCESS$ Application-Confirm-Password $New Password$

Application-Confirm-Password password

Validates if the password is the password for the current user. For password, you can use a reference to the field that contains the password, such as field 102 or field 103. This command returns one of the following integers:

1-The password was confirmed.

0-The password is not valid.

If you used AR System version prior to 6.0 to create workflow involving a Password field (ID 102), the workflow might not function in AR System versions 6.0 and later. Version 6.0 included enhanced encryption and tighter security controls. To work around this issue, use the Application-Confirm-Password $PROCESS$ command.

As LJ mentions, should not be too hard to set-up a history and run this command to validate.

Cheers

Carl

Here's the documentation on the OOB password policies you can set up:

https://docs.bmc.com/docs/display/public/ars91/Enforcing+a+password+policy+introduction