Re: [cas-user] Re: SPNEGO Client Selection Strategy

to choose to go directly to SPNEGO or evaluate > the client before starts SPNEGO. > > Christian Poirier > Mobile: 418-473-2824 > > 2018-05-23 1:58 GMT-04:00 Charles Le Gallic >: > >> Ok thanks. Let me know if you can confirm that current native >> implementation

Re: [cas-user] Re: SPNEGO Client Selection Strategy

ier a écrit : > Hi Charles > > Yes I did, but with my own development and my properties. I will check if > I can implement with Client Access Strategy by implementing my own SPNEGO > Service Access Strategy > > Christian Poirier > Mobile: 418-473-2824 > > 2018-05-22

Re: [cas-user] Re: SPNEGO Client Selection Strategy

e implementation based on a > RegisteredServiceAccessStrategy is possible. > > Christian Poirier > Mobile: 418-473-2824 > > 2018-05-18 1:28 GMT-04:00 Charles Le Gallic : > >> Hi Christian, >> >> Which version of CAS do you use ? >> >> It seems to be a version

Re: [cas-user] Re: SPNEGO Client Selection Strategy

Hi Christian, Which version of CAS do you use ? It seems to be a version below CAS 5.0.x (org.jasig packages and XML spring configurations). SPNEGO client selection strategy was working on 4.x version, but I cannot make it work after having upgrade to CAS 5.1.x Regards, Charles

[cas-user] Re: SPNEGO Client Selection Strategy

Hi Nicholas, It's seems to me that Kerberos / SPNEGO client selection strategy is broken since Alfresco 5.0.x. Indeed, there are several other messages in this discussion list referring to this problem : here , h

Re: [cas-user] Pac4j delegate authentication, adding a PrincipalResolver to ClientAuthenticationHandler

to override the createResult method of the > authentication handler. > > Thanks. > Best regards, > Jérôme > > > > 2016-09-30 14:48 GMT+02:00 Charles Le Gallic >: > >> Hi, >> >> We are currently using CAS 4.2.5 as an OpenId Connect (OIDC) client to

[cas-user] Pac4j delegate authentication, adding a PrincipalResolver to ClientAuthenticationHandler

Hi, We are currently using CAS 4.2.5 as an OpenId Connect (OIDC) client to retrieve the identity provider attributes. It works like a charm (congratulations to the CAS development team :)). But we wish to add additional attributes, retrieved from our internal database, to the user CAS principa