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
Bug: User with ~100 classification groups cannot view submissions #179
Comments
Do you really need that many groups? This must break so much of the interface. I'm just trying to understand why you'd want data to be seperated is this many groups and why one user would be member of them all. |
Unfortunately, yes. The user that is a member of all groups is usually only accessed via API, individual users usually have ~10 groups. |
Instead of making a user part of all groups can you not just add a required group and make the API user part of that group? Required groups are automatically added to the submission as soon as a group is selected so this way it would ensure your API user always as access to the data. |
I don't think that's possible since the groups are dynamic groups, and not defined in the classifications config? |
Yeah so what I'd do is define that extra group in the classification.yml and set it to be a required group. Then make sure the API user is not part of any of the other groups. There is no issue setting up groups in the classification.yml and mixing this with the dynamic groups. |
Should be resolved in the latest release. If the issue still persists, feel free to reopen the issue 😀 |
Hey, this does not appear to be resolved. It also seems like I cannot re-open an issue. |
Describe the bug
We are controlling access to information in AssemblyLine using the classfication engine.
When logged on as an user with about 100 classifcation groups, an exception is thrown.
Error message:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Access to the submission
Screenshots
N/A
Environment (please complete the following information if pertinent):
Additional context
N/A
The text was updated successfully, but these errors were encountered: