Password puzzle

ACDC

I am trying to work out a simple method on how to prevent a user from replacing their password with the same existing password - So if the new password is the same as the existing password report error - any ideas ?

pureist

Why not, OLD_VALUE(..) ?

ACDC

That seemed like a good idea but it does not work

If RegularUser.Password WAS CHANGED AND OLD_VALUE(RegularUser.Password)=RegularUser.Password
Then ...

I think Aware assumes it was not changed because its the same

pureist

what happens with just:
If RegularUser.Password = OLD_VALUE(RegularUser.Password)..
maybe the evaluation basis is different.
otherwise maybe need to use a dummy password Attribute which is updated with the new password when it is changed, then used in future comparisons.
BUT..
isn't there a rule 'uniqueness of LoginName' inbuilt which can be adapted?

ACDC

BUT..
isn't there a rule 'uniqueness of LoginName' inbuilt which can be adapted?

I have tried a couple of variations of this but to no avail

otherwise maybe need to use a dummy password Attribute which is updated with the new password when it is changed, then used in future comparisons.

cant't get this to work

If RegularUser.Password = OLD_VALUE(RegularUser.Password)..
maybe the evaluation basis is different.

This reports the error on every save of the RegularUser object.

The problem in all instances is I need to use WAS CHANGED to get it working and awareim assumes it was not changed because the same password was used, so the rule is ignored (unless I am blind to the obvious)

pureist

what about, WAS NOT CHANGED or equivalent?
that will work, but you'll have to structure so that the rule isn't evaluated if Cancel/Close is clicked to not proceed with change..
If Password WAS NOT CHANGED and PasswordChangedFlag = 'Yes' then display Error
'PasswordChangedFlag' attribute is set to Yes when the OK button is clicked.

also, I don't think Aware actually updates an attribute value if the new value is the same as existing.
thus, some kind of 'dirty' flag isn't set for the attribute, and therefore WAS CHANGED isn't satisfied.

BobK

1) I assume your users are updating the RegularUser BO directly. Try using a temp BO for the new password. Compare that with the RegularUser password. If they are the same: report an error, if different: copy password from temp Bo to RegularUser BO

2) Since the RegularUser password is stored encrypted, unless you have another attribute that stores the clear text password, you will need to encrypt the temp BO password so that you are comparing encrypted with encrypted.