Skip to content
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] SecurityViolation when using a project name already used by someone else in same group #17

Open
erickmartins opened this issue Jun 18, 2021 · 3 comments

Comments

@erickmartins
Copy link
Collaborator

See /hyperfile/omero/autoimport/bolcun-filas_lab/besenr_20210615_180003/ on bhomero01lp.

@erickmartins
Copy link
Collaborator Author

In summary:

  1. if an import wants to use a project name that other user already is using, the new project is created, the new dataset is created, but we try to link the new dataset to the previously-existing project, which can cause a SecurityViolation.

The bigger issue is that, even though all the data is moved to the correct place server-side (so, for the user, these imports "happened"), the SecurityViolation causes the import to stop.

@erickmartins
Copy link
Collaborator Author

Possible solution: check Project ownership and create new one if it is not owned by relevant user

@erickmartins
Copy link
Collaborator Author

new cli-transfer based import process will make this moot - user on spreadsheet will be enforced and a new project/dataset will be created for that user even if a different user in the same group has same names.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant