Managing Secure Resources in Web Resources that are Accessed by Multiple Portals

• US 20060294106A1
• Filed: 08/10/2006
• Published: 12/28/2006
• Est. Priority Date: 05/31/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Frieden, Kurt, Markoff, Matthew S., Rudominer, Mitchell B.
• Granted Patent: US 7,366,724 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 63/104 Grouping of entities
• CPC Class Codes: Y10S 707/99939 Privileged access
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation

Abstract

A method, apparatus, and computer-readable media for authorizing users of network portals to access a secure resource hosted by a secure server comprises storing a plurality of user identifiers, each representing a user of an owning portal; storing for each of the user identifiers an access privilege to the secure resource; storing a proxy user identifier representing a guest portal and a guest access privilege to the secure resource for all of the users of the guest portal; receiving from the owning portal a first request for access to the secure resource, the first request comprising a first user identifier representing a user of the owning portal; granting to the user of the owning portal access to the secure resource according to the access privilege stored for the first user identifier; receiving from the guest portal a second request for access to the secure resource, the second request comprising a second user identifier representing a user of the guest portal and a portal identifier representing the guest portal; and granting to the user of the guest portal access to the secure resource according to the guest access privilege stored in the authorization table for the proxy user identifier.

Claims

1. :

An apparatus for authorizing users of network portals to access a project hosted by a secure server, comprising;

an owning portal including an owning portal (OP) policy manager, an OP repository, and an authorization table, the OP policy manager for determining whether a user is authorized to communicate with the secure server, the OP repository for comparing authentication information to stored information, and the authorization table for storing a plurality of user identifiers, each representing a user of the owning portal, and for storing for each of the user identifiers an access privilege to the project;

wherein the owning portal is configured for assigning a proxy user identifier to a guest portal, and for associating a role with the proxy user identifier that conveys certain access privileges to the project, the role including an access level and an activity security; and

wherein the authorization table stores a portal identifier, role, and proxy user identifier representing the guest portal and a guest access privilege to the project for users of the guest portal;

a secure server including a secure server policy manager for receiving from the owning portal a first request for access to the project, the first request comprising a first user identifier representing a user of the owning portal, wherein the secure server policy manager grants to the user of the owning portal access to the project according to the access privilege stored in the authorization table for the first user identifier;

wherein the secure server policy manager receives from the guest portal a second request for access to the project, the second request comprising a second user identifier representing a user of the guest portal and the portal identifier representing the guest portal, wherein the secure server policy manager grants to the user of the guest portal access to the project according to the guest access privilege stored in the authorization table for the proxy user identifier, and

wherein the first request comprises a portal identifier representing the owning portal, wherein the apparatus further comprises a portal repository to receive the first request, and to authenticate the owning portal using the portal identifier in the first request.

2. :

The apparatus of claim 1, further comprising a user repository to authenticate the user of the owning portal based on the first user identifier and the security credential associated with the user of the owning portal.

3. :

The apparatus of claim 1, further comprising;

a portal policy manager to authorize the user of the owning portal based on the first user identifier; and

wherein the owning portal sends the first request to the secure server when the user of the owning portal is successfully authorized by the portal policy manager.

4. :

The apparatus of claim 1 further comprising a portal repository to receive the second request, and to authenticate the guest portal using the portal identifier in the second request.

5. :

The apparatus of claim 1, further comprising;

a portal policy manager to authorize the user of the guest portal based on the second user identifier; and

wherein the guest portal sends the second request to the secure server when the user of the guest portal is successfully authorized by the portal policy manager.

6. :

An apparatus for authorizing users of network portals to access a project hosted by a secure server, comprising;

an owning portal including an owning portal (OP) policy manager, an OP repository, and an authorization table, the OP policy manager for determining whether a user is authorized to communicate with the secure server, the OP repository for comparing authentication information to stored information, and the authorization table for storing a plurality of user identifiers, each representing a user of the owning portal, and for storing for each of the user identifiers an access privilege to the project;

wherein the authorization table stores a portal identifier, role, and proxy user identifier representing the guest portal and a guest access privilege to the project for users of the guest portal; and

a secure server established by an administrator of said owning portal including a secure server policy manager to receive from the owning portal a first request for access to the project, the first request comprising a first user identifier representing a user of the owning portal, wherein the secure server policy manager grants to the user of the owning portal access to the project according to the access privilege stored in the authorization table for the first user identifier;

wherein the secure server policy manager receives from the guest portal a second request for access to the project, the second request comprising a second user identifier representing a user of the guest portal and the portal identifier representing the guest portal, wherein the secure server policy manager grants to the user of the guest portal access to the project according to the guest access privilege stored in the authorization table for the proxy user identifier, and

wherein the first request comprises a portal identifier representing the owning portal, wherein the apparatus further comprises a portal repository to receive the first request, and to authenticate the owning portal using the portal identifier in the first request.

7. :

The apparatus of claim 6, further comprising a user repository to authenticate the user of the owning portal based on the first user identifier and the security credential associated with the user of the owning portal.

8. :

The apparatus of claim 6, further comprising;

a portal policy manager to authorize the user of the owning portal based on the first user identifier; and

