We have seen this before when the authentication service timeout is not configured properly what authentication are you using, in the past we have seen this when customers used AuthenticationLDAPTimeout instead of LDAPAuthenticationTimeout. It does appear to be a timeout issue as per your last comment.
But if you can trace this then it would provide more information.
Posted: 3 years ago
Updated: 3 years ago
Posted: 6 Dec 2017 3:42 EST Updated: 6 Dec 2017 7:32 EST