INFORMATION CARD FEDERATION POINT TRACKING AND MANAGEMENT

• US 20090077118A1
• Filed: 11/25/2008
• Published: 03/19/2009
• Est. Priority Date: 03/16/2007
• Status: Abandoned Application

• Current Assignee: Apple Inc.
• Original Assignee: Novell Incorporated (Open Text Corporation)
• Inventors: Busath, Wendy Michelle, Doman, Thomas E., Buss, Duane F.
• Application Number:
  US12/323,177
• Publication Number:
  US 20090077118A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/34 involving the use of external additional devices, e.g. dongles or smart cards
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices

Abstract

A client can store information about federation points. A federation point is a combination of an identifier of an account on a relying party and an identifier of an information card. The client can track which information cards are included n various federation points, and can use this information to assist the user in performing a transaction with relying parties.

Claims

1. An apparatus, comprising:

a client (105);

a receiver (210) on the client (105) to receive a request (705, 710, 715) from a user to manage at least one of a federation point (230, 525, 505, 510, 515) and an information card (220, 530);

a data store (225) on the client (105), the data store (225) capable of storing federation points (230, 525, 505, 510, 515), each federation point (230, 525, 505, 510, 515) including an identifier (520) of an account (605, 610, 615, 620) on a relying party (130) and an identifier (530) of an information card (220);

a data store accessor (240) on the client (105) to access said federation points (230, 525, 505, 510, 515) stored in the data store (225);

an identifier (265) on the client (105) to identify federation points (230, 525, 505, 510, 515) in the data store (225) and to identify information cards (220, 530) in the card selector (205) to which said request is applicable; and

a card selector (205) on the client (105) to present information about said federation points (230, 525, 505, 510, 515) in the data store (225) to said user and to receive from said user a change (720, 725, 730) to at least one of said identified federation points (230, 525, 505, 510, 515) and said identified information cards (220, 530).

2. An apparatus according to claim 1, further comprising a data store modifier (270) on the client (105) to modify the data store (225) responsive to said received change.

3. An apparatus according to claim 1, wherein said request (705, 710, 715) includes a request (705) to manage all federation points (230, 525, 505, 510, 515) including said relying party (130).

4. An apparatus according to claim 1, wherein said request (705, 710, 715) includes a request (710) to manage all information cards (220, 530) included in a selected federation point (230, 525, 505, 510, 515).

5. An apparatus according to claim 1, wherein said request (705, 710, 715) includes a request (715) to manage all federation points (230, 525, 505, 510, 515) including a selected information card (220, 530).

6. An apparatus according to claim 1, wherein:

the apparatus further comprises an query mechanism (250) on the client (105) to query an endpoint (805) on a relying party (130) for information (815) about an account (605, 610, 615, 620) included in a given federation point (230, 525, 505, 510, 515) including a given information card (220, 530); and

the receiver (210) is operative to receive said information (815) about said account (605, 610, 615, 620) included in said given federation point (230, 525, 505, 510, 515) including said given information card (220, 530) from said endpoint (805).

7. A method, comprising:

receiving (1405) a request (705, 710, 715) to manage at least one of a federation point (230, 525, 505, 510, 515) and an information card (220, 530);

identifying (1420, 1425) all federation points (230, 525, 505, 510, 515) and information cards (220, 530) to which the request is applicable;

presenting (1430) to a user the identified federation points (230, 525, 505, 510, 515) and the identified information cards (220, 530);

receiving (1435) from the user a change (720, 725, 730) to at least one of the identified federation points (230, 525, 505, 510, 515) or one of the identified information cards (220, 530); and

storing (1440) the received change (720, 725, 730).

8. A method according to claim 7, wherein receiving (1405) a request (705, 710, 715) to manage at least one of a federation point (230, 525, 505, 510, 515) and an information card (220, 530) includes receiving (1405) a request (705) to manage all federation points (230, 525, 505, 510, 515) including the relying party (130).

9. A method according to claim 7, wherein receiving (1405) a request (705, 710, 715) to manage at least one of a federation point (230, 525, 505, 510, 515) and an information card (220, 530) includes receiving (1405) a request (710) to manage all information cards (220, 530) included in federation points (230, 525, 505, 510, 515) including the identifier (520) of the account (605, 610, 615, 620) on the relying party (130).

10. A method according to claim 7, wherein receiving (1405) a request (705, 710, 715) to manage at least one of a federation point (230, 525, 505, 510, 515) and an information card (220, 530) includes receiving (1405) a request (715) to manage all federation points (230, 525, 505, 510, 515) including a selected information card (220, 530).

11. A method according to claim 7, further comprising querying (1445) an endpoint (805) of a relying party (130) regarding an account (605, 610, 615, 620) included in a given federation point (230, 525, 505, 510, 515) including a given information card (220, 530).

12. A system, comprising:

a client (105, 910);

a data store (225) on the client (105, 910), the data store (225) capable of storing federation points (230, 525, 505, 510, 515), each federation point (230, 525, 505, 510, 515) including an identifier (520) of an account (605, 610, 615, 620) of an account on a relying party (130) and an identifier (530) of an information card (220);

a set of information cards (220, 530) on the client (105, 910);

a data store accessor (240) on the client (105, 910) to identify at least one federation point (230, 525, 505, 510, 515) in the data store (225); and

an exporter (275) on the client (105, 910) to export information (905) about said at least one federation point (230, 525, 505, 510, 515) and information (905) about said at least one information card (220, 530).

13. A system according to claim 12, further comprising:

a workflow manager on the client (105, 910) to execute a cardflow;

a cardflow store on the client (105, 910), the cardflow store capable of storing said cardflow; and

the receiver (210) on the client (105, 910) is operative to receive a request by a user to initiate said cardflow to synchronize said at least one federation point (230, 525, 505, 510, 515).

14. A method, comprising:

receiving (1705) a request to synchronize federation point (230, 525, 505, 510, 515) information on a first client (105, 910) with a second client (105, 910);

identifying (1720) at least one federation point (230, 525, 505, 510, 515) on the first client (105, 910);

identifying (1725) at least one information card (220, 530) included in the identified federation point (230, 525, 505, 510, 515) on the first client (105, 910); and

exporting (1730) from the first client (105, 910) information (905) about the identified federation point (230, 525, 505, 510, 515) and information (905) about the identified information card (220, 530) included in the identified federation point (230, 525, 505, 510, 515).

15. A method according to claim 14, wherein receiving (1705) the request to synchronize federation point (230, 525, 505, 510, 515) information comprises receiving (1710) a request to initiate a cardflow on the first client (105, 910) to synchronize the federation point (230, 525, 505, 510, 515) information on the first client (105, 910) with the second client (105, 910).

16. A system, comprising:

a client (105, 910);

a data store (225) on the client (105, 910), the data store (225) capable of storing federation points (230, 525, 505, 510, 515), each federation point (230, 525, 505, 510, 515) including an identifier (520) of an account (605, 610, 615, 620) on a relying party (130) and an identifier (530) of an information card (220);

a set of information cards (220, 530) on the client (105, 910);

an importer (280) to receive information (905) about at least one federation point (230, 525, 505, 510, 515) and information (905) about at least one information card (220, 530);

a federation point merger (285) to merge said information (905) about said at least one federation point (230, 525, 505, 510, 515) into the data store (225); and

an information card merger (290) to merge said information (905) about said at least one information card (220, 530) into the set of information cards (220, 530).

17. A system according to claim 16, wherein the federation point merger (285) includes:

an absent federation point identifier (1005) to identify an absent federation point (230, 525, 505, 510, 515) in said information (905) about said at least one federation point (230, 525, 505, 510, 515) that is not in the data store (225); and

an adder (1010) to add said absent federation point (230, 525, 505, 510, 515) to the data store (225).

18. A system according to claim 16, wherein the federation point merger (285) includes:

a modified federation point identifier (1015) to identify a modified federation point (230, 525, 505, 510, 515) in said information (905) about said at least one federation point (230, 525, 505, 510, 515) that exists in the data store (225); and

a modifier (1020) to modify said federation point (230, 525, 505, 510, 515) in the data store (225) to be consistent with said modified federation point (230, 525, 505, 510, 515).

19. A system according to claim 16, wherein the federation point merger (285) includes:

a deleted federation point identifier (1025) to identify a deleted federation point (230, 525, 505, 510, 515) in the data store (225) that is not in said information (905) about said at least one federation point (230, 525, 505, 510, 515); and

a deleter (1030) to delete said deleted federation point (230, 525, 505, 510, 515) from the data store (225).

20. A system according to claim 16, wherein the information card merger (290) includes:

an absent information card identifier (1105) to identify an absent information card (220, 530) in said information (905) about said at least one information card (220, 530) that is not in the set of information cards (220, 530; and

an adder (1110) to add said absent information card (220, 530) to the set of information cards (220, 530).

21. A system according to claim 16, wherein the information card merger (290) includes:

a modified information card identifier (1115) to identify a modified information card (220, 530) in said information (905) about said at least one information card (220, 530) that exists in the set of information cards (220, 530); and

a modifier (1120) to modify said information card (220, 530) in the set of information cards (220, 530) to be consistent with said modified information card (220, 530).

22. A system according to claim 21, wherein the modifier (1120) is operative to modify said information card (220, 530) in the set of information cards (220, 530) to be included in a first federation point (230, 525, 505, 510, 515) instead of a second federation point (230, 525, 505, 510, 515).

23. A system according to claim 16, wherein the information card merger (290) includes:

a deleted information card identifier (1125) to identify a deleted information card (220, 530) in the set of information cards (220, 530) that is not in said information (905) about said at least one information card (220, 530); and

a deleter (1130) to delete said deleted information card (220, 530) from the set of information cards (220, 530).

24. A method, comprising:

importing (1805) into a client (105, 910) information (905) about at least one federation point (230, 525, 505, 510, 515) and information (905) about at least one information card (220, 530) included in the federation point (230, 525, 505, 510, 515);

merging (1810) the information (905) about the at least one federation point (230, 525, 505, 510, 515) with federation point (230, 525, 505, 510, 515) information on the client (105, 910); and

merging (1815) the information (905) about the at least one information card (220, 530) included in the federation point (230, 525, 505, 510, 515) with at least information card (220, 530) on the client (105, 910).

25. A method according to claim 24, wherein merging (1810) the information (905) about the at least one federation point (230, 525, 505, 510, 515) with federation point (230, 525, 505, 510, 515) information on the client (105, 910):

determining (1905) that the at least one federation point (230, 525, 505, 510, 515) does not exist in the federation point (230, 525, 505, 510, 515) information on the client (105, 910); and

adding (1910) the at least one federation point (230, 525, 505, 510, 515) to the federation point (230, 525, 505, 510, 515) information on the client (105, 910).

26. A method according to claim 24, wherein merging (1810) the information (905) about the at least one federation point (230, 525, 505, 510, 515) with federation point (230, 525, 505, 510, 515) information on the client (105, 910) includes:

determining (1915) that the at least one federation point (230, 525, 505, 510, 515) exists in the federation point (230, 525, 505, 510, 515) information on the client (105, 910); and

modifying (1920) the federation point (230, 525, 505, 510, 515) information on the client (105, 910) to be consistent with the information (905) about the at least one federation point (230, 525, 505, 510, 515).

27. A method according to claim 24, wherein merging (1810) the information (905) about the at least one federation point (230, 525, 505, 510, 515) with federation point (230, 525, 505, 510, 515) information on the client (105, 910) includes:

identifying (1925) a federation point (230, 525, 505, 510, 515) in the federation point (230, 525, 505, 510, 515) information on the client (105, 910) that is not included in the information (905) about the at least one federation point (230, 525, 505, 510, 515); and

deleting (1930) the identified federation point (230, 525, 505, 510, 515) from the federation point (230, 525, 505, 510, 515) information on the client (105, 910).

28. A method according to claim 24, wherein merging (1815) the information (905) about the at least one information card (220, 530) included in the federation point (230, 525, 505, 510, 515) with at least information card (220, 530) on the client (105, 910) includes:

determining (2005) that the at least one information card (220, 530) does not exist on the client (105, 910); and

adding (2010) the at least one information card (220, 530) to the client (105, 910).

29. A method according to claim 24, wherein merging (1815) the information (905) about the at least one information card (220, 530) included in the federation point (230, 525, 505, 510, 515) with at least information card (220, 530) on the client (105, 910) includes:

determining (2015) that the at least one information card (220, 530) exists on the client (105, 910); and

modifying (2020) the client (105, 910) so that the at least one information card (220, 530) on the client (105, 910) is consistent with the information (905) about the at least information card (220, 530).

30. A method according to claim 29, wherein modifying (2020) the client (105, 910) so that the at least one information card (220, 530) on the client (105, 910) is consistent with the information (905) about the at least information card (220, 530) includes modifying an information card (220, 530) on the client (105, 910) so that the information card (220, 530) on the client (105, 910) is included in the at least one federation point (230, 525, 505, 510, 515).

31. A method according to claim 24, wherein merging (1815) the information (905) about the at least one information card (220, 530) included in the federation point (230, 525, 505, 510, 515) with at least information card (220, 530) on the client (105, 910) includes:

identifying (2025) an information card (220, 530) on the client (105, 910) that is not included in the information (905) about the at least one information card (220, 530); and

deleting (2030) the identified information card (220, 530) from the client (105, 910).