Task #5690 (new)
Opened 13 years ago
Last modified 9 years ago
LIM: session state is not immediately updated
Reported by: | wmoore | Owned by: | jburel |
---|---|---|---|
Priority: | major | Milestone: | Unscheduled |
Component: | Security | Version: | n.a. |
Keywords: | n.a. | Cc: | atarkowska, jburel, ux@… |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description
If I create a Private group then upgrade permissions to collaborative, the user chooser in webclient still appears disabled (as if group is still private) even though there are multiple users in the chooser.
Change History (11)
comment:1 Changed 13 years ago by atarkowska
- Owner changed from wmoore to jmoore
- Remaining Time 0.25 deleted
comment:2 Changed 13 years ago by jmoore
- Cc jburel added
- Component changed from Web to Security
There is a workaround (see below), but it might make sense to add a call to getEventContext() on every mutator in IAdmin. Note, though, this will happen on every call if we do it server-side. If you would rather do it client-side after a number of changes, it will work as expected.
commit fb41050de4c6aa8af9a8c2c9027d4674226005c3 Author: jmoore <josh@glencoesoftware.com> Date: Thu Feb 17 16:13:39 2011 +0100 Forcing reload of user context in test (Fix #4384, See #4011) diff --git a/components/tools/OmeroPy/test/integration/isession.py b/components/tools/OmeroPy/test/integration/isession.py index 80364d3..826db89 100644 --- a/components/tools/OmeroPy/test/integration/isession.py +++ b/components/tools/OmeroPy/test/integration/isession.py @@ -143,13 +143,14 @@ class TestISession(lib.ITest): svc.getMyOpenAgentSessions("OMERO.web") svc.getMyOpenClientSessions() - def XtestTicket2196SetSecurityContext(self): + def testTicket2196SetSecurityContext(self): ec = self.client.sf.getAdminService().getEventContext() exp0 = omero.model.ExperimenterI(ec.userId, False) grp0 = omero.model.ExperimenterGroupI(ec.groupId, False) grp1 = self.new_group([exp0]) # Change: should pass + self.client.sf.getAdminService().getEventContext() # Force reload #4011 self.client.sf.setSecurityContext(grp1) # Make a stateful service, and change again
comment:3 Changed 13 years ago by Aleksandra Tarkowska <aleksandrat@…>
(In [8232024488e3fc3b1a51cf15dd84eae3cc00d742/ome.git] on branch develop) this fixes the disabled list, see #5690, still we need to decide if we want to fix the context update problem in 4.3 or no
comment:4 Changed 13 years ago by jburel
- Sprint changed from 2011-06-02 (13) to 2011-06-16 (14)
Moved from sprint 2011-06-02 (13)
comment:5 Changed 13 years ago by jmoore
The following commits should have (also) been filed under this ticket rather than #5711:
- (In [7d5df5debe0b534dfcf68bc2a1039f2555ad957e/ome.git] on branch develop) this clean up getEventContext reload in every single call, see #5711 and remove unexpected print out
- (In [bd138a37947b11b8b60b31431433a1a44c70d6ff/ome.git] on branch develop) Reduce calls to IAdmin.getEventContext (See #4011, #5711)
- (In [afe533e910e4e4673555b7cd45d6e44c5309536f/ome.git] on branch develop) Fix setCurrentGroup in OMEROMetadataStoreClient (See #5711)
comment:6 Changed 13 years ago by jmoore
- Sprint 2011-06-16 (14) deleted
- Summary changed from Bug: Web user chooser after Private -> collab to LIM: session state is not immediately updated
After 4.3.0, this needs to be reviewed, possibly as a part of API evolution.
comment:7 Changed 13 years ago by jmoore
- Milestone changed from OMERO-Beta4.3 to OMERO-Beta4.3.2
API changes should be post 4.3.1
comment:8 Changed 13 years ago by jburel
- Milestone changed from OMERO-Beta4.3.2 to Unscheduled
comment:9 Changed 12 years ago by jburel
- Cc ux@… added
Scott can you review. It was reporting during 4.3 testing
comment:10 Changed 12 years ago by jburel
- Milestone changed from Unscheduled to OMERO-4.5
- Owner changed from jmoore to jburel
To check as part of 4.5
comment:11 Changed 9 years ago by jamoore
- Milestone changed from 5.x to Unscheduled
That problem is much deeper, then described and affects both Web and Insight clients. Basically every manipulation on the group or user level (adding user to the group, changing permission, etc) affect current context (every single active sessions). Ideal solution would be if server could notify client application about changes in the context. It is unlikely for client to update context in every single call, especially when few calls are required to complete the task. Josh what are your thoughts about that?