US 2007/0169175 A1Published application

Killing login-based sessions with a single action

AssigneeInternational Business Machines Corporation

InventorsKylene Hall, Johnny Shieh

Life of this patent

Estimating the term…

Loading patent…

Abstract

A method, system, and program are provided for killing login-based sessions with a single action. In addition to issuing a session token to a client system upon login by a user to a network service, a personal token is issued to the client system. The personal token is executable at the client system to trigger accesses to a personal session controller and to automatically disallow the session token if the personal session controller indicates that the personal token is deactivated. The personal session controller enables an interface through which a user is enabled select to deactivate all active personal tokens with a single action, such that a user manages killing login-based sessions independent of the server system authorizing each login-based session and independent of the client system to which the login-based session was authorized.

Claims20

Dependent claims

A method for user-specified management of at least one separate login-based session via a network, wherein each said separate login-based session is enabled by a separate session token issued to a separate client system from among a plurality of client systems from which a particular user logs in, wherein at least one server system authorizing each said separate login-based session issues each said separate session token, comprising;

responsive to detecting, at a personal session controller, authorization for each said separate login-based session, separately issuing from said personal session controller a separate personal token to each said separate client system, wherein each said separate personal token triggers access to said personal session controller via said network to request a status of said separate personal token and automatically disallows an associated separate session token if said personal session controller indicates said separate personal token status is deactivated;
and
enabling, by said personal session controller, an interface providing a selectable option for said particular user to deactivate all of said separate personal tokens with a single action, such that said particular user accesses said personal session controller to manage each said separate login-based session independent of each said server system authorizing each said separate login-based session.

A system for user-specified management of at least one separate login-based session via a network, wherein each said separate login-based session is enabled by a separate session token issued to a separate client system from among a plurality of client systems from which a particular user logs in, wherein at least one server system authorizing each said separate login-based session issues each said separate session token, comprising;

a personal session controller communicatively connected to said network, wherein said personal session controller further comprises:
means, responsive to detecting authorization for each said separate login-based session, for separately issuing from said personal session controller a separate personal token to each said separate client system, wherein each said separate personal token triggers access to said personal session controller via said network to request a status of said separate personal token and automatically disallows an associated separate session token if said personal session controller indicates said separate personal token status is deactivated;
and
means for enabling an interface providing a selectable option for said particular user to deactivate all of said separate personal tokens with a single action, such that said particular user accesses said personal session controller to manage each said separate login-based session independent of each said server system authorizing each said separate login-based session.

1 more element

A program for user-specified management of at least one separate login-based session via a network, said program embodied in a computer-readable medium, said program comprising computer-executable instructions which cause a computer to perform the steps of:

responsive to detecting authorization for each said separate login-based session from at least one server system each issuing a separate session token to a separate client system from among a plurality of client systems from which a particular user logs in, separately issuing a separate personal token to each said separate client system, wherein each said separate personal token triggers access to a personal session controller via said network to request a status of said separate personal token and automatically disallows an associated separate session token if said personal session controller indicates said separate personal token status is deactivated;
and
enabling an interface providing a selectable option for said particular user to deactivate all of said separate personal tokens at said personal session controller with a single action.

Dependencies are inferred from the claim text.

Facts

Application: 11/334,670Filed 18 Jan 2006
Published: 19 Jul 2007
Term ends: Not estimatedThe source records don’t support an estimate.

Classification5 codes

H04L 63/0807
For authentication of entities: using tickets, e.g. Kerberos
H04L 67/14
Network arrangements or protocols for supporting network services or applications: session management
H04L 67/142
Session management: managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
H04L 67/146
Session management: markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding