I'm using distributed web session with clustered SSO. Everything works fine, but I noticed a weird behavior: Web sessions get distributed only after the 2. request to the session when using a custom authenticator valve (even if I specify the BasicAuthenticatorValve itself).
I noticed this happens only if I specify an authenticator in jboss-web.xml, even if I use org.apache.catalina.authenticator.BasicAuthenticator. If I omit the <valve>...</valve> entry, everything works fine. This causes the client to accept over and over new sessions as soon as the requests get balanced. My balancer distributes evenly, without stickyness (Server one, Server two, Server one, ... and so on). I noticed while debugging, that the valve pipeline within the context is slightly different when specifying a custom authenticator.
Is this a bug or is this just something to configure? My environment is:
Same behavior in JBoss EAP 6.3, 6.4, Works on the first request in Wildfly 8.2