Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #11362 (new)

Opened 6 years ago

Last modified 3 years ago

Bug: No permissions on getObjects("Dataset")

Reported by: wmoore Owned by: wmoore
Priority: major Milestone: Unscheduled
Component: Web Version: n.a.
Keywords: n.a. Cc: Benjamin.sauer@…, server@…
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description (last modified by jamoore)

From: https://www.openmicroscopy.org/qa2/qa/feedback/7562/
See also: https://www.openmicroscopy.org/qa2/qa/feedback/9171/

webclient/views.py
caused by this line:

788:        datasets = c_type == "dataset" and list(conn.getObjects("Dataset", [c_id])) or list()

exception ::omero::InternalException?
{

serverStackTrace = ome.conditions.InternalException?: No permissions: Details:{;perm=rw----user=0;group=0;create=500;update=500}

at ome.security.basic.CurrentDetails?.applyContext(CurrentDetails?.java:413)
at ome.security.basic.BasicACLVoter.postProcess(BasicACLVoter.java:385)
at ome.tools.hibernate.ProxyCleanupFilter?.filter(ProxyCleanupFilter?.java:119)
at ome.util.ContextFilter?.filter(ContextFilter?.java:160)
at ome.util.ContextFilter?.doFilter(ContextFilter?.java:84)

Change History (12)

comment:1 Changed 6 years ago by jamoore

  • Cc Benjamin.sauer@… added
  • Description modified (diff)
  • Milestone changed from Unscheduled to 5.0.2

comment:2 Changed 6 years ago by wmoore

  • Milestone changed from 5.0.2 to Unscheduled

Until we have more info it's hard to schedule a fix for this.

comment:3 Changed 5 years ago by jamoore

  • Cc cblackburn added

Colin: is this what we're periodically seeing on the integration tests?

comment:5 Changed 4 years ago by wmoore

Same error at #13070

comment:6 Changed 4 years ago by jamoore

I assume some lack of context (i.e. -1) at the calling sight is triggering this.

comment:9 Changed 3 years ago by wmoore

Reproduced with this query

select obj from Dataset obj join fetch obj.details.owner as owner join fetch obj.details.group join fetch obj.details.creationEvent

Removing obj.details.group fixes the error and we only see the error if we use omero.group: -1 AND the list of Datasets includes objects that are not in the user's default group.

comment:10 Changed 3 years ago by mtbcarroll

  • Cc server@… added; cblackburn removed
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.109294 sec.)

We're Hiring!