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
comment:2 Changed 9 years ago by jmoore
comment:3 Changed 9 years ago by jmoore
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
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
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:
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.