Task #1974 (closed)

Opened 5 months ago

Last modified 4 months ago

Use Session.useragent for identifying active sessionss

Reported by: jmoore Owned by: jmoore
Priority: minor Milestone: OMERO-Beta4.2
Component: Security Cc: atarkowska, jburel, cneves-x, bwzloranger
Remaining Time: 0.0d Sprint: 2010-03-19 (5)
Resources: n.a. References: n.a.
Referenced By: n.a.

Description

In order to identity active sessions, all clients should clearly mark either the default event type or the user-agent with some well-known string. I'd suggest initially using user-agent, which could eventually become a semi-colon separated list of agents, or  similar.

Requires changes to all clients (mark below when finished):

  • server: provide a utility method and default config.
  • importer
  • scripts
  • insight
  • web

References

Change History

Changed 4 months ago by jmoore

  • status changed from new to assigned
  • sprint set to 2010-03-19 (5)
  • component changed from General to Security
  • remaining_time changed from 1 to 0.75
  • milestone changed from Unscheduled to OMERO-Beta4.2

Moving into the current iteration. While working on #1704, it was easy to add support for agents. Currently, it is necessary to use the implicit context:

  client = omero.client()
  client.getImplicitContext().put(omero.constants.AGENT, "OMERO.web")
  sf = client.createSession();

Methods should be added to the omero.client object to set this value more simply. AND we need to decide if we want more intelligent agent strings than just "OMERO.web", "OMERO.insight", etc.

Changed 4 months ago by jmoore

(In [6458]) see #1974 - server-side changse for setting Session.userAgent

Note: unfortunately, some of the internal server changes for this commit made their way into the previous two commits.

Changed 4 months ago by jmoore

(In [6459]) see #1974 - Adding setAgent to all SDKs with sensible defaults

Changed 4 months ago by jmoore

  • status changed from assigned to closed
  • resolution set to fixed
  • remaining_time changed from 0.75 to 0

(In [6460]) fix #1974 - using setAgent almost everywhere

Work is still needed to pass the agent setting down to BlitzGateway from OmeroWeb, and Insight will need a new jar before the agent can be set.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.2.1-PRO © 2008-2009 agile42 all rights reserved (this page was served in: 0.223801 sec.)