(And also the fact that "cleanupUrl", which is necessary for
services to be comparable & recognizable, is protected, but for that
we can make a subclass of SimpleWebApplicationServiceImpl, which I
suppose doesn't count as modifying CAS code)
Well, actually not it is final.
Cheerio,
Michael Johnston
[email protected]
On 31-Jul-08, at 5:36 PM, Scott Battaglia wrote:
You should be able to set it on the CasArgumentExtractor. Set the
"disableSingleSignOut" property to true.
-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia
On Thu, Jul 31, 2008 at 6:50 PM, dale77
<[email protected]> wrote:
Can some kind soul please help me out with the configuration to
prevent CAS
posting single sign out xml back to services?
Our CAS server lives in a DMZ that has no DNS access, so when the
TGT is
destroyed the system hangs as CAS tries to post back to hosts it
cannot
resolve... I believe that single sign out is turned on by default,
hence the
need to switch it off in our system.
I expect it will be simply a bean modification in
deployerConfigContext.xml.
Does anyone know the necessary spring incantation?
Thanks!
Dale
--
View this message in context:
http://www.nabble.com/How-do-I-turn-off-single-sign-out-in-CAS3.2%2B-tp18765177p18765177.html
Sent from the CAS Users mailing list archive at Nabble.com.
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
