Changing user identities without closing applications

• US 7,346,908 B2
• Filed: 08/17/2004
• Issued: 03/18/2008
• Est. Priority Date: 01/26/1999
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Sager, Christopher T., Mitchell, Darren, Evans, Christopher A.
• Primary Examiner(s): Nguyen; Van H.
• Application Number:
  US10/919,876
• Publication Number:
  US 20050022206A1
• Time in Patent Office: 1,309 Days
• Field of Search: 719/310, 719/320, 719/328, 713/1, 713/2, 713/100, 707/2, 707/9, 707/10, 709217-219, 717/121, 717/130
• US Class Current: 719/310
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 2221/2149 Restricted operating environment

Abstract

An operating system registry contains multiple “identities.” One of these identities is designated the current identity. An application executing on a multitasking computer system uses information stored in the current identity to configure the application, for example to provide a user-specific user interface. When an application opens, it registers with an identity manager using objects known as “connection points.” To switch identities, a user supplies the name of an identity to switch to. The identity manager then uses the registered connection points to query each of the applications for permission to switch identities. If all the registered connection points grant permission to switch identities, then the identity manager switches the current identity by changing information in the registry. The identity manager then notifies all applications, via their registered connection points, that a change to the registry has been made so that the applications can take appropriate action.

Claims

1. A computer system comprising:

a processor;

an identity manager executing on the processor;

a plurality of applications, the applications executing on the processor substantially simultaneously; and

a registry containing a plurality of profiles and a plurality of identities of users of the computer system, each of the identities containing a plurality of work-environment settings, one of the identities being designated in the registry as the current identity of a user of the computer system, one of the profiles being designated in the registry as the current profile,

wherein each of the applications registers at least one connection point with the identity manager when the application opens,

wherein the application gives permission to change identities to the identity manager via the registered connection point or points of the application, and

wherein the identity manager changes the identity that is designated as the current identity in the registry if permission is received from all registered connection points of each application, the identity manager changing the identity that is designated as the current identity without changing the profile that is designated as the current profile.

2. The computer system of claim 1, wherein one of the applications has multiple threads, each of the threads having a connection point that is registered with the identity manager.

3. A computer system comprising:

a processor;

an identity manager executing on the processor;

a plurality of applications, the applications executing on the processor substantially simultaneously; and

a registry containing a plurality of profiles and a plurality of identities of users of the computer system, each of the identities containing a plurality of work-environment settings, one of the identities being designated in the registry as the current identity of a user of the computer system, one of the profiles being designated in the registry as the current profile,

wherein each of the applications registers at least one connection point with the identity manager when the application opens,

wherein the identity manager changes the identity that is designated as the current identity without changing the profile that is designated as the current profile, and

wherein the identity manager notifies each of the applications via the connection points of the application that a change has been made to the registry.

4. The computer system of claim 3, wherein one of the applications has multiple threads, each of the threads having a connection point that is registered with the identity manager.

5. A computer-readable medium having computer-executable instructions for performing the steps of:

a. when a first application opens, creating a first connection point corresponding to the first application, the computer-readable medium having stored thereon a database containing a first identity of a user of a computer system and a second identity of a user of the computer system, the first identity being designated as the current identity, the first application using the first identity;

b. when a second application opens, creating a second connection point corresponding to the second application, the second application using the first identity;

c. registering the first and second connection points with an identity manager;

d. using the first connection point to query the first application for permission to switch identities and using the second connection point to query the second application for permission to switch identities; and

e. if all the registered connection points of all the first and second applications grant permission to change identities, changing the current identity from the first identity to a second identity, wherein the current identity is changed without having to close the first and second applications.

6. A computer-readable medium having computer-executable instructions for performing the steps of:

a. when a first application opens, creating a first connection point corresponding to the first application, the computer-readable medium having stored thereon a database containing a first identity of a user of a computer system and a second identity of a user of the computer system, the first identity being designated as the current identity, the first application using the first identity;

b. when a second application opens, creating a second connection point corresponding to the second application, the second application using the first identity;

c. registering the first and second connection points with an identity manager;

d. changing the current identity from the first identity to a second identity; and

e. using the first connection point to notify the first application that there has been a change in the database and using the second connection point to notify the second application that there has been a change in the database, wherein the current identity is changed without having to close the first and second applications.