Bug: Admin chgrp user to private Project

[wmoore]

See ​https://github.com/openmicroscopy/openmicroscopy/pull/3420

If Admin tries to chgrp a user's Dataset to a private group and link it to an existing user's Project there, we get error below.

Failing integration test added in ​https://github.com/will-moore/openmicroscopy/commit/2615f1af31ad397d7e8d2e0a95adcfb0fe9ec93c

Failed stacktrace: ome.conditions.ReadOnlyGroupSecurityViolation: Cannot link to ome.model.containers.Dataset:Id_2753
Current user (root) is an admin or the owner of
the private group (Test Group=rw----). It is not allowed to
link to users' data.
at ome.security.basic.OmeroInterceptor.evaluateLinkages(OmeroInterceptor.java:513)
at ome.security.basic.OmeroInterceptor.onSave(OmeroInterceptor.java:160)
at org.hibernate.event.def.AbstractSaveEventListener.substituteValuesIfNecessary(AbstractSaveEventListener.java:414)
at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:293)

[mtbcarroll]

The error makes sense to me: the Python gateway's chgrpObjects actually tries to create and save a new link and the server complains that the admin can't be linking to someone else's stuff in their private group, which seems reasonable.

The Java gateway's importImageFile instead indirectly utilizes ImportSettings.userSpecifiedTarget which I would guess is the correct approach and why Insight has no trouble in this workflow.

[mtbcarroll]

In case the above was confusing: I was looking at Insight's import because I wondered how "import as" copes with all this. For simply moving data, in that situation Insight doesn't even offer the admin the user's containers as destinations for the move and also doesn't seem to let the admin put the user's data into containers.

[mtbcarroll]

Fixed by Will on the basis of Josh's ​https://github.com/openmicroscopy/openmicroscopy/pull/3420#issuecomment-73228516 by setting link.details.owner to the appropriate unloaded Experimenter before saving the link.