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 #1974 (closed)

Opened 9 years ago

Closed 9 years ago

Use Session.useragent for identifying active sessionss

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

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

Change History (4)

comment:1 Changed 9 years ago by jmoore

  • Component changed from General to Security
  • Milestone changed from Unscheduled to OMERO-Beta4.2
  • Remaining Time changed from 1 to 0.75
  • Sprint set to 2010-03-19 (5)
  • Status changed from new to assigned

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.

comment:2 Changed 9 years 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.

comment:3 Changed 9 years ago by jmoore

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

comment:4 Changed 9 years ago by jmoore

  • Remaining Time changed from 0.75 to 0
  • Resolution set to fixed
  • Status changed from assigned to closed

(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.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.82031 sec.)

We're Hiring!