System and method of dynamic entitlement

• US 20050278640A1
• Filed: 02/28/2005
• Published: 12/15/2005
• Est. Priority Date: 06/09/2004
• Status: Abandoned Application

• Current Assignee: Computer Sciences Corporation (DXC Technology Company)
• Original Assignee: Computer Sciences Corporation (DXC Technology Company)
• Inventors: Manning, Paul, Broughton, John M., Gottshall, Paul R. Jr., Jones, Edwin R., Ehlen, Phil, McDaniel, Darrell L.
• Application Number:
  US11/068,568
• Publication Number:
  US 20050278640A1
• Time in Patent Office: Days
• US Class Current: 715/741
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices

Abstract

A method for creating a user interface for a system may include dynamically assessing entitlement of a user to data elements and/or processes of the system based at least on a security setting of the user and a context of the transaction between the user and the system, authorizing the user to access portions of the system, and filtering a response message of the system based at least on the authorization of the user. The user interface may be rendered based at least on the filtered response message to allow the user to access some portions of the system and to inhibit the user from accessing other portions of the system. A system may include a CPU and a memory coupled to the CPU including program instructions executable to implement the method described above. A carrier medium may include program instructions executable to implement the method described above.

Claims

1. A method for creating a user interface for a system, comprising:

identifying a user of the system;

assessing a security setting of the user;

assessing context within a transaction between the user and the system;

assessing entitlement of the user to portions of the system based at least partially on the security setting of the user and the context of the transaction between the user and the system;

authorizing the user to access portions of the system to which the user is entitled;

filtering a response message of the system based at least partially on the authorization of the user; and

rendering the user interface based at least partially on the filtered response message to allow the user to access one or more of the portions of the system that the user is authorized to access and to inhibit the user from accessing one or more of the portions of the system that the user is not authorized to access.

2. The method of claim 1, wherein identifying the user comprises identifying a role of the user.

3. The method of claim 1, wherein assessing entitlement of the user comprises dynamically assessing entitlement of the user.

5. The method of claim 1, wherein rendering the user interface comprises withholding one or more features of the system, wherein the user is not authorized to access each of the withheld features.

9. The method of claim 1, wherein rendering the user interface comprises dynamically changing a function of the user interface.

10. The method of claim 1, wherein rendering the user interface comprises limiting availability of one or more data elements of the system to the user.

13. The method of claim 1, wherein rendering the user interface comprises displaying one or more authorized data entry fields substantially without gaps.

16. The method of claim 1, wherein rendering the user interface comprises displaying one or more authorized display fields substantially without gaps.

18. The method of claim 1, wherein rendering the user interface comprises updating a data element of the system based at least partially on the user'"'"'s security setting, the context within the transaction, and the presence or absence of one or more other data elements in a system response to a user request for information.

22. The method of claim 1, wherein rendering the user interface comprises displaying one or more read-only fields that the user is not authorized to access.

25. The method of claim 1, further comprising providing metadata to presentation services based at least partially on the user'"'"'s security setting and applicable support data and rules governing availability of the support data.

27. The method of claim 1, further comprising providing a dynamic display with available actions and drop-down data entry fields with filtered data elements based at least partially on the user'"'"'s security setting.

28. The method of claim 1, further comprising providing a dynamic display with available actions and drop-down data entry fields with filtered data elements based at least partially on metadata describing the transaction.

4. (canceled)

6-8. -8. (canceled)

11-12. -12. (canceled)

14-15. -15. (canceled)

17. (canceled)

19-21. -21. (canceled)

23-24. -24. (canceled)

26. (canceled)

29-30. -30. (canceled)

31. A method for creating a user interface for a system comprising:

accessing a website through a user system;

transmitting a security setting of a user via the website;

assessing entitlement of the user to access one or more portions of the system based at least partially on the security setting of the user; and

rendering a user interface based at least partially on the security setting of the user, wherein the user interface comprises one or more of the portions of the system the user is entitled to access, and wherein at least a portion of the system the user is not entitled to access is not viewable in the user interface.

32. The method of claim 31, further comprising assessing a context within a transaction between the user and the system, wherein the user interface is at least partially rendered based on the context of the transaction, and wherein the user interface is configured such that a transaction the user is not entitled to access is not viewable in the user interface.

33. The method of claim 31, wherein rendering the user interface comprises displaying one or more authorized data entry fields substantially without gaps.

47. The method of claim 31, wherein the user can view a portion of the system that the user is not entitled to access, and wherein the user is inhibited from accessing portions of the system the user is not entitled to access.

34-40. -40. (canceled)

41. A method for creating a user interface for a system comprising:

accessing a website through a user system;

transmitting a security setting of a user via the website;

assessing a context of a transaction between the user and the system;

assessing an entitlement of the user to access portions of the system based at least partially on the security setting of the user and the context of the transaction; and

rendering a user interface based at least partially on the security setting of the user and the context of the transaction, wherein the user interface is configured to allow the user to execute one or more actions the user is entitled to access, and wherein the user interface is configured to inhibit the user from executing one or more of the actions the user is not entitled to access.

44. The method of claim 41, further comprising providing a dynamic display with available actions and drop-down data entry fields with filtered data elements based at least partially on the user'"'"'s security setting and the context of the transaction.

45. The method of claim 41, wherein rendering the user interface comprises displaying one or more read-only fields that the user is not authorized to access.

42-43. -43. (canceled)

46. (canceled)