Once you made the change to the error.properties file, did you restart your web server?
Yes we did restart both our app and web server however the error code = 109 is not returning. Whenever I'm trying to log a locked account the error code = 105 still returns.
Sorry. Forgot to ask earlier. I hope you also purged the web server cache for good measure?
I also purge the web sever cache but with no luck the result is still the same. I haven't checked the signon.html if there's a link between the new error code (109) that must be declared in there.
By the way, just reading through your original question again.
If on the login page, you are still seeing 105 as the error code, then maybe you should change the text for 105 instead of 109?
It appears that you made a change to the text for 109, correct?
Sorry, I am not in front of a computer to check the text for 105 and 109 to determine what each one means.
Other thing is, maybe something else is going on to cause a 105 so it does not get to a 109 error message.
Nope. In the past, this has worked without any issues for me.
Never had to modify anything additional other than error.properties file.
105=Your User ID and/or Password are invalid.
109=Your account has been disabled/locked. Please wait for 30min then try again. (We just added this error code in the error.properties because originally it wasn't in there)
Based on our requirement we can't edit out 105 because it is still being used to prompt users who weren't locked out that they enter an invalid username/password.
I saw from Oracle that they remove 109 in the error.properties because of some security matters. However our client wants us to bring back this code.
By the way thanks for the effort of suggesting some possible ways to fix this.
Gotcha! You are welcome.
You might also want to check your app server logs when you get the 105 error to see if the userid is locked or invalid is getting logged there.
That might give you some ideas!
"I saw from Oracle that they remove 109 in the error.properties because of some security matters."
It might very well be the reason.