Comment 11 for bug 1842930

The same behaviour should be reproducible via command line client.

This issue is inherent if you use tokens, which are valid for some time, and services only validate the token itself, but not (via keystone), if the token has become invalid.