6 replies to this topic

[sudhakar]

Hi,

I am adding a record (new operator id) in ‘logonf’ proisam file through an update function.
Eg – @COD = ‘DIV’
@OPRID = ‘SUD’
@LPWD1 = @OPRID
And rest of the fields through a standard user id record.

As @LPWD1 is an encrypted field, ProIV storing the value in this field as like – ÙUD
First character is encrypted.

When I try to Login to ProIV through above operator Id, SUD and password SUD, system denied with error message Invalid password.

But when I change password using $OPR, the password is not getting encrypted and able to login to system. I also get confirmed through report function on LOGONF file.

How ProIV is treating same file in two ways?

Any advices…?

Thanks in advance

Sudhakar

[Rob Donovan]

Hi,

It works fine on V5.5 doing what you said, for me....

What kernel version are you on?

Rob.

[Wim Soutendijk]

are you adding the record using the same file definition (LOGONF)?
I have seen problems when trying to add a record through an alternate file definition (LOGONF2) with encrypted fields.

[George Macken]

Hi

I too have had the same experience of "encryption" as Wim

You have to use the File Definition LOGONF to add/change the password on the operator, do not use an Alternate File definition.

see
http://www.proivrc.c...=1761&hl=logonf

Rgds


George

[Mike Schoen]

The filehdr record has an encryption key field, which contains the key for the encryption. If you do use an alternate filename, eg LOGONF2, you need to set this back to LOGONF for it to work.

[sudhakar]

Sounds like Wim and George are right.

When I use direct file instead of Alternate file, it is working Perfectly.

Thanks to all

Sudhakar