Sorry, that last email actually sent?? Eeek, had only half written it! So yeah, in short I've tried the simple examples in phpCAS and they give the same result as using the main application: A page in the browser saying "authentication failed".
I've tried running through the ticket authentication process manually, using the first part of https://wiki.jasig.org/display/CAS/Proxy+CAS+Walkthroughas a guide. The code on the Lindode.com server works fine, while the code on our Amazon-hosted site fails. I've attached another version of the log, with hopefully all the relevant information in it. http://pastebin.com/AaC5uxN0 There's a null pointer exception on linhe 319 regarding org.springframework.web.servlet.tags.ThemeTag. I have *no* idea what that is. Charlie -- http://twitter.com/SonniesEdge On 30 August 2011 15:43, Charlie Owen <[email protected]> wrote: > ** > Sorry for the delay - bank holiday weekend here in the UK! > > > On 26/08/11 18:46, Joachim Fritschi wrote: > > can you please give one of the simple phpcas examples a try and see if it > is something specific that we can tie to the new host. (php version, curl, > strange hostname? etc.) > > > Configured and tried the phpCAS simple examples. I get exactly the same > response in the browser: a page entitled "CAS Authentication failed!" > > The cas server log ends before the interesting part. You only have the part > where the TGT is issued but the proxyValidate call is missing. Also the > whole stack dump you are recieving on the phpcas end should be available in > the logs. > > > Waiting on the CAS developer to get back to me with another version of the > log. > > It looks like inspectr is failing somehow with a null pointer. I can only > assume that something has changed between your two hosts. > > > Yeah, that's the nub of the problem. The server that we own and control > works fine. However, the final app is being deployed to a managed hosting > solution for the client. I'm trying to identify where the problem is so that > I can get them to fix it :( > > > Things that come to mind: > - service settings in the cas admin gui? > - hostname > - ipv4 vs ipv6 > - username/account used (missing required attributes?) > - other server in a possible cluster is hit? > > > > Other things you could try: Try hitting the proxyValidate page manually and > check if get a proper response. > > > AH. How do you mean hit it? > > > -- 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
