dotted user names and hosts are truncated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Undecided
|
Ed Cranford |
Bug Description
If a username or host in a user CRUD call has a dot in it, it gets truncated and serves 404s for the new shortened identifier.
In the worst case scenario, users could be modifying the wrong user should there happen to be a real user identified with the shortened field.
Setup:
curl -i http://
HTTP/1.1 200 OK
{
"users": [
{
"databases": [],
"host": "127.0.0.1",
"name": "example"
}
]
}
Expectation:
curl -i http://
HTTP/1.1 200 OK
{
"user": {
"databases": [],
"host": "127.0.0.1",
"name": "example"
}
}
Reality:
curl -i http://
HTTP/1.1 404 Not Found
{
"itemNotFound": {
"code": 404,
"message": "User example@127.0.0 cannot be found on the instance."
}
}
I'm aware that this is the accepted workaround:
curl -i http://
HTTP/1.1 200 OK
{
"user": {
"databases": [],
"host": "127.0.0.1",
"name": "example"
}
}
But it's admittedly a little surprising to a lot of API users, and I bet I could swing it so that the Expectation works without disrupting the rest of the API's behavior.
description: | updated |
Changed in trove: | |
milestone: | none → icehouse-2 |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | icehouse-2 → 2014.1 |
Fix proposed to branch: master /review. openstack. org/56966
Review: https:/