Project-based configuration management method and apparatus

• US 7,251,655 B2
• Filed: 05/21/2004
• Issued: 07/31/2007
• Est. Priority Date: 11/21/2000
• Status: Expired due to Fees

• Current Assignee: SZ DJI Technology Co., Ltd. (d/b/a DJI) (iFlight Technology Company Limited)
• Original Assignee: Microsoft Corporation
• Inventors: Kaler, Christopher G., Lovell, Martyn S., Grier, Michael J., Kruy, Steven J.
• Primary Examiner(s): ROBINSON, GRETA LEE
• Application Number:
  US10/851,885
• Publication Number:
  US 20040216090A1
• Time in Patent Office: 1,166 Days
• Field of Search: 707/9, 707/200, 707/203, 707/206, 717/122
• US Class Current: 1/1
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: Y10S 707/99939 Privileged access
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A configuration management system creates (602) each configuration by assigning a configuration identifier to each configuration. In addition, relational information is computed (706) that indicates the relationships between the configuration and any configurations upon which it is based. The system then tracks (604) changes to files of the configuration by storing information associating each new file version with the configuration identifier. The system also tracks (1210) changes to file properties. A configuration is then reconstructed (608) as of a desired date, by identifying (2104, 2106) the file versions and properties associated with that configuration as of the desired date. A determination is made (2110) whether a user that has requested the file versions has access privileges by first checking a security cache (2600) for the user privileges information. If the information is not on the cache, it is computed from a security table (2800) and stored on the cache. The system automatically compresses (3118) and reconstitutes (3006) file versions that are stored in the version store.

Claims

1. A method, performed by a configuration management system, for determining whether a user has access privileges to file versions of a desired configuration of a project, the method comprising:

determining whether a record for the user exists in a security cache, wherein the security cache includes user capabilities information for users who have requested access to files of the project;

where, if no record exists for the user;

determining the user capabilities information for the user from an access token for the user and security descriptors for the system, wherein the access token and security descriptors are stored in a security table, which is separate from the security cache; and

adding a new record to the security cache that includes the user capabilities information for the user; and

accessing the user capabilities information in the security cache for the user; and

where, if a record exists for the user;

accessing the user capabilities information in the security cache for the user; and

creating a virtual table by joining together the security cache and a file contents table, wherein the file contents table includes information identifying each file version managed by the system;

determining, from the virtual table, whether the user has access privileges to the file versions of the desired configuration; and

providing an indication of user access privileges to the file versions of the desired configuration.

2. The method as claimed in claim 1, further comprising storing an indication of the time when the new record was added to the security cache.

3. The method as claimed in claim 2, further comprising:

determining an age of a record within the security cache from the indication of the time;

if the age is greater than a threshold age, deleting the user capabilities information in the record; and

recomputing and storing the user capabilities information for the user that the record corresponds to.

4. The method as claimed in claim 3, further comprising:

determining the age of all records within the security cache; and

deleting, recomputing, and storing the user capabilities information for all the records having ages greater than the threshold age.

5. A computer-readable medium having computer-executable instructions for performing the steps recited in claim 1.