Patent Grant
7392246
This application is related to copending U.S. patent application Ser. No. 10/128,306, titled “Content Management System and Methodology Featuring Query Conversion Capability for Efficient Searching,” filed on Apr. 23, 2002, which is assigned to the same assignee as the present application, and which is incorporated herein by reference.
The present invention generally relates to databases and more particularly to a method and apparatus for storing and accessing information in content management systems. More specifically, this invention pertains to a method for maintaining security rules for document and folder access within the query process of the content management system.
Conventional content management systems typically include a library server (LS), one or more resource managers (RMs) and a client access application program interface (API). A client is coupled by a network to the API and seeks information stored in the resource manager. The library server stores metadata relating to the objects or data stored in the resource manager. The library server also controls the particular objects that a particular client user can access. Client users can submit requests known as queries through the API to search or retrieve metadata stored in the library server or objects stored in the resource manager.
Content management systems typically store three types of information, namely primary content (data), user metadata, and system metadata. Primary content is stored in the resource manager and includes both structured and semi-structured data such as text files, images, web pages, video clips, for example. Descriptions of, and information about the primary content stored in the resource manager, which are normally provided by client users, are referred to as “user metadata,” and are stored in the library server.
In contrast to “user metadata,” “system metadata” is the information created by the content management system itself for access control, storage management, and content tracking and reference. Both user metadata and system metadata reside in the library server that acts as a repository for the metadata in database form.
As compared to primary content, both user and system metadata are well structured. In general, content management systems provide a set of functions for content (data and metadata) creation, content search and retrieval, and content distribution that enable user to manage data, system metadata and user metadata. As mentioned earlier, one approach is to store the metadata in the library server and to store the primary content (data) in a separate component designated the resource manager. Another approach is to store both metadata and primary content in a common database.
In most content management systems, both system metadata and user metadata are searchable using SQL generated by a client-side API. For security purposes, the search methodology should allow only authorized personnel to view specific documents and folders. Skilled users can modify the SQL produced by the API to bypass security rules.
Current search mechanisms in content management systems can, in response to such a query, return to an unauthorized user a folder that matches a query. The folder does not include the sensitive information, but the existence of the folder gives information to the user that should not be released. Consequently, a skilled user can probe for the existence of classified or sensitive information through the query mechanism. By obtaining a response advising the user that a document matching the search request exists within the folder, a skilled user can search for other types of documents within the folder even though they are not actually authorized to view the documents, potentially creating a serious security exposure.
What is therefore needed is a system and method for enforcing security rules during a search for specific data stored in the content management system while maintaining the performance advantages of client-side query generation. The need for such a system and method has heretofore remained unsatisfied.
The present invention satisfies this need, and presents a system, a computer program product, and associated method (collectively referred to herein as “the system” or “the present system”) for implementing access control for queries to a content management system. The present system, installed on the content management server, generates the SQL sub-expression to implement the access control rules and merge with the SQL passed from the API.
The content management system query API provides capabilities to search within an item type hierarchy, across item types, across linked items, multi-value attributes, versions, and references, as described, for example, in patent application Ser. No. 10/128,306, supra. In addition, a built-in access control checking mechanism is implemented on the server side of the content management system.
In this client/server environment, the query SQL statement is built in two layers: the API (client) layer and the server layer. The API sends the query string to the underlying stored procedure. The stored procedure then generates the access control logic based on the configuration parameters of the library server.
This access control logic is dynamically added to the query string sent by the API. The stored procedure prepares, builds and executes this new query string as a dynamic SQL statement. The present system allows the content management system query to have the performance advantages of client-side query generation while maintaining the full security model enforced by the server.
In a client/server system, either the client or the database server could enforce the security by ensuring that the calls made to the server are legal. However, if the access control logic were included in the SQL generated by the API, a security exposure would exist because someone with skill could modify the SQL expression passed to the stored procedure and bypass security.
The present system circumvents this security risk by including the access control logic on the server side of the content management system. The server generates the SQL sub-expression that implements the access control rules. The SQL sub-expression is then merged with the SQL passed from the API.
The present system provides a stored procedure interface for clients to pass query information using SQL. Any user with the appropriate technical skills can use the relatively simple interface of the present system with ease. One feature of the stored procedure interface is that the SQL passed is updated dynamically with the access control privilege information of the user obtained from the library server. In addition, the access control logic is applied to all the intermediate steps of the query. This adds a new level of security to the content management system. The present system maintains security rules even if SQL sent to the server is modified by users with impressive SQL skills.
The present system utilizes SQL within the API and stored procedures. The concept of the present system could be applied to other query languages and other client/server systems that include query processing.
The present system can be protected by viewing the CLI (call level interface) trace and the event monitor (or equivalent tool). The CLI trace provides information on all parameters passed to the stored procedure, including the SQL string sent by the API, but without the SQL to implement the access control logic. The event monitor would have the completed SQL statement in addition to the access control logic.
The various features of the present invention and the manner of attaining them will be described in greater detail with reference to the following description, claims, and drawings, wherein reference numerals are reused, where appropriate, to indicate a correspondence between the referenced items, and wherein:
The following definitions and explanations provide background information pertaining to the technical field of the present invention, and are intended to facilitate the understanding of the present invention without limiting its scope:
API: Application Program Interface, a language and message format used by an application program to communicate with the operating system or some other control program such as a database management system (DBMS) or communications protocol.
Attribute: a property or characteristic, and more particularly, a field in a database.
Item: The basic information entities managed by the library server. “Items” as used herein come in two types, simple items and resource items. An item can be, for example, a folder or a document.
Metadata: data about data. Metadata is definitional data that provides documentation of or information about other data managed within an environment or by an application. Metadata may document data about data elements or attributes such as name, size, or data type. It may also log data about data structures including length, fields, and columns. Other data included in Metadata encompass the association, storage location, and ownership of data. Metadata may additionally include descriptive information about the context, quality and condition, and/or characteristics of data.
SQL: Structured Query Language, a standardized query language for requesting information from a database.
A client computer 35 including a client application 40 is coupled to content management system 100 via the application program interface (API) 30. Library server (LS) 20 is coupled to application program interface 30 and receives queries from client application 40. These queries seek information that is stored in library server 20 and/or resource manager 25. Library server 20 includes a query processor 15 that receives queries in a first format from client computer 35 and translates the queries into a second format usable by library server 20.
Library server 20 is coupled to resource manager 25 and contains user and system metadata concerning the primary content (data or objects) that are stored in resource manager 25. Many types of data can be stored in resource manager 25, for example, business information, applications, text, audio, video and streaming data, to name a few.
Content management system 100 employs a rich data model wherein data including metadata is stored in a tree-based hierarchical data structure including multiple database tables. Traditionally, search on the metadata is through either a specific API or via SQL language on some systems. Since content management systems in general provide a much richer data model than their underlying database systems, writing search queries based on a specific API or SQL can be both tedious and inefficient in content management systems without query processor 15. The content management system 100 with its query processor 15 advantageously insulates the client user from these high levels of query complexity.
The access control logic generator 10 restricts which items will be included in the query. Method 200 of content manager 100 utilizing access control logic generator 10 is illustrated by the block diagram of
At block 215, the query processor 15 parses the SQL string. The access control logic generator then inserts access control logic with every portion of the SQL string parsed in block 215. The access control logic is created according to access control privilege information of the user obtained from the library server 20. The library server 20 then executes the resulting SQL statement at block 225.
A sample query that is not expressed in query language can be exemplified as follows: Find folders where (criteria) Containing documents where (criteria).
The first portion of the query, “Find folders where (criteria)”, requests access to a folder matching some user specified criteria. If the user does not have access to the folder, the query is not resumed by the content management system. This level of security is already implemented by content management systems.
The second portion of this query, “containing documents where (criteria)”, requests documents matching the user's specified criteria. If the user does not have access to the document, previously the document portion of the query would not be resumed, but the folder request might be returned to the user. To eliminate this potential breach of security, the access control logic generator 10 inserts access control in both portions of the sample query, preventing either document or folder information returning to the user in the absence of proper authorization.
A sample query string sent by the application program interface 30 to the query processor 15 is shown below:
The access control logic generator 10 generates the following SQL string to verify access authorization of the user.
The access control logic generator 10 then includes the access control logic string with the query string, as shown below:
It is to be understood that the specific embodiments of the invention that have been described are merely illustrative of certain application of the principle of the present invention. Numerous modifications may be made to the system and method for implementing access control for queries to a content management system invention described herein without departing from the spirit and scope of the present invention.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4751740 | Wright | Jun 1988 | A |
| 4969091 | Muller | Nov 1990 | A |
| 5204961 | Barlow | Apr 1993 | A |
| 5321841 | East et al. | Jun 1994 | A |
| 5455953 | Russell | Oct 1995 | A |
| 5469576 | Dauerer et al. | Nov 1995 | A |
| 5615337 | Zimowski et al. | Mar 1997 | A |
| 5644768 | Periwal et al. | Jul 1997 | A |
| 5696898 | Baker et al. | Dec 1997 | A |
| 5701458 | Bsaibes et al. | Dec 1997 | A |
| 5742810 | Ng et al. | Apr 1998 | A |
| 5774719 | Bowen | Jun 1998 | A |
| 5778398 | Nagashima et al. | Jul 1998 | A |
| 5799310 | Anderson et al. | Aug 1998 | A |
| 5819252 | Benson et al. | Oct 1998 | A |
| 5826268 | Schaefer et al. | Oct 1998 | A |
| 5859966 | Hayman et al. | Jan 1999 | A |
| 5862378 | Wang et al. | Jan 1999 | A |
| 5875332 | Wang et al. | Feb 1999 | A |
| 5892902 | Clark | Apr 1999 | A |
| 5940616 | Wang | Aug 1999 | A |
| 6012067 | Sarkar | Jan 2000 | A |
| 6016394 | Walker | Jan 2000 | A |
| 6047291 | Anderson et al. | Apr 2000 | A |
| 6055637 | Hudson et al. | Apr 2000 | A |
| 6063133 | Li et al. | May 2000 | A |
| 6065117 | White | May 2000 | A |
| 6067414 | Wang et al. | May 2000 | A |
| 6088524 | Levy et al. | Jul 2000 | A |
| 6104393 | Santos-Gomez | Aug 2000 | A |
| 6128621 | Weisz | Oct 2000 | A |
| 6148342 | Ho | Nov 2000 | A |
| 6161182 | Nadooshan | Dec 2000 | A |
| 6167405 | Rosensteel, Jr. et al. | Dec 2000 | A |
| 6173400 | Perlman et al. | Jan 2001 | B1 |
| 6212511 | Fisher et al. | Apr 2001 | B1 |
| 6219826 | De Pauw et al. | Apr 2001 | B1 |
| 6233586 | Chang et al. | May 2001 | B1 |
| 6263313 | Milsted et al. | Jul 2001 | B1 |
| 6263342 | Chang et al. | Jul 2001 | B1 |
| 6272488 | Chang et al. | Aug 2001 | B1 |
| 6279111 | Jensenworth et al. | Aug 2001 | B1 |
| 6282649 | Lambert et al. | Aug 2001 | B1 |
| 6289344 | Braia et al. | Sep 2001 | B1 |
| 6289458 | Garg et al. | Sep 2001 | B1 |
| 6292936 | Wang | Sep 2001 | B1 |
| 6308274 | Swift | Oct 2001 | B1 |
| 6314449 | Gallagher et al. | Nov 2001 | B1 |
| 6327629 | Wang et al. | Dec 2001 | B1 |
| 6338056 | Dessloch et al. | Jan 2002 | B1 |
| 6339777 | Attaluri et al. | Jan 2002 | B1 |
| 6343286 | Lee et al. | Jan 2002 | B1 |
| 6591272 | Williams | Jul 2003 | B1 |
| 20010002486 | Kocher et al. | May 2001 | A1 |
| 20010008015 | Vu et al. | Jul 2001 | A1 |
| 20010019614 | Madoukh | Sep 2001 | A1 |
| 20010037317 | Freiwirth et al. | Nov 2001 | A1 |
| 20030018607 | Lennon et al. | Jan 2003 | A1 |
| 20030187848 | Ghukasyan et al. | Oct 2003 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20040162825 A1 | Aug 2004 | US |
