Comment 7 for bug 1471882

My understanding of the keystone V3 concept is that the 'user_domain' is integral part of the username (defaulting to 'Default' to permit V2 backwards compatibility) --> user_domain = namespace for usernames / authentication scope.

This is different to 'project' and 'domain' scope: They are about authorization scope ("scoping") and are mutually exclusive. Currently domain scoping seems not to be supported by the monascaclient so far and I did not attempt change this.

So I was hoping that my additions can only have limited side effects.

Would you have a kind of test suite which I could extend to include user domains?
----------------
These are the resources I used to understand the concept:
https://github.com/openstack/python-keystoneclient/blob/stable/kilo/keystoneclient/httpclient.py
http://developer.openstack.org/api-ref-identity-v3.html

The most important statement in the documentation was this one:
"Provide one of the following sets of credentials to authenticate:
User ID and password,
user name and password scoped by domain ID or name,
user ID and password scoped by project ID or name with or without domain scope,
or token."