When the session being timed out with a crowd user, Artifactory reporting 500 in the logs.

When the session is timed out with a "crowd" user, Artifactory reporting 500 in the logs as below:

2020-04-16T02:57:04.475Z [jffe ] [ERROR] [5f7fddc9fd2f93a9] [ ] [main ] - Error in validateUiSessionAndSaveUserOnReqCROWD for url - /api/v1/ui/auth/screen/systemMessages

2020-04-16T02:57:04.476Z [jffe ] [ERROR] [5f7fddc9fd2f93a9] [ ] [main ] - Error: Request failed with status code 500

2020-04-16T02:57:21.802Z [jfrt ] [ERROR] [518e2e3ff5f94d88] [c.e.m.GlobalExceptionMapper:48] [http-nio-8081-exec-3] - getWriter() has already been called for this response{{2020-04-16T02:57:21.803L [tomct] [SEVERE] [ ] [org.glassfish.jersey.server.ServerRuntime$Responder] [org.glassfish.jersey.server.ServerRuntime$Responder process] - Error occurred when processing a response created from an already mapped exception. }}

2020-04-16T02:57:21.805L [tomct] [WARNING] [ ] [org.glassfish.jersey.server.ServerRuntime$Responder] [org.glassfish.jersey.server.ServerRuntime$Responder release] - Attempt to release request processing resources has failed for a request.

The UI will not redirect to the login page. Instead, it will stay in the last browsed page in the UI and it will throw the above error in the console.log.

Steps to reproduce:

1. Install the Artifactory 7.3.2.
2. Integrate crowd with Artifactory.
3. Login the UI with the crowd user.
4. Keep it idle until the session times out.