- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2020 10:48 AM
Hello,
I'm running Unity Connection 12.5(1) SU2. I had a user access the Web Inbox today with Chrome and after they tried to login they received /inbox/j_security_check error. I've never seen the before and this is the only person that has ever reported it.
Solved! Go to Solution.
- Labels:
-
Unified Communications
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2020 12:35 PM
When I've seen the "j_security_check error" in collab applications it is because the server you are accessing thinks you have two sessions open to the same page at the same time. It gives this error as a precaution to admins so they don't accidentally misconfigure things.
For your user, I would guess that they either have been in the Admin pages and then tried to switch to the Web Inbox using the same browser without fully logging out of the Admin pages. Or, they opened the Web Inbox and exited and then re-entered again without having fully logged out.
If they fully close their browser and access the Web Inbox fresh, do they still get the error?
Maren
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2020 12:35 PM
When I've seen the "j_security_check error" in collab applications it is because the server you are accessing thinks you have two sessions open to the same page at the same time. It gives this error as a precaution to admins so they don't accidentally misconfigure things.
For your user, I would guess that they either have been in the Admin pages and then tried to switch to the Web Inbox using the same browser without fully logging out of the Admin pages. Or, they opened the Web Inbox and exited and then re-entered again without having fully logged out.
If they fully close their browser and access the Web Inbox fresh, do they still get the error?
Maren
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2020 02:07 PM
Hi Maren,
Thanks for the reply. I saw a similar resolution on the Web when I was searching but, it was old and not much else on the topic. I have asked the user to close all instances of their browser and try it again. I will post the findings!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2020 07:25 AM
Yes, simply closing all browser instances resolved the issue!
Thanks for the quick response!!
