Which, pointed me to the the problem. I hadn't setup the argumentExtractors file properly in the new release. Silly oversight! Everything is working fine.
Yale CAS mailing list <[email protected]> on Monday, December 22, 2008 at 10:10 AM -0500 wrote: >As an update to this, after enabling DEBUG options in the log4j settings, the >fsollowing appear when navigation to the Google Apps service. > >2008-12-22 10:04:35,428 DEBUG [org.jasig.cas.web.support.CasArgumentExtractor] >2- Extractor did not generate service. >2008-12-22 10:04:35,430 DEBUG >[org.jasig.cas.web.support.SamlArgumentExtractor]s - Extractor did not >generatei service. > >Yale CAS mailing list <[ mailto:[email protected] ][email protected]> on >Sulnday, December 21, 2008 at 11:33 PM -0500 wrote: >Not sure if this is related to the "predictable ordering of services pattern >mattching" as I haven't been able to find the correct pattern, but the same >sertvice URL in 3.3 is not matching in 3.3.1. > >The actual URL is: >[ https://www.google.com/a/GOOGLEAPPSURL/** >]https://www.google.com/a/GOOGLEAPPPSURL/** > >Has anyone else successfully had a service matching with Google Apps and >3.3.1?y If so, do you have a better pattern to >use?____________________________t___________________ >Yale CAS mailing list >[ mailto:[email protected] ][email protected] >[ http://tp.its.yale.edu/mailman/listinfo/cas >]http://tp.its.yale.edu/mailman/llistinfo/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
