Simplified identity management of a common area endpoint

• US 20070283427A1
• Filed: 06/01/2006
• Published: 12/06/2007
• Est. Priority Date: 06/01/2006
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Pall, Gurdeep S., Yee, Dawson, Gupta, Anoop, Maximo, Rui
• Application Number:
  US11/445,174
• Publication Number:
  US 20070283427A1
• Time in Patent Office: Days
• US Class Current: 726/9
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234

Abstract

Techniques are provided for configuring a device. A token including first information identifying a user is received. The first information is read from the token. The device is configured using the first information in accordance with configuration data for the user.

Claims

1. A method of configuring a device comprising:

receiving a token including first information identifying a user;

reading said first information from said token; and

configuring a device using said first information in accordance with configuration data for the user.

2. The method of claim 1, further comprising:

performing processing to authenticate the user using a portion of said first information.

3. The method of claim 1, further comprising:

communicating with a registration module to verify that said first information identifies a registered user.

4. The method of claim 1, wherein said device is configured on a temporary basis.

5. The method of claim 1, wherein said token is used to configure a plurality of different devices for a same user.

6. The method of claim 1, wherein said device is a phone.

7. The method of claim 1, wherein said device is a computer.

8. The method of claim 1, wherein said device is a mobile communications device.

9. The method of claim 1, wherein a first portion of said configuration data is stored on the token and a second portion of the configuration data is stored on a registration server.

10. The method of claim 9, wherein said token is initialized with said first information as part of registration of said user.

11. The method of claim 1, wherein said first information includes a private key, a digital certificate, and a personal identifier.

12. The method of claim 11, wherein said personal identifier is used to control whether processing is allowed using the private key.

13. The method of claim 11, wherein said personal identifier is a biometric indicator.

14. The method of claim 1, wherein said device is used in connection with video conferencing.

15. The method of claim 11, wherein said token includes a processor thereon used to generate the private key.

16. The method of claim 1, wherein said device is an endpoint in a communication path and communications to the user are routed to the device.

17. The method of claim 1, further comprising:

inserting said token into a token reader;

entering input data; and

determining whether said input data matches a personal identifier included in said first information on said token.

18. The method of claim 17, wherein, if said input data matches said personal identifier, subsequent processing is performed using a private key included in said first information on said token.

19. A computer readable medium comprising executable code for configuring a device comprising code that:

receives a token including first information identifying a user;

reads said first information from said token;

performing processing to authenticate the user using a portion of said first information; and

configures a device using said first information in accordance with configuration data for the user.

20. A method of configuring a device comprising:

receiving a token including first information identifying a user;

reading said first information from said token;

communicating with a registration module to verify that said first information identifies said user as a registered user;

configuring a device using said first information in accordance with configuration data for the user; and

forwarding communications for said user to said device for a duration while said device is configured for said user.