Yes, there is a configuration option. You should have something similar to this in your configuration file:
<bean id="casProxyTicketValidator" class="org.acegisecurity.providers.cas.ticketvalidator.CasProxyTicketValidator"> <property name="casValidate"><value>https://localhost:8443/cas/proxyValidate</value></property> <property name="proxyCallbackUrl"><value>https://localhost:8443/contacts-cas/casProxy/receptor</value></property> <property name="serviceProperties"><ref bean="serviceProperties"/></property> <!-- <property name="trustStore"><value>/some/path/to/your/lib/security/cacerts</value></property> --> </bean> Your "casValidate" property should point to "serviceValidate" (i.e. https://secure.its.yale.edu/cas/serviceValidate) -Scott On 5/21/07, Tim Speevack <[EMAIL PROTECTED]> wrote:
Scott Battaglia <[EMAIL PROTECTED]> writes: > > > Tim,If you want to parse the XML, I believe the endpoint is "serviceValidate" and not "validate".-Scott Scott, I don't see how I could have any control over that. As far as I can tell this is triggered from the acegi implementation of CasProxyTicketValidator. Are you saying this is a configuration problem? _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
-- -Scott Battaglia LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
