There doesn't seem to be any callback in the trace. I go back to my earlier question if it has to do anything to do with using the Saml11TicketValidator instead of the Cas20ProxyTicketValidator. The Saml11TicketValidator does not have any of the properties such as acceptAnyProxy, proxyCallbackUrl, proxyGrantingTicketStorage-ref
I was missing out on the service manage configuration but I have added attribute release for both http and https. Don't know if it has any bearing on the proxy ticket. What am I missing if I see this on the console: AttributePrincipalImpl.getProxyTicketFor(109) | No ProxyGrantingTicket was supplied, so no Proxy Ticket can be retrieved. If I am using Spring Security, do I need any configuration in the web.xml. The only security filter I have is the org.springframework.web.filter.DelegatingFilterProxy. Regards On 8/3/11 10:53 AM, Marvin Addison wrote: >> The proxy ticket is always NULL. > May be a proxy callback authentication or configuration problem. Turn > up the logging to DEBUG on the server and read whether the proxy > callback is invoked successfully. > > M > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
