Task #8144 (closed)
Opened 7 years ago
Closed 7 years ago
BUG: can't applySettingsToImages as system
| Reported by: | cneves | Owned by: | jamoore |
|---|---|---|---|
| Priority: | major | Milestone: | OMERO-4.4 |
| Component: | Services | Version: | n.a. |
| Keywords: | n.a. | Cc: | jburel, callan, jamoore |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | 2012-03-13 (10) |
Description
Can't use renderingSettingsService.applySettingsToImages if not logged in as owner of the destination images even if logged in user is an admin.
https://github.com/cneves/openmicroscopy/commit/72543d386ef9425d5d9bcb0f64384cf39f691751 adds a test that shows this behaviour. That commit is based on ome/develop with jmoore/3529-callcontext merged in.
Change History (4)
comment:1 Changed 7 years ago by cneves
comment:2 Changed 7 years ago by jmoore
- Cc jmoore added
- Milestone changed from Unscheduled to OMERO-Beta4.4
- Owner changed from jmoore to cneves-x
- Sprint set to 2012-02-28 (9)
Carlos, I'm passing back to you for clarification. Debugging in Eclipse, I see on the second call to applySettings, that RenderingSettingsImpl.loadRenderingSettings is returning null, because in fact there are no rdefs belonging to root (the current user) for the given pixels. Could this be a case of the use of the specific group ID coming back to bite us?
comment:3 Changed 7 years ago by jmoore
- Owner changed from cneves-x to jmoore
- Sprint changed from 2012-02-28 (9) to 2012-03-13 (10)
- Status changed from new to accepted
In discussion with Carlos, this isn't actually an omero.group issue, but rather a sudo/omero.user issue (#8097) which I'll handle next.
comment:4 Changed 7 years ago by jmoore
- Resolution set to fixed
- Status changed from accepted to closed
Fixed by using omero.user from #8097 (i.e. new-style sudo)
Test had a small problem, fixed in https://github.com/cneves/openmicroscopy/commit/78e80c3674c7b22ae57ccc40ca5d742fba87e64f