wherein the owning portal sends the first request to the secure server when the user of the owning portal is successfully authorized by the portal policy manager.

9. :

The apparatus of claim 6, further comprising a portal repository to receive the second request, and to authenticate the guest portal using the portal identifier in the second request.

10. :

The apparatus of claim 6, further comprising;

a portal policy manager to authorize the user of the guest portal based on the second user identifier; and

wherein the guest portal sends the second request to the secure server when the user of the guest portal is successfully authorized by the portal policy manager.

11. :

Tangible computer-readable media embodying instructions executable by a computer to perform a method for authorizing users of network portals to access a project hosted by a secure server, the method comprising;

storing a plurality of user identifiers, each representing a user of an owning portal;

storing for each of the user identifiers an access privilege to the project;

assigning a proxy user identifier for a guest portal;

associating a role with the proxy user identifier that conveys certain access privileges to the project, the role including an access level and an activity security;

storing a portal identifier, role, and proxy user identifier representing the guest portal and a guest access privilege to the project for users of the guest portal;

receiving from the owning portal a first request for access to the project, the first request comprising a first user identifier representing a user of the owning portal, wherein the first request comprises a portal identifier representing the owning portal;

authenticating the owning portal using the portal identifier in the first request;

granting to the user of the owning portal access to the project according to the access privilege stored for the first user identifier;

12. :

The media of claim 11, wherein the method further comprises;

receiving at the owning portal from the user of the owning portal a second request for access to the project, the second request comprising the first user identifier and a security credential associated with the user of the owning portal; and

authenticating the user of the owning portal based on the first user identifier and the security credential associated with the user of the owning portal.

13. :

The media of claim 11, wherein the method further comprises;

authorizing at the owning portal the user of the owning portal based on the first user identifier; and

sending the first request from the owning portal to the secure server when the user of the owning portal is successfully authorized.

14. :

The media of claim 11, wherein the method further comprises;

receiving from the guest portal a second request for access to the project, the second request comprising a second user identifier representing a user of the guest portal and a portal identifier representing the guest portal;

authenticating the guest portal using the portal identifier in the second request; and

granting to the user of the guest portal access to the project according to the guest access privilege for the stored proxy user identifier.

15. :

The media of claim 11, wherein the method further comprises;

receiving at the guest portal from the user of the guest portal a second request for access to the project, the second request comprising a second user identifier and a security credential associated with the user of the guest portal; and

authenticating the user of the guest portal based on the second user identifier and the security credential associated with the user of the guest portal.

16. :

The media of claim 15, wherein the method further comprises;

authorizing at the guest portal the user of the guest portal based on the second user identifier; and

sending the second request from the guest portal to the secure server when the user of the guest portal is successfully authorized by the portal policy manager.

17. :

Tangible computer-readable media embodying instructions executable by a computer to perform a method for authorizing users of network portals to access a project hosted by a secure server, the method comprising;

storing a plurality of user identifiers, each representing a user of an owning portal;

storing for each of the user identifiers an access privilege to the project;

determining whether the user is authorized to communicate with the secure server;

comparing authentication information to stored information;

assigning a proxy user identifier for a guest portal;

storing a portal identifier, role, and proxy user identifier representing the guest portal and a guest access privilege to the project for users of the guest portal;

receiving from the owning portal a first request for access to the project, the first request comprising a first user identifier representing a user of the owning portal, wherein the first request comprises a portal identifier representing the owning portal;

authenticating the owning portal using the portal identifier in the first request;

granting to the user of the owning portal access to the project according to the access privilege stored for the first user identifier;

receiving from the guest portal a second request for access to the project, the second request comprising a second user identifier representing a user of the guest portal and a portal identifier representing the guest portal; and

granting to the user of the guest portal access to the project according to the guest access privilege for the stored proxy user identifier.

18. :

The media of claim 17, wherein the method further comprises;

receiving at the owning portal from the user of the owning portal a third request for access to the project, the third request comprising the first user identifier and a security credential associated with the user of the owning portal; and

authenticating the user of the owning portal based on the first user identifier and the security credential associated with the user of the owning portal.

19. :

The media of claim 17, wherein the method further comprises;

authorizing at the owning portal the user of the owning portal based on the first user identifier; and

sending the first request from the owning portal to the secure server when the user of the owning portal is successfully authorized.

20. :

The media of claim 17, wherein the method further comprises;

receiving from the guest portal a third request for access to the project, the third request comprising a third user identifier representing a user of the guest portal and a portal identifier representing the guest portal;

authenticating the guest portal using the portal identifier in the third request; and

granting to the user of the guest portal access to the project according to the guest access privilege for the stored proxy user identifier.

21. :

The media of claim 17, wherein the method further comprises;

receiving at the guest portal from the user of the guest portal a third request for access to the project, the third request comprising the second user identifier and a security credential associated with the user of the guest portal; and

authenticating the user of the guest portal based on the second user identifier and the security credential associated with the user of the guest portal.

22. :

The media of claim 21, wherein the method further comprises;

authorizing at the guest portal the user of the guest portal based on the second user identifier; and

sending the third request from the guest portal to the secure server when the user of the guest portal is successfully authorized by the portal policy manager.