-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCS user endpoint uses wrong data type for booleans #181
Comments
basic auth or oidc? what user was used? the filter |
It was oidc and einstein. |
|
Some more info from Jesus.
|
Differences:
Json:
|
I will add authorization info, just in case is useful as well |
the output from ocis should now match the one from oc10:
vs
yes uidnumber, gidnumber, id and username are new, but TCP is built on the robustness principle and it applies here as well. This is only additional data. hmm the hm in reva we have an ocsBool:
let me check ocis-ocs which now implements the endpoint. owncloud/ocis-ocs#39 now uses the truthy rendering, which should now return boolean |
Vincent Petry commented: Set to p2 This is blocking testing efforts about TUS for mobile. It can wait until the next sprint but would be good to have it early in the next sprint. |
ocis.owncloud.works now returns this:
|
Unfortunately, clients still fail with this response. Checking out what's going on... |
Seen in owncloud/product#181 (comment) Please check which one is correct.
owncloud/ocis-ocs#47 did not fix. This is because another difference is there: Before: That makes Android not to finish the log on process and iOS finishes but display name is missing everywhere in the app |
I just noticed that the responses from curl https://demo.owncloud.com/ocs/v1.php/cloud/users/admin\?format\=json -u admin -s | jq
{
"ocs": {
"meta": {
"status": "ok",
"statuscode": 100,
"message": null
},
"data": {
"enabled": "true",
"quota": {
"free": 25287991296,
"used": 6784009,
"total": 25294775305,
"relative": 0.03,
"definition": "default"
},
"email": null,
"displayname": "admin",
"home": "/var/lib/owncloud/files/admin",
"two_factor_auth_enabled": "false"
}
}
} displayname curl https://demo.owncloud.com/ocs/v1.php/cloud/user\?format\=json -u admin -s | jq
{
"ocs": {
"meta": {
"status": "ok",
"statuscode": 100,
"message": "OK",
"totalitems": "",
"itemsperpage": ""
},
"data": {
"id": "admin",
"display-name": "admin",
"email": null
}
}
} display-name This is awful... 😞 |
Is |
Should this be changed in clients? this is not very backwards compatible then... |
According to @butonic we should support both |
Seen in owncloud/product#181 (comment) Please check which one is correct.
Seen in owncloud/product#181 (comment) Please check which one is correct.
Just checked with @felixboehm and @micbar , different attribute names ( |
So the server will not change the naming? and keep different spellings? |
Backend needs to be fixed. Spelling will be same as oC 10. ( |
I was checking with oC10 Docker, new iOS, current Android, and 2.7 desktop, they all use the same user endpoint:
|
From client perspective, only |
Connecting via the Android App works now. |
Vincent Petry commented: Mobile team might have a workaround, but it might not be worth working around if fixing the issue is trivial. [~dchristofas] are you able to quickly estimate the effort ? My gut feeling tells me that it might be a one liner. cc [~mbarz] |
Jörn Friedrich Dreyer commented: I'll work on this while waiting for builds to finish ... |
@jesmrec, tried to connect to https://ocis.owncloud.works using the Android App. The authentication process doesn't finish successfully and upon looking into the backend logs I found this:
Is there a bug in the backend or does the Android App need some changes.
The text was updated successfully, but these errors were encountered: