Hello Alberto Could you kindly guide which specific logs I shoud check. Should I go ahead and check the logs of the application that is using the CAS REST Services? because I have already checked the CAS SERVER LOGS and there are no errors in those logs. Best Regards Syed Zaheer Mehdi
________________________________ From: Alberto Cabello Sánchez <[email protected]> To: [email protected] Cc: SYED ZAHEER MEHDI <[email protected]> Sent: Wednesday, April 16, 2014 4:31 AM Subject: Re: [cas-user] CAS 500 errors sometimes seen in logs when application is authenticating against CAS using REST services On Wed, 16 Apr 2014 02:05:36 -0700 (PDT) SYED ZAHEER MEHDI <[email protected]> wrote: > However, there are occasions when 500 errors come up, in such scenarios the > TicketGranting Ticket comes up as an empty string for the user and hence no > Service Ticket gets granted to the user. This is shown in below logs; > > SSO failed - CAS error - Username: xyz12 > Token: > Error: Invalid status code: 500 > > Could anyone kindly guide me why such a scenario is coming up where the TGT > value is getting passed as an empty string and hence CAS 500 errors are > coming up. Hello, Syed Zaheer. An "error 500" should write a more verbose information to log files. Please check it to get a complete error stack and hopefully a root cause. -- Alberto Cabello Sánchez <[email protected]> -- 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
