Apologies for not getting back to you sooner, I missed your update during the holidays. Here's my understanding of the situation.
It looks like the only way to hit the issue is if, a) you are authenticating and using v2.0 APIs, and b) the user is coming from the non-default domain. Remember that in v2.0 we do not have the concept of a domain, and as a result, the v2.0 APIs assume the default domain.
So a few more comments so we can narrow down the problem.
You mention that the admin user is tied to the default domain, so you only have a single domain in your deployment?
What's the value of `default_domain_id` in the config file, it's under the [identity] section?
If using v3 of the APIs, I believe this issue should go away, could you try that to make sure? A quick test would be:
Hey Kris,
Apologies for not getting back to you sooner, I missed your update during the holidays. Here's my understanding of the situation.
It looks like the only way to hit the issue is if, a) you are authenticating and using v2.0 APIs, and b) the user is coming from the non-default domain. Remember that in v2.0 we do not have the concept of a domain, and as a result, the v2.0 APIs assume the default domain.
So a few more comments so we can narrow down the problem.
You mention that the admin user is tied to the default domain, so you only have a single domain in your deployment?
What's the value of `default_domain_id` in the config file, it's under the [identity] section?
If using v3 of the APIs, I believe this issue should go away, could you try that to make sure? A quick test would be:
export OS_USERNAME=xxxx DOMAIN_ NAME=xxxx NAME=openstack DOMAIN_ NAME=xxxx API_VERSION= 3 /openstack- dev.int. godaddy. com:35357/ v3/
export OS_USER_
export OS_PROJECT_
export OS_PROJECT_
export OS_PASSWORD='xxxx'
export OS_IDENTITY_
export OS_AUTH_URL=https:/
then issue: `openstack project list`