RE: [cas-user] JSON Service for CAS Client does not follow success message of required Handler

OK, this got interesting J I was hoping I could blame your handler for doing something weird but offhand I don’t see much. So go ahead and submit and issue please, and attach your overlay to the issues project. From: Claude Viéville [mailto:claude.vievi...@univ-lille1.fr] Sent: Tuesday, June

Re: [cas-user] JSON Service for CAS Client does not follow success message of required Handler

here is the link to the gist : https://gist.github.com/vieville/9c116fcdd0dfea70268b89d67c0c4b0c Le mercredi 22 juin 2016 03:48:43 UTC+2, Misagh Moayyed a écrit : > > You wrote L1LdapAuthenticationHandler.java, correct? Can you share it as a > gist, etc? > > > > *From:* Claude Viéville

RE: [cas-user] JSON Service for CAS Client does not follow success message of required Handler

You wrote L1LdapAuthenticationHandler.java, correct? Can you share it as a gist, etc? From: Claude Viéville [mailto:claude.vievi...@univ-lille1.fr] Sent: Monday, June 20, 2016 7:03 AM To: CAS Community Cc: mmoay...@unicon.net Subject: Re: [cas-user] JSON Service for CAS

RE: [cas-user] JSON Service for CAS Client does not follow success message of required Handler

Share logs please. From: Claude Viéville [mailto:claude.vievi...@univ-lille1.fr] Sent: Monday, June 13, 2016 11:19 AM To: jasig-cas-user Cc: cas-user@apereo.org; mmoay...@unicon.net Subject: Re: [cas-user] JSON Service for CAS Client does not follow success

Re: [cas-user] JSON Service for CAS Client does not follow success message of required Handler

Hi Misagh Thank you for your reply. I do not understand. What is then the value of the "requiredHandlers" attribute in the service json file? In my case, if I define the requiredHandler as "hfcAuthenticationHandler*2*" which during authentication throws an AuthenticationException (login

Re: [cas-user] JSON Service for CAS Client does not follow success message of required Handler

I don’t think that actually works the way you describe. You are telling CAS that the only way an authentication event can success is if handler X succeeds. In your case, it never does. If your use case is, “I only want this handler to run for this service, and that handler for that service”,