-
Hash: SHA256
Rop,
On 3/10/15 2:57 PM, rop wrote:
We are trying to upgrade Tomcat from 7.0.35 to 7.0.59.
For some reason, the form-based authentication gets broken after
the upgrade, and just gives Invalid username and/or password,
please try again when trying to login.
Cannot find
and 7.0.49 do not exist in the tomcat archive)
And from 7.0.50 it breaks.
So apparently, between 47 and 50 some change occurred that breaks our
login
On Thu, Mar 12, 2015 at 3:37 PM, David kerber dcker...@verizon.net wrote:
On 3/12/2015 10:16 AM, rop wrote:
Hi Chris,
Thanks for your input.
Re
ma...@apache.org wrote:
On 12/03/2015 15:51, rop wrote:
Ah, I got it now.
Thanks, David.
Yes, the a-b-c-d points are OK then.
As a trouble-shoot action, I actually did an install-and-test binary
search
among the intermediate tomcat-versions to pinpoint exactly which version
breaks
Hi Chris,
Yes, we are applying salt before hashing (to prevent googling up many
passwords from the hashes).
Override probably seemed like easiest way at the time, but maybe a better
way now. Will check it out, thanks.
/Rop
On Thu, Mar 12, 2015 at 8:53 PM, Christopher Schultz
ch
We are trying to upgrade Tomcat from 7.0.35 to 7.0.59.
For some reason, the form-based authentication gets broken after the
upgrade,
and just gives Invalid username and/or password, please try again
when trying to login.
Cannot find anything in catalina.out related to this.
From our logging, it
Googling the exception, turns up this:
https://answers.atlassian.com/questions/54260/potenntial-incopmatibilty-between-tomcat-dpcp-oracle-active-objects
If that doesnt answer your question ja...@atlassian.com is asking you to
contact him :)
2013/1/16 KARR, DAVID dk0...@att.com
I got the responsibility of maintaining a legacy web-application running on
Tomcat 5.5.36 and using the *j_security_check* feature for
user-authentication.
One problem scenario I am looking into:
When you first start the browser and logon to the application, everything
works OK
The
