Re: [cas-user] Re: CAS 5.3.x PAC4J

2018-09-26 Thread Jérôme LELEU
Hi, Authentication handlers are called depending on the passed credentials. For a delegated authentication, a ClientCredentials is created which triggers the ClientAuthenticationHandler. Are you sure your new authentication handler supports ClientCredentials? Thanks. Best regards, Jérôme On

Re: [cas-user] Re: CAS 5.3.x PAC4J

2018-09-25 Thread Colin Wilkinson
Regarding Authentication I have ask a separate question to see if what I want to do is possible. On Wednesday, 26 September 2018 08:14:00 UTC+10, Colin Wilkinson wrote: > > Hi Jérôme, > > I am not 100% sure, if it maybe a edge bug with CAS server itself. > Basically its an issue when

Re: [cas-user] Re: CAS 5.3.x PAC4J

2018-09-25 Thread Colin Wilkinson
Hi Jérôme, I am not 100% sure, if it maybe a edge bug with CAS server itself. Basically its an issue when serialising the session, there is no problem when executing code only when trying to serialise the session and that made the problem hard to track. Basically I had two beans that were

Re: [cas-user] Re: CAS 5.3.x PAC4J

2018-09-25 Thread Jérôme LELEU
Hi, Was it a bug on your customization or something from the CAS server itself? Thanks. Best regards, Jérôme On Tue, Sep 25, 2018 at 4:37 AM Colin Wilkinson wrote: > Hi, > > I have worked out what the issue was. It one of the scope session beans > being loaded after the initial request that