Comment 2 for bug 1299146

Submitted as bug 1299153, further complications for Swift:

--------------
There is a problem with the Swift ACL code -- it is not domain-aware. It assumes that user names are unique. I've filled that as bug 1299146.

However, even if Swift's ACL code becomes domain-aware, a deployer might enable multiple domains, but use the v2 protocols with auth_token in the Swift pipeline.

A possible solution is to add the ability for Keystone to enforce unique user names. If Swift knows this it is enabled, it can process ACLs safely as-is without worrying about mapping users do domains.
--------------

Merging the two issues (creating Keystone and Swift tasks) since those are two facets of the same problem.