Authentication failed on high load and multiple replicas of jans auth server

[aguskwee]

Hi,
I encountered an issue on Janssen 1.1.0 during high load and used multiple replicas of jans auth server. For your info, single replica works OK. I am using redis to store sessionId to speed up authentication process. I also disable useLocalCache properties. By doing this, I assume, auth server will always read from the Redis to get the information on the session attributes.

However, sometimes, it seems that the session attributes are not synced between 2 different pods. Let says the user completes step 1 authentication and the request is handled inside pod1 auth server. Then, on the step 2 authentication, the request is handled by pod2. Then when getting the session attributes, some of the attributes are missing causing the auth server thinks that it has not passed step 1 authentication, hence, it returns error.

Has anyone encountered this issue?

Regards.