You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When migrating from OVH Keystone API v2.0 to v3 the Authenticate method return Bad Request which isn't very explicit. After debugging it, I see that the server respond with a json error message with the reason but is discarded by the client. We should maybe extend the error type to add the return messages and/or add an error field in v3AuthResponse. I can try to do a PR to add it if it make sens for the project but I have not a good knowledge of this code base.
{
"error": {
"message": "Expecting to find domain in user. The server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error.",
"code": 400,
"title": "Bad Request"
}
}
I resolve my issue by setting swift.Connection.Domain to default.
I can't find if the user domain is mandatory in the protocol but if it is we should be set to default if it is not provided, like in the project scope
When migrating from OVH Keystone API v2.0 to v3 the
Authenticate
method returnBad Request
which isn't very explicit. After debugging it, I see that the server respond with a json error message with the reason but is discarded by the client. We should maybe extend the error type to add the return messages and/or add an error field inv3AuthResponse
. I can try to do a PR to add it if it make sens for the project but I have not a good knowledge of this code base.Reading https://docs.openstack.org/keystone/pike/contributor/http-api.html and the server response :
I resolve my issue by setting
swift.Connection.Domain
todefault
.I can't find if the user domain is mandatory in the protocol but if it is we should be set to
default
if it is not provided, like in the project scopeswift/auth_v3.go
Lines 225 to 227 in 017f012
adding an else seems sufficient
swift/auth_v3.go
Lines 197 to 201 in 017f012
I can make a PR too.
The text was updated successfully, but these errors were encountered: