Client agents for obtaining attributes from unavailable clients

• US 8,108,533 B2
• Filed: 03/01/2010
• Issued: 01/31/2012
• Est. Priority Date: 04/12/2007
• Status: Active Grant

• Current Assignee: YOUnite Inc.
• Original Assignee: YOUnite Inc.
• Inventors: Siress, Anthony, Fitzpatrick, Mark
• Primary Examiner(s): Meky, Moustafa M
• Application Number:
  US12/715,306
• Publication Number:
  US 20100191762A1
• Time in Patent Office: 701 Days
• Field of Search: 709200-203, 709217-229, 707/769, 707/802
• US Class Current: 709/229
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/59 Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable

Abstract

Creating an agency relationship among clients of a computer system with respect to personal privileged, or otherwise sensitive permissions and/or attributes, is described. The technique enables a querying client to obtain permission and/or attributes from a queried client, even if the queried client is unavailable.

Claims

1. A system comprising:

a server that maintains permissions to attributes;

wherein, in operation;

the server receives a request from a subscriber for an attribute of a client of a client server, wherein the client server includes a client agent for the client;

the server contacts the client agent to indicate that the attribute of the client has been requested;

the server receives the attribute from the client agent;

the server stores the attribute;

the server sends the attribute to the subscriber to satisfy the request for an attribute from the client;

the server deletes the attribute.

2. The system of claim 1, further comprising the client server.

3. The system of claim 1, wherein the client server includes a profile database having client profile information of the client.

4. The system of claim 1, wherein the server stores a permission to the attribute.

5. The system of claim 1, wherein the client agent stores a permission to the attribute.

6. The system of claim 1, wherein the client agent stores the attribute.

7. The system of claim 1, wherein the server forwards the request for an attribute to a plurality of client agents, including the client agent, simultaneously.

8. The system of claim 1, wherein the server forwards the request for an attribute to a plurality of client agents, including the client agent, in an order specified by the server.

9. The system of claim 1, wherein the server first contacts the client in an attempt to satisfy the request, but the client is not available.

11. The system of claim 9, further comprising the client server.

12. The system of claim 9, wherein the client server includes a profile database having client profile information of the client.

13. The system of claim 9, wherein the server stores a permission to the attribute.

14. The system of claim 9, wherein the client agent stores a permission to the attribute.

15. The system of claim 9, wherein the client agent stores the attribute.

16. The system of claim 9, wherein the server forwards the request for an attribute to a plurality of client agents, including the client agent, simultaneously.

17. The system of claim 9, wherein the server forwards the request for an attribute to a plurality of client agents, including the client agent, in an order specified by the server.

18. The system of claim 9, wherein the server first contacts the client in an attempt to satisfy the request, but the client is not available.

19. The system of claim 9, wherein the server comprises a permission server for storing permissions and an attribute server for storing attributes, wherein the permission server does not have access to attributes stored on the attribute server and the attribute server does not have access to permissions stored on the permission server.

10. A system comprising:

a server that maintains permissions to attributes;

wherein, in operation;

the server receives a request from a subscriber for an attribute of a client of a client server, wherein the client server includes a client agent for the client;

the server contacts the client agent to indicate that the attribute of the client has been requested;

the client agent sends the attribute to the subscriber to satisfy the request.

20. A method comprising:

maintaining permissions to attributes;

receiving a request from a subscriber for an attribute of a client of a client server, wherein the client server includes a client agent for the client;

contacting the client agent to indicate that the attribute of the client has been requested;

receiving the attribute from the client agent;

storing the attribute;

sending the attribute to the subscriber to satisfy the request for an attribute from the client;

deleting the attribute.