IP Library Granted Patent US 7,464,162
Granted Patent B2
US 7,464,162 · App. 09/792,918 · Granted Dec 9, 2008

Systems and methods for testing whether access to a resource is authorized based on access information

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,464,162
App. No.
09/792,918
Granted
Dec 9, 2008
Kind
B2
Abstract

The Access Tester allows an administrator, or any other authorized user, to determine who or what entities have access to a resource, whether a particular individual or set of individuals have access to a resource under certain conditions and whether the authorization rules associated with a resource operate as intended. In one embodiment, an administrator uses a graphical user interface to enter access information. Exemplar access information includes one or more URLs identifying the resource(s), one or more request methods, one or more IP addresses, date and time restrictions, and an identification of one or more users. The Access Tester determines whether the identified users are authorized to access the resource(s) associated with the URL(s) using the request methods, during the date and time provided.

Claims (137)

1. A method for testing access to a resource available on a network, comprising the steps of:

receiving access information;

testing whether access to said resource is authorized based on said access information without granting authorization to said resource, said testing includes accessing an authorization rule for said resource and accessing an identity profile for a first user to determine whether at least a portion of said authorization rule is satisfied based on information in said identity profile, said authorization rule is not part of said identity profile; and

reporting whether access to said resource is authorized based on said step of testing.

2. A method according to claim 1 , wherein:

said step of receiving access information includes receiving said access information from a user interface.

3. A method according to claim 1 , wherein:

said access information is capable of including an identification of said resource, identification information for one or more entities, one or more request methods, an address of a device, date information and time information.

4. A method according to claim 1 , wherein:

said access information includes an identification of one or more entities;

said identification of one or more entities includes a user name for said first user; and

said step of testing includes determining whether said first user can access said resource.

5. A method according to claim 1 , wherein:

said access information includes an identification of one or more entities;

said identification of one or more entities includes a user role; and

said step of testing includes determining whether a set of one or more entities satisfying said role can access said resource.

6. A method according to claim 1 , wherein:

said access information includes timing information.

7. A method according to claim 6 , wherein:

said timing information includes a time range; and

said step of testing includes determining whether a set of entities can access said resource within said time range.

8. A method according to claim 6 , wherein:

said timing information includes a date range; and

said step of testing includes determining whether a set of entities can access said resource within said date range.

9. A method according to claim 1 , wherein:

said access information includes an address of a device; and

said step of testing includes determining whether an entity using said device can access said resource.

10. A method according to claim 1 , wherein:

said access information includes an access request method; and

said step of testing includes determining whether an entity can access said resource using said access request method.

11. A method according to claim 1 , wherein:

said access information includes a URL identifying said resource.

12. A method according to claim 1 , wherein:

said access information includes an identification of a set of entities; and

said step of testing includes the steps of:

(a) selecting an entity,

(b) checking authorization for said entity, and

(c) repeating steps (a) and (b) for each remaining entity in said set of entities.

13. A method according to claim 1 , wherein:

said access information includes an identification of said resource and does not include an identification of any entities; and

said step of testing determines which entities can access said resource.

14. A method according to claim 1 , wherein:

said access information includes an identification of an entity and does not include an identification of any resources; and

said step of testing includes determining which resources can be accessed by said entity.

15. A method according to claim 1 , wherein:

said step of testing includes determining whether all of said authorization rule is satisfied.

16. A method according to claim 15 , wherein:

said access information includes information for identifying a set of one or more entities;

said authorization rule includes role criteria; and

said step of determining whether all of said authorization rule is satisfied includes evaluating whether said set of one or more entities meet said role criteria.

17. A method according to claim 15 , wherein:

said access information includes information for identifying a set of one or more entities;

said authorization rule includes rule criteria; and

said step of determining whether all of said authorization rule is satisfied includes evaluating whether said set of one or more entities meet said rule criteria.

18. A method according to claim 1 , wherein:

said step of reporting is user configurable so that a user can provide an indication of whether to display one or more authorization rules.

19. A method according to claim 1 , wherein:

said step of reporting includes displaying first information indicating that said first user can access said resource at a first time and second information indicating that said first user cannot access said resource at a second time.

20. A method according to claim 1 , wherein sad step of testing includes the steps of:

searching for a specific authorization rule;

determining authorization using said specific rule if said specific rule is found; and

determining authorization using a default rule if said specific rule is not found.

21. A method according to claim 1 , wherein said step of testing includes the steps of:

identifying a policy domain;

searching for a policy;

determining authorization using a default rule for said policy domain if no policy is found; and

determining authorization using a specific rule for said policy if said policy is found.

22. One or more processor readable storage devices having processor readable code embodied on said processor readable storage devices, said processor readable code for programming one or more processors to perform a method, comprising the steps of:

receiving access information; and

testing whether access to a resource is authorized based on said access information, said testing includes:

identifying a policy domain to which said resource belongs, said policy domain includes a set of one or more policies,

determining whether said resource is associated with a policy in said set of one or more policies,

if said resource is not associated with a policy in said set, determining whether access to said resource is authorized using an authorization rule associated with said policy domain but not a policy in said set of one or more policies, and

if said resource is associated with a policy in said set, determining whether access to said resource is authorized using an authorization rule associated with said policy with which said resource is associated.

23. One or more processor readable storage devices according to claim 22 , wherein said processor readable code includes:

a user interface console;

an access tester; and

an authorization module.

24. One or more processor readable storage devices according to claim 22 , wherein:

said access information is capable of including an identification of said resource, identification information for one or more entities, one or more request methods, an address of a device, date information and time information.

25. One or more processor readable storage devices according to claim 22 , wherein:

said access information includes an identification of one or more entities;

said identification of one or more entities includes a user role; and

said step of testing includes determining whether a set of one or more entities satisfying said role can access said resource.

26. One or more processor readable storage devices according to claim 22 , wherein:

said access information includes an identification of one or more entities;

said identification of one or more entities includes a rule; and

said step of testing includes determining whether a set of one or more entities satisfying said rule can access said resource.

27. One or more processor readable storage devices according to claim 22 , wherein:

said access information includes timing information;

said timing information includes a time range; and

said step of testing includes determining whether a set of entities can access said resource within said time range.

28. One or more processor readable storage devices according to claim 22 , wherein:

said access information includes an access request method; and

said step of testing includes determining whether an entity can access said resource using said access request method.

29. One or more processor readable storage devices according to claim 22 , wherein:

said access information includes information for identifying a first user; and

said step of testing includes the steps of:

accessing an identity profile for said first user, and

comparing information in said identity profile to authorization criteria for said resource to determine whether said first user is authorized to access said resource.

30. One or more processor readable storage devices according to claim 22 , wherein:

said step of testing includes determining whether an authorization rule is satisfied;

said access information includes information for identifying a set of one or more entities;

said authorization rule includes rule criteria; and

said step of determining whether an authorization rule is satisfied includes evaluating whether said set of one or more entities meet said rule criteria.

31. An apparatus comprising:

a communication interface;

one or more storage devices; and

one or more processors in communication with said one or more storage devices and said communication interface, said one or more processors programmed to perform a method comprising the steps of:

receiving access information, and

testing whether access to a resource secured by an access system is authorized based on said access information, said access system includes an access management system and an identity management system wherein testing includes

identifying a policy domain;

searching for a policy;

determining authorization using a default rule for said policy domain if no policy is found; and

determining authorization using a specific rule for said policy if said policy is found.

32. An apparatus according to claim 31 , wherein:

said access information is capable of including an identification of said resource, identification information for one or more entities, one or more request methods, an address of a device, date information and time information.

33. An apparatus according to claim 31 , wherein:

said access information includes an identification of one or more entities;

said identification of one or more entities includes a user role; and

said step of testing includes determining whether a set of one or more entities satisfying said role can access said resource.

34. An apparatus according to claim 31 , wherein:

said access information includes an identification of one or more entities;

said identification of one or more entities includes a rule; and

said step of testing includes determining whether a set of one or more entities satisfying said rule can access said resource.

35. An apparatus according to claim 31 , wherein:

said access information includes timing information;

said timing information includes a time range; and

said step of testing includes determining whether a set of entities can access said resource within said time range.

36. An apparatus according to claim 31 , wherein:

said access information includes an access request method; and

said step of testing includes determining whether an entity can access said resource using said access request method.

37. An apparatus according to claim 31 , wherein:

said access information includes information for identifying a first user; and

said step of testing includes the steps of:

accessing an identity profile for said first user, and

comparing information in said identity profile to authorization criteria for said resource to determine whether said first user is authorized to access said resource.

Assignments (4)
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNOR FROM ORACLE, USA TO ORACLE CORPORATION PREVIOUSLY RECORDED ON REEL 016327 FRAME 0803. ASSIGNOR(S) HEREBY CONFIRMS THE IDENTITY OF THE ASSIGNOR. SEE THE FIRST PARAGRAPH OF ATTACHED CONFIRMATORY ASSIGNMENT.. Recorded Aug 8, 2005
From: ORACLE CORPORATION
To: ORACLE INTERNATIONAL CORPORATION
Reel/Frame 016364/0919 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE FROM ORACLE, USA TO ORACLE CORPORATION PREVIOUSLY RECORDED ON REEL 016327 FRAME 0222. ASSIGNOR(S) HEREBY CONFIRMS THE IDENTITY OF THE ASSIGNEE. SEE THE FIRST PARAGRAPH OF ATTACHED CONFIRMATORY ASSIGNMENT.. Recorded Aug 5, 2005
From: OBLIX, INC.
To: ORACLE CORPORATION
Reel/Frame 016361/0252 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 29, 2005
From: OBLIX, INC.
To: ORACLE, USA
Reel/Frame 016327/0222 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 29, 2005
From: ORACLE, USA
To: ORACLE INTERNATIONAL CORPORATION
Reel/Frame 016327/0803 →