The problem
By default the bundled Crowd client configuration (stored in the crowd.properties file bundled in CROWD_DISTRIBUTION/client/conf) does not include the Crowd's SSO cookie name. This is an inferior configuration that will cause a flood of requests to Crowd to find out the cookie name on almost every action performed in the client application.

The fix
The default crowd.properties file should include the "cookie.tokenkey" property set to the default name of the Crowd SSO cookie "crowd.token_key". The documentation should also mention that the name of the cookie should be adjusted to match whatever is configured in Crowd.

The workaround
Adding the cookie.tokenkey property to the crowd.properties file used by the client application is enough to fix the problem.