Errors Returned From The Server Are Not Displayed During The Change Of Password
(Doc ID 1073090.1)
Last updated on JULY 26, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
***Checked for relevance on 27-Nov-2012***
When a CSR logs in for the first time and tries to change the password or when a CSR's password expires and tries to change the password, no error messages are returned from the server. The problem is there is no indication anywhere that an error occurred during the password change and the control remains on the password change window. This is happening when we are trying to apply the password rules in the server code.
The errors are detected by the server and cm.pinlog actually logs them but they are not returned to the client in the form of a pop up window.
The user has custom errors for length of password and other conditions, these error messages are not piped back to the client. The user doesn't see any generic error message. The error messages are loaded into the /strings class in the database.
Steps to Reproduce:
With the custom password validation code in the policy opcode, if a CSR tries to change his/her password to a permanent password in the little window that pops up, then the error is not displayed.
Custom error message in a pop up window should be displayed to the user.
No error message is displayed, hence the CSR wouldn't know even if an error occurred until cm.pinlog is opened.
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