?
From: Zac Harvey
Sent: Friday, June 27, 2014 2:29 PM
To: cas-user@lists.jasig.org
Subject: RE: [cas-user] CAS: Broken webflow on failed authentication on 4.0.0?
Thanks again Dmitriy, and yes of course I have reproduced locally :-)
The HTTP 302 is certainly
Correction: it seems to be more reproducible in non-Chrome browsers (IE, FF,
Safari, etc.)
From: Zac Harvey
Sent: Friday, June 27, 2014 1:23 PM
To: 'cas-user@lists.jasig.org'
Subject: CAS: Broken webflow on failed authentication on 4.0.0?
I am on CAS 4.0.0 and am experiencing what I *believe*
Here’s some insight into this req-resp - on the second HTTP POST with correct
credentials, HTTP 302 is returned and browser simply re-issues GET to the
/login resource:
Remote Address:75.101.143.131:80
Request URL:http://mycas.commercehub.cloudbees.net/login
Request Method:POST
Status Code:302
than what we use! So this
is a problem that transpires network stack/topology/technologies and is
definitely a problem with CAS itself.
From: Dmitriy Kopylenko [mailto:dkopyle...@unicon.net]
Sent: Friday, June 27, 2014 2:16 PM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] CAS: Broken
a problem with CAS itself.
From: Dmitriy Kopylenko [mailto:dkopyle...@unicon.net]
Sent: Friday, June 27, 2014 2:16 PM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] CAS: Broken webflow on failed authentication on 4.0.0?
Here’s some insight into this req-resp - on the second HTTP
behavior).
I really think this is an issue with Spring Webflow.
From: Dmitriy Kopylenko [mailto:dkopyle...@unicon.net]
Sent: Friday, June 27, 2014 2:27 PM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] CAS: Broken webflow on failed authentication on 4.0.0?
Have you tried to reproduce
