Comment 21 for bug 1443913

I remember we discussed this bug with Mike Fedosin, and the reason indeed appeared to be in KSM token caching. The easiest workaround I see for now is to disable that caching. There is a risk, however, of a serious performance impact.
The correct way is to request a new token on a client.

I'll prepare a patch to disable KSM caching as I don't want to introduce quick&dirty solution in the main repository. If this option wins, we can always adopt it in our distributive some way, but it has really slim chances to land in community.