E-PC/E-SEC: PeopleCode API RevalidatePassword Fails on Passwords with 31/32 Characters, When Called from Fluid Pages. Error "The Current Password does not match the the actual password." Is Displayed, even though the Password Is Correct.
(Doc ID 2620251.1)
Last updated on DECEMBER 16, 2019
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.56 and later
Information in this document applies to any platform.
PeopleCode API RevalidatePassword fails on Passwords with 31/32 characters, when called from Fluid pages.
It works fine if called from Classic/Classic Plus pages.
The issue can be reproduced at will with the following steps:
1. Create a Fluid Page that has a push button, which calls the RevalidatePassword API.
2. Create a User and set the password with 31 or 32 characters. For example: thisisatesttotroubleshootthefun
3. Execute the code in PIA for that user .
4. RevalidatePassword fails. Error message "The Current Password does not match the the actual password." is displayed, even though the password is correct.
In HCM, that can be also verified in the W2 Consent page (Employee Self-Service Homepage > Payroll Tile > W-2/W-2c > W-2/W-2c Consent).
1- Login and select the Employee Self-Service Homepage.
2- Select the Payroll Tile.
3- On the left panel navigation, select W-2/W-2c > W-2/W-2c Consent.
4- In the page, select the checkbox and click on the submit button.
5- The RevalidatePassword dialog opens up.
6- Enter the correct password with 31 or 32 characters.
7- Error is displayed, even though the password is correct.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document