Ticket #864 (closed story: fixed)
OmeroSessions Umbrella ticket
| Reported by: | jmoore | Owned by: | jmoore |
|---|---|---|---|
| Priority: | critical | Milestone: | 3.0-Beta3 |
| Component: | Security | Version: | 3.0-M1 |
| Keywords: | sessions, ejb, server | Cc: | atarkowska, callan, jmarie, donald |
Description (last modified by jmoore) (diff)
For milestone:3.0-Beta3 the Omero server will gain a session mechanism to replace JAAS for authentication and authorization. This is primarily due the login overhead per method call, but several other benefits are gained:
- A persistent location for information such as umask, client agent name, etc.
- Ability to create temporary logins for batch processing or URL links
- Timeouts
This ticket subsumes the following:
- #297 - An extra method on the session service should allow guest login
- It is still unclear which methods should allow the "guest" role
- #416 - umask will now be handled via the session service
- #486 - Throttling; though not necessarily completed with this ticket, the hooks for throttling individual users or groups, should be in place.
- #585 - The login module will no longer throw PSQLExceptions or similar
- #621 - Having this functionality in a service will also make it available to blitz]
- #664 - No longer needed with persistent sessions.
- #665 - Will consider adding @PermitAll, especially for guest support.
- ... more to come ...
See also : #772
Change History
Note: See
TracTickets for help on using
tickets.
