Multi-level security profile refresh
First Claim
Patent Images
1. A computer implemented method for performing a multi-level refresh of a cached user security profile associated with a client in a database management system comprising the steps of:
- receiving a user request from a user associated with said client;
copying a transaction aging value to a security aging value associated with said cached user security profile if said transaction aging value is specified with said user request;
calculating a decay time utilizing a profile refresh time stamp associated with said cached user security profile and a system clock; and
refreshing said cached user security profile if a refresh event occurs.
1 Assignment
0 Petitions
Accused Products
Abstract
A request is received from a user associated with the client and a transaction aging value is copied to a security aging value associated with the cached user security profile if the transaction aging value is specified with the user request. A decay time is calculated utilizing a profile refresh time stamp associated with the cached user security profile and a system clock. The cached user security profile is then refreshed if a refresh event occurs.
35 Citations
33 Claims
-
1. A computer implemented method for performing a multi-level refresh of a cached user security profile associated with a client in a database management system comprising the steps of:
-
receiving a user request from a user associated with said client;
copying a transaction aging value to a security aging value associated with said cached user security profile if said transaction aging value is specified with said user request;
calculating a decay time utilizing a profile refresh time stamp associated with said cached user security profile and a system clock; and
refreshing said cached user security profile if a refresh event occurs. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A method for performing a multi-level refresh of a cached user security profile associated with a client in a database management system comprising:
-
generating a transaction message wherein said transaction message comprises a transaction aging value and an indication that said transaction aging value is present; and
sending said transaction message to said database management system wherein said database management system comprises a multi-level security profile refresh routine and whereby said multi-level security profile refresh routine refreshes said cached user security profile if a refresh event occurs. - View Dependent Claims (12, 13)
-
-
14. A computer system for performing a multi-level refresh of a cached user security profile associated with a client in a database management system comprising:
-
a computer;
means for receiving a user request from a user associated with said client;
means for copying a transaction aging value to a security aging value associated with said cached user security profile if said transaction aging value is specified with said user request;
means for calculating a decay time utilizing a profile refresh time stamp associated with said cached user security profile and a system clock; and
means for refreshing said cached user security profile if a refresh event occurs. - View Dependent Claims (15, 16, 17, 18, 19, 20, 21, 22, 23)
-
-
24. An article of manufacture for use in a computer system tangibly embodying computer instructions executable by said computer system to perform process steps for performing a multi-level refresh of a cached user security profile associated with a client in a database management system, said process steps comprising:
-
receiving a user request from a user associated with said client;
copying a transaction aging value to a security aging value associated with said cached user security profile if said transaction aging value is specified with said user request;
calculating a decay time utilizing a profile refresh time stamp associated with said cached user security profile and a system clock; and
refreshing said cached user security profile if a refresh event occurs. - View Dependent Claims (25, 26, 27, 28, 29, 30, 31, 32, 33)
-
Specification