Comment 2 for bug 1761050

Going through the zaqarclient codebase, it seems to me that they don't use keystone sessions to do http requests, instead, they use the session to get the token explicitly and further in their "transport drivers" they build another object to do the requests. in the case of the http driver, they create another requests session and put the headers explicitly there. This is where they do authentication:

https://github.com/openstack/python-zaqarclient/blob/master/zaqarclient/auth/keystone.py#L175

And they seem to use a deprecated method (get_token), however, that code does seem to trigger reauthentication (deep into the rabbithole). So... I'm not sure what the issue is. But I think it's either in zaqarclient or mistral.