This bahaviour is because of specifics of Cas30ProxyTicketValidator requests and the response view rendering by ContentNegotiatingViewResolver. Proxy validator seems not to set the accepted content types on the URLConnection. This causes in my case requesting the Proxy Ticket with content type text/html. Some strange InternalResourceViewResolver takes the control over the response rendering and can not serve anything meaningful. The other candidate views are not picked because they serve application/xml contenttype what Cas30ProxyTicketValidator doesn't request.
My workaround is to add the accept header to the proxy ticket validator and to proxy retriever. If the Cas30ProxyTicketValidator still be the official way to connect to CAS, i could propose the pull request. On Wednesday, July 12, 2017 at 4:31:01 PM UTC+2, Gena Batalski wrote: > > Hello > > I'm getting the problem while retrieving the proxy ticket. After the PT > successfully created and written to Audit-Log, the response processing > doesn't pick up the "protocol/2.0/casProxySuccessView.html" to render the > ticket back but end up with Error 404. > > What is wrong? > > Regards, > > Gena > -- - CAS gitter chatroom: https://gitter.im/apereo/cas - CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html - CAS documentation website: https://apereo.github.io/cas - CAS project website: https://github.com/apereo/cas --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/98be1dc6-eb3f-4e81-a713-d91d9c7eab92%40apereo.org.
