-
Notifications
You must be signed in to change notification settings - Fork 21
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
key/fqfield error when requesting restricted field #789
Comments
Sending the correct status is quite important here as the client uses that information to control certain recovery logic. When resolving a long polling connection with a status code 200 the client currently assumes that the connection could be reopened immediately after a health check (for example after a reboot of the service). |
I can not reproduce the error. I saved your request in a file called
When anonymous is disabled, I get an empty response:
This is correct, since the anonymous can not see the user. When I activate anonymous user for meeting 1, I get the following response:
To enable the anonymous user, I called:
|
I cannot reproduce this anymore. |
I ran into this issue again today with current main. |
Can you tell me as detailed as possible, how I can reproduce it? |
I am using the dev setup with its unchanged example data ( When I do the first step as you described it:
I get
|
I can reproduce this. |
When the restrictor depends on db-values of the request user, then it has to pay attanchen, that the request is not send for the anonsmous user (userID==0) since the anonyomus user is not in the database. There were two cases, where a check was missing. This PR adds these checks. Fixes OpenSlides#789
I had another look and was able to reproduce it. The problem was the field The reason for that error was, that I checked the DB-Field I checked all other places, where I do a DB request for the request user and found another case for the personal_note. I am confident, that I found all places and that the error should not happen again (future changes not included). |
When the restrictor depends on db-values of the request user, then it has to pay attanchen, that the request is not send for the anonsmous user (userID==0) since the anonyomus user is not in the database. There were two cases, where a check was missing. This PR adds these checks. Fixes #789
When the restrictor depends on db-values of the request user, then it has to pay attanchen, that the request is not send for the anonsmous user (userID==0) since the anonyomus user is not in the database. There were two cases, where a check was missing. This PR adds these checks. Fixes #789
When requesting the following payload without an authentication token set an error is sent which does not seem right.
Request:
Error:
Besides from that the error message is sent with a status code 200. It would be better to receive an authentication error or at least a non ok status code in that case.
The text was updated successfully, but these errors were encountered: