Improve domain related defaults when using v3 identity API
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-openstackclient |
Fix Released
|
High
|
Steve Martinelli |
Bug Description
In version 0.4.0 of python-
openstack --os-identity-
This results in an authentication request of:
-------
{
"auth": {
"scope": {
},
}
},
"identity": {
}
},
]
}
}
}
-------
If I then install python-
DEBUG: keystoneclient.
ERROR: openstack Authentication failure: Expecting to find domain in project - the server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error. (HTTP 400)
The request looks like this:
-------
{
"auth": {
"scope": {
}
},
"identity": {
}
},
]
}
}
}
-------
The domain is no longer filled in when one is not explicitly specified as a command-line option. If I specify '--os-user-
Changed in python-openstackclient: | |
milestone: | none → m6 |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in python-openstackclient: | |
assignee: | nobody → Steve Martinelli (stevemar) |
Changed in python-openstackclient: | |
status: | Confirmed → In Progress |
Changed in python-openstackclient: | |
milestone: | m6 → m7 |
Changed in python-openstackclient: | |
status: | Fix Committed → Fix Released |
This may have happened when the auth option checking was shifted to the auth plugins from ksc, it is certainly not intentional.