Trusting security attribute authorities that are both cooperative and competitive

• US 20040128559A1
• Filed: 12/31/2002
• Published: 07/01/2004
• Est. Priority Date: 12/31/2002
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Zurko, Mary Ellen, Pescatello, Joseph A.
• Application Number:
  US10/334,536
• Publication Number:
  US 20040128559A1
• Time in Patent Office: Days
• US Class Current: 713/202
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32

Abstract

A method and system for authorizing a user. The method comprises the steps of assigning a first role to a user in a first domain, assigning a second role in a second domain to the first role, and assigning access to a resource in the second domain to the second role. The method comprises the further steps of receiving a request from the user for the resource; and providing access to the resource, to the user. The invention may be employed by users and services to manage their interaction with those services, including configuring which they trust for what types of information, in what applications, and which subsets of information they can be trusted to provide.

Claims

1. A method of authorizing a user, comprising the steps of:

assigning a first role to a user in a first domain;

assigning a second role in a second domain to the first role;

assigning access to a resource in the second domain to the second role;

receiving a request from the user for the resource; and

providing access to the resource, to the user.

2. A method according to claim 1, wherein said request includes information identifying the role of the user in the first domain.

3. A method according to claim 2, wherein said request also includes information about the first domain.

4. A method according to claim 1, wherein the receiving step includes the step of passing a secure, trusted token to the second domain identifying the role of the user in the first domain.

5. A method according to claim 1, wherein:

a set of users have roles in the first domain; and

some of said roles in the first domain are defined as users in the second domain.

6. A method according to claim 1, further comprising the step of providing a database that identifies, for each of a set of roles in the first domain, one or more roles in the second domain, and wherein the step of assigning a second role in a second domain to the first role includes the steps of using said first role as an index into said database to identify said second role from the database.

7. A method according to claim 1, wherein each of a set of roles in the first domain is mapped to one or more roles in the second domain using a procedure selected from the group comprising:

mapping each of said set of roles in the first domain to a respective one role in the second domain, mapping each of said set of roles in the first domain to a plurality of roles in the second domain, and mapping a plurality of roles in the first domain to one, common role in the second domain.

12. A system according to claim 7, wherein:

a set of users have roles in the first domain; and

some of said roles in the first domain are defined as users in the second domain.

8. A system for authorizing a user, comprising:

means for assigning a first role to a user in a first domain;

means for assigning a second role in a second domain to the first role;

means for assigning access to a resource in the second domain to the second role;

means for receiving a request from the user for the resource; and

means for providing the user with access to the resource.

9. A system according to claim 8, wherein said request includes information identifying the role of the user in the first domain.

10. A system according to claim 9, wherein said request also includes information about the first domain.

11. A system according to claim 8, further comprising:

a secure, trusted token identifying the role of the user in the first domain; and

means for passing the token to the second domain.

13. A system according to claim 8, further comprising a database that identifies, for each of a set of roles in the first domain, one or more roles in the second domain, and wherein the means for assigning a second role in a second domain to the first role includes means for using said first role as an index into said database to identify said second role from the database.

14. A system according to claim 8, wherein the means for assigning a second role in the second domain includes means for mapping each of a set of roles in the first domain to one or more roles in the second domain using a procedure selected from the group comprising:

each of said set of roles in the first domain is mapped to a respective one role in the second domain, each of said set of roles in the first domain is mapped to a plurality of roles in the second domain, and a plurality of roles in the first domain is mapped to one, common role in the second domain.

15. A program storage device readable by machine, tangibly embodying a program of instructions executable by the machine to perform method steps for authorizing a user, said method steps comprising:

assigning a first role to a user in a first domain;

assigning a second role in a second domain to the first role;

assigning access to a resource in the second domain to the second role;

receiving a request from the user for the resource; and

providing access to the resource, to the user.

16. A program storage device according to claim 15, wherein said request includes information identifying the role of the user in the first domain.

17. A method according to claim 16, wherein said request also includes information about the first domain.

18. A method according to claim 15, wherein the receiving step includes the step of passing a secure, trusted token to the second domain identifying the role of the user in the first domain.

19. A method according to claim 15, wherein:

a set of users have roles in the first domain; and

some of said roles in the first domain are defined as users in the second domain.

20. A program storage device according to claim 15, wherein said method steps further comprise the step of providing a database that identifies, for each of a set of roles in the first domain, one or more roles in the second domain;

and the step of assigning a second role in a second domain to the first role includes the steps of using said first role as an index into said database to identify said second role from the database.

21. A program storage device according to claim 15, wherein each of a set of roles in the first domain is mapped to one or more roles in the second domain using a procedure selected from the group comprising:

mapping each of said set of roles in the first domain to a respective one role in the second domain, mapping each of said set of roles in the first domain to a plurality of roles in the second domain, and mapping a plurality of roles in the first domain to one, common role in the second domain.

22. A method of mapping from an attribute in one domain to an identity in another domain, comprising the steps of:

assigning a role to a user in a first domain;

assigning an identity in a second domain to the role;

assigning access to a resource in the second domain to the identity;

receiving a request from the user with the role for the resource;

mapping the request to the identity in the second domain; and

providing access to the resource, to the user.

23. A method according to claim 22, further comprising the step of providing a database that identifies, for each of a set of roles in the first domain, one or more roles in the second domain, and wherein the mapping step includes the steps of using said role as an index into said database to identify said identity for the role in the second domain.

24. A method according to claim 22, wherein each of a set of roles in the first domain is mapped to one or more identities in the second domain using a procedure selected from the group comprising:

mapping each of said set of roles in the first domain to a respective one identity in the second domain, mapping each of said set of roles in the first domain to a plurality of identities in the second domain, and mapping a plurality of roles in the first domain to one, common identity in the second domain.