-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Worker and supervisor unable to auto annotate with models, 403 error #4996
Comments
Hi @aliu-dm Are you trying to run automatic annotations on the whole task or for one frame only? |
Hi @bsekachev For both a whole task and one frame only when in an organization. A normal user (not superuser) in their personal workspace can annotate a single frame, but not the whole task. When they try to annotate a whole task in their personal workspace they receive the same 403 error as above. |
I was not able to reproduce your issue (I am on current and this user is a worker in the organization: Because of some reasons I unable to run nuclio functions now, but I didn't get any 403 permissions denied and my request was sent to I also can submit that the worker can not get a list of currently using this URL: Theoretically you can catch this error after serverless response is received, but in this case could you please submit that you can see nuclio-dashboard calls in For example in my case, I see the following:
@nmanovic According to
Also we have the following test scope:
|
@aliu-dm , you need to add business group for your users. CALL_OFFLINE means to run a task for the whole task. Only users with the business role can do that. |
@nmanovic I've just updated a worker in the organization to be a part of the business group, so they have both user and business roles. When they are assigned a task, they can auto annotate both the task and a frame within a job in that task. But, if they are only assigned a job, they are unable to auto annotate that each frame. When a worker is not in the business group and assigned a task and assigned a task, they can only auto annotate a frame within a job in that task as you have indicated. On another note, I see in the documentation here a TBD for system roles, would it be possible to get something up there in the near future as I do not know what the access for the other roles entail? @bsekachev I can see similar logs as shown below, I've redacted the name of the function I used but it is basically the same as the yolov5 model with some modifications so I could use my own trained model
|
Hello, Can you please let me know how to create a business gropu? Thanks |
I also have this issue. I have a user, from an organisation with worker role, who is a member of a user group in the admin panel. If I only assign a job to this user — he couldn't use AI Tools (
And for the second case I got:
It seems strange to me, that when executing a serverless function on only one image in a job, we have request with the "path" equals "tasks/allow". Why is it going to "tasks/allow", shouldn't it go to "jobs/allow", @nmanovic or @bsekachev ? Could you fix it, please? P.S.
The latter problem was fixed with adding this user to the business group in the admin panel. |
As a temporary solution I made this modification to the cvat/apps/iam/rules/tasks.rego
Now our annotators could use AI Tools in their jobs, without adding them to the admin group with dangerous rights. Removing annotators from the admins also helped to clean up their Jobs page, now they see jobs assigned only to them. |
@hadi-ghnd In the admin panel, once you select a user as shown here. @alex4men Thanks for the temporary fix! It worked for me as well. |
@aliu-dm Thank you. After I login and hover over my name, there is no option called "Admin Page". I probably have done something wrong with Django. |
Looks like this account is not a superuser. |
@bsekachev Thank you. This solved my problem. |
@yasakova-anastasia why did you close it?) It's not solved properly yet. Still waiting for the answer from @bsekachev or @nmanovic on the question from the message #4996 (comment)
Is my solution legit, should I make a PR, or is it just a bad smelling kludge?) |
@yasakova-anastasia , could you please reproduce and fix if it is a problem on our side? |
Hi, I was able to reproduce the problem. Thinking on the fix. |
Please, provide the version you are using. |
2.3.0 from last week |
Your screenshot has another error, not with 403 code. |
Fixes cvat-ai#4996 - Added job access checks for model launches in the interactive mode
My actions before raising this issue
Similar issues seem to occur in #4860 and #4548
Expected Behaviour
Any user should be able to use automatic annotations in an organization, not just Owner and Maintainer
Current Behaviour
Only the owner and maintainers of an organization are able to use auto annotations, worker and supervisors receive the following error
Error: Request failed with status code 403. {"detail":"You do not have permission to perform this action."}.
Possible Solution
Steps to Reproduce (for bugs)
Context
I would like for other users in my organization to be allowed to auto annotate without giving them higher levels of privilege.
Your Environment
git log -1
): b9abbcedocker version
(e.g. Docker 17.0.05): 20.10.17The text was updated successfully, but these errors were encountered: