Password Comparison Is Not Returning True If Encrypted Password Matches With Clear Text Password (Doc ID 3061089.1)

Last updated on DECEMBER 02, 2024

Applies to:

Symptoms

In BRM version 12, when one is resetting password for Customer Center user, it is allowed to set the same password as existing without throwing an exception.
Earlier in BRM 7.5, it used to error out as previous (encrypted) password was same as new (clear text) password.

Current encryption method - OZT.

STEPS:

Below flist is being created as part of password comparison opcode execution:

# number of field entries allocated 20, used 3
0 PIN_FLD_POID POID [0] 0.0.0.1 /service/admin_client 12345678910111 11
0 PIN_FLD_PASSWD_CLEAR STR [0] "XXXX"
0 PIN_FLD_PASSWD STR [0] "XXXX"

For all the records, it is returning BOOLEAN FALSE i.e. encrypted password (PIN_FLD_PASSWD) does not match with clear text password (PIN_FLD_PASSWD_CLEAR).

There is also some customization on customer side. 

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.