Severity of this issue is very low as invalid cookie value can only occur when AM server is being reinstalled (i.e. when users can have stale cookie value). Also the issue can be workarounded by closing and opening the browser (thus deleting the session cookie). However I feel like we might want to address this somehow.
When the SSO cookie contains invalid value it is being rejected by the backend and XUI ends with the following error:
stack trace for the server rejection
``` Daemon Thread [http-nio-8080-exec-3] (Suspended (breakpoint at line 49 in InvalidSessionIdException)) (out of synch) owns: NioEndpoint$NioSocketWrapper (id=2193) InvalidSessionIdException..process(SocketWrapperBase, SocketEvent) line: 887 NioEndpoint$SocketProcessor.doRun() line: 1684 NioEndpoint$SocketProcessor(SocketProcessorBase).run() line: 49 ThreadPoolExecutor(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1136 ThreadPoolExecutor$Worker.run() line: 635 TaskThread$WrappingRunnable.run() line: 61 TaskThread(Thread).run() line: 833 ```Severity of this issue is very low as invalid cookie value can only occur when AM server is being reinstalled (i.e. when users can have stale cookie value). Also the issue can be workarounded by closing and opening the browser (thus deleting the session cookie). However I feel like we might want to address this somehow.