Locking a user's password value

[Former Member]

Under 46C, I just made the value in BCDA1 a date way in the further, and this preclued the expiration of the password. Since upgrade to 6.0....doesn't seem to work. Or, should I say, id's created prior to 6.0 seem to work, but if created after 6.0 upgrade, don't.

Most all users do have, and should have their passwords expire at what is defined within the instance. But I have a need to lock in password for certain users, mainly scanners etc, so the password will not expire. How can I do that with 6.0?

[Former Member]

Hi Jerry,

since 6.20 you need the following fields:

pwdchgdate & bcda1

=> Just update pwdchgdate as well and it will work what you prefer )

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

It appears all the old id’s created in 46C that we had the values locked, have blank (zeros) in pwdchgdate and also in passcode.

Normal pwdchgdate values appears to be the last date changed.

So to lock in a password, is this value to be zero…or some date in the future? A little testing seems to indicate, both values do lock it in, but not sure why.

If I altered passcode to zeros, this nukes the password, even though the 46C created ones, seem to survive with that value.

[former_member235924]

Hi,

depending on the requirements, you can use a service system user for example.

Choose the F1-Help in the field for the user type in SU01 and see which one is the best for your purposes. For these users the password will not expire and the user doesn't have to change the password at first logon.

Ingrid