All, Some users noticed that in Acegi 1.0 and higher (but not Acegi 1.0-rc2 or lower), CAS and Acegi refused to authenticate properly under certain conditions, namely when the jsession id was appended to the service URL. This was because Acegi 1.0 correctly encodes the service url to include the jsession id.
This was an issue with CAS (as no version of CAS ever accounted for the jsession id) and not with Acegi (which correctly encoded the URL). As of CAS 3.0.5, this issue has been corrected: http://www.ja-sig.org/products/cas/announcements/index.html#ann1 All CAS deployers who have clients that use Acegi 1.0 are encouraged to upgrade to 3.0.5. Thanks -Scott -- Scott Battaglia Application Developer, Architecture & Engineering Team Enterprise Systems and Services, Rutgers University v: 732.445.0097 | f: 732.445.5493 | [EMAIL PROTECTED] ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Home: http://acegisecurity.org Acegisecurity-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
