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 #13030 (new)

Opened 4 years ago

Last modified 4 years ago

Newly added omero prop cause SecurityViolation

Reported by: atarkowska Owned by: atarkowska
Priority: major Milestone: Permissions
Component: Services Version: OMERO-5.1.3
Keywords: n.a. Cc:
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description (last modified by atarkowska)

Newly added omero properties in the Python gateway throws an exception when connecting to the older server within the same series. getConfigService().getConfigValue(...) throws an exception SecurityViolation? when property is not present

Note that this is only an issue for nonadmin user, admin account doesn't see that

Change History (7)

comment:1 Changed 4 years ago by atarkowska

  • Description modified (diff)

Fixed in https://github.com/openmicroscopy/openmicroscopy/pull/4191 althouth I think there should be a better way to resolve it on the IConfig directly.

comment:2 Changed 4 years ago by atarkowska

  • Component changed from OmeroPy to Services
  • Milestone changed from OMERO-5.1.4 to OMERO-5.2.0
  • Owner changed from atarkowska to jamoore
  • Priority changed from blocker to major

Downgrading the priority and pushing to 5.2

comment:3 Changed 4 years ago by Aleksandra Tarkowska <A.Tarkowska@…>

(In [f7ca2741dba05215d22a1455be6e6e84bf53a88e/ome.git] on branch develop) preventing newly added settings from throwing an exception, see #13030

comment:4 Changed 4 years ago by jamoore

  • Owner changed from jamoore to atarkowska

Ola: what exactly would you like to happen? When we add a method in a point release (e.g. in 5.1.5) then all code has to use:

try:
  service.newMethod()
except Ice.OperationNotExistException:
  # handle

I would think that treating new config properties the same way would be ok.

comment:5 Changed 4 years ago by jburel

  • Milestone changed from OMERO-5.2.1 to OMERO-5.2.2

Milestone OMERO-5.2.1 deleted

comment:6 Changed 4 years ago by jburel

  • Milestone changed from OMERO-5.2.2 to OMERO-5.2.1

Milestone OMERO-5.2.2 deleted

comment:7 Changed 4 years ago by jburel

  • Milestone changed from OMERO-5.2.2 to Permissions
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.75980 sec.)

We're Hiring!