Hi,
We have a 11.4 SP6 WCC running in RHEL 6.10.
Sometimes when a user wants to log on WCC though he enters his ID and password properly, Dashboard screen is not loaded by login screen is loaded again and he is asked to enter again his ID/password.
I haven seen this behaviour in all main browsers (IE, Firefox and Chrome)
Following lines can be seen in WCC log
# Creating EEM session. ID=948C352BFBB02E0A3F762E08AD5E0630CA7D8E291E653E4BA5F881E445A40370.emidvwcc0001|USER=hppzybyt
CA-wcc.log:INFO | jvm 1 | 2019/10/25 07:30:12 | -782358 | @rest <172.19.0.172 hppzybyt ~D4B> [] INFO #AuthenticationResource # Logging user hppzybyt in. Creating session 948C352BFBB02E0A3F762E08AD5E0630CA7D8E291E653E4BA5F881E445A40370.emidvwcc0001.
CA-wcc.log:INFO | jvm 1 | 2019/10/25 07:30:15 | -782356 | @rest <172.19.0.172 hppzybyt ~948> [] INFO #AuthenticationResource # challengeInfo() returns ChallengeInfoResponse [useSecurePassword=true, modulus=ab9885e49678412ccf5171202ef12ce925316205e941812b82e8488728da9e88df76fde2e936d3072e30ff8d7ba640bc8220d571a177eb4bd8b32ef1adde89a306744f283e5f0745a66305458fba37b3d93141226f73ec7371071ded8654af3d4b29a8f9736023952f13d05c021a067702b94a5f7c198c94d0a6c8267f4739ad, pubExponent=10001, timeMillis=1571981415400]
CA-wcc.log:INFO | jvm 1 | 2019/10/25 07:30:17 | -782354 | @rest <172.19.0.172 hppzybyt ~948> [] INFO #AuthenticationResource # loginInfo() returns ntlmEnabled=false
CA-wcc.log:INFO | jvm 1 | 2019/10/25 07:30:20 | -782351 | @rest <172.19.0.172 hppzybyt ~948> [] INFO #AuthenticationResource # challengeInfo() returns ChallengeInfoResponse [useSecurePassword=true, modulus=ab9885e49678412ccf5171202ef12ce925316205e941812b82e8488728da9e88df76fde2e936d3072e30ff8d7ba640bc8220d571a177eb4bd8b32ef1adde89a306744f283e5f0745a66305458fba37b3d93141226f73ec7371071ded8654af3d4b29a8f9736023952f13d05c021a067702b94a5f7c198c94d0a6c8267f4739ad, pubExponent=10001, timeMillis=1571981419995]
CA-wcc.log:INFO | jvm 1 | 2019/10/25 07:30:20 | -782351 | @rest <172.19.0.172 hppzybyt ~948> [] INFO #SSOContext # Destroying EEM session. ID=948C352BFBB02E0A3F762E08AD5E0630CA7D8E291E653E4BA5F881E445A40370.emidvwcc0001 reason:AuthenticationResource.cleanupOldSession() new login request, cleaning old session
CA-wcc.log:INFO | jvm 1 | 2019/10/25 07:30:20 | -782351 | @rest <172.19.0.172 hppzybyt ~948> [] INFO #AuthenticationResource # cleanupOldSession for user hppzybyt. Destroying session 948C352BFBB02E0A3F762E08AD5E0630CA7D8E291E653E4BA5F881E445A40370.emidvwcc0001.
CA-wcc.log:INFO | jvm 1 | 2019/10/25 07:30:20 | -782351 | @rest <172.19.0.172 hppzybyt ~948> [] INFO #AuthenticationResource # encrypted value for login: 5a6440537cc87f92de2629e44cd32bebab3098ab72dc2f9401310185a4c4c897a8204d3b7ffefb9b7c073a0771549b270f74c4ab79935e94cb334afb770d37fb4a35dbf65d213a3eaad10b8efc3348e26f3eaf226179a2b141af9ecb2090cb905db32c8e143e0287b59bee9d6a526f6628cc82bcd65da01195bacbc651facd6f
CA-wcc.log:INFO | jvm 1 | 2019/10/25 07:30:20 | -782351 | @rest <172.19.0.172 hppzybyt ~948> [] INFO #SSOContext
it looks like if WCC were destroying an old session and creating a new one.
Is there any way to fix it?
thanks
José