Comment 9 for bug 1555629

Honestly, I'd prefer that it worked the same regardless of the config entry or backend configuration. End consumers of the API don't necessarily know how keystone is configured or what backends may be enabled, so they'll have to program defensively anyway and always pass the domain, just in case the configuration is such that you only get domain scoped results. Keystone should strive for the path of least surprise here.