So just to confirm... does that mean that this paragraph:
There is a further consideration for active/active deployments: session
affinity. Session affinity is a feature of most load balancer equipment
where the device performs state management for incoming requests and routes
a client to the
Greetings,
I believe I have made some in roads this afternoon. I've switched to the
maven overlay method using the latest cas 5.0 snapshot.
I think I am getting very close to achieving what we need. I am currently
encountering the following error when deploying cas.war:
Caused by:
I am still struggling with this, when I try to visit the login page with
https I get this in the logs:
[STDERR] 2016-10-27 22:23:44.943:WARN:oejh.HttpParser:qtp3213500-21:
Illegal character 0x16 in state=START for buffer
Tom,
The service associated with the ST is specific. The error in your logs
is there because your client is trying to validate without parameters.
Either the redirect from CAS to your service after login has no
parameters or your service is stripping the parameters when trying to
post validation.
I'm back to CAS testing... I wrote a selective resolver derived from the
one mentioned (SelectiveAuthenticationProviderWebflowEventResolver) to
not trigger MFA when SPNEGO has succeeded. This part seems to work, but
when Service ticket is validated, I get :
