Documentation for CAS upgrade in 2.0
Concerned version
Version: %2.0.0
Platform: Nginx
Summary
Apparently, in our config for 1.9 CAS was activated but no config havent been set...
In 2.0, this cause a breakdown in logoout chain with no Error in LLNG log after a possible timeout on LLNG side.
Disable the CAS as issuer module solve the issue. But better log, an maybe a fast response from LLNG is expected
Look in log the time for the next event...
Logs
Dec 10 10:59:59 srv-test-nginxv1 LLNG[13900]: Start routing default route
Dec 10 10:59:59 srv-test-nginxv1 LLNG[13900]: Processing importHandlerData
Dec 10 10:59:59 srv-test-nginxv1 LLNG[13900]: Processing controlUrl
Dec 10 10:59:59 srv-test-nginxv1 LLNG[13900]: Processing checkLogout
Dec 10 10:59:59 srv-test-nginxv1 LLNG[13900]: Processing code ref
Dec 10 10:59:59 srv-test-nginxv1 LLNG[13900]: Launching ::Issuer::CAS::logout
Dec 10 11:00:42 srv-test-nginxv1 LLNG[18459]: Get session 4c367d1817641275b02e4abaaa6c4ffb349ffa002a49653d944b61c299129363 from Handler::Main::Run
Dec 10 11:00:42 srv-test-nginxv1 LLNG[18459]: Check session validity from Handler
Dec 10 11:00:42 srv-test-nginxv1 LLNG[18459]: Session timeout -> 72000
Dec 10 11:00:42 srv-test-nginxv1 LLNG[18459]: Session _utime -> 1544457581
Dec 10 11:00:42 srv-test-nginxv1 LLNG[18459]: now -> 1544457641
Backends used
MongoDB