A method, an apparatus, a computer system, a security component and a computer readable medium for defining access rights in metadata-based file arrangement

Field of the Invention

0001The present invention relates to defining access rights for objects in a computer system.

Background of the Invention

0002In a computer system, an access control list (ACL) is a solution of a security model for giving permissions to users for accessing electronically stored object. An ACL specifies which users and/or user groups are authorized to access objects and which operations are allowed on given objects. The operations can include reading ("R") from an object, writing ("W") to an object, deleting ("D") an object, and executing ("X") an object. Traditionally the users are identified by their name, and the groups by their members.

0003In addition to name-based access control, there is a solution for a role-based access control. In such a system, the permission to perform a certain operation is assigned to a specific role rather than a name. This eases the maintenance work because ACL doesn't have to be updated every time a new user is added to a certain job function.

0004Aforementioned solutions are derived from so called traditional folder structure, where folders are located in a static folder hierarchy. Therefore also ACL's are limited to a single hierarchy of access rights. Similarly, access roles are often statically assigned from a predefined set of users of user groups.

0005A publication <patcit id="pcit0001" dnum="US20080155652A"><text>US 2008/0155652</text></patcit> discloses a method and a system for using ACL rule to generate an ACL for a document included in a file plan. A file plan includes a plurality of containers, wherein each container is capable of providing management information for documents in the file plan. An ACL rule indicates one of the plurality of ACL rules, wherein the ACL rules provide different ways to form file plan document ACL's using at least one of an ACL defines for a container and a pre-file plan document ACL indicating users enable to access the document before the document is added to the file plan. A request to add a document to the file plan is received and a file plan document ACL is generated according to the defined ACL rule. The file plan document ACL is associated with the document in the file plan.

0006A publication <patcit id="pcit0002" dnum="US20070174031A"><text>US 2007/0174031</text></patcit> discloses a method for taking a policy decision. The policy decision device has access to objects being relatable to each other by relations of one or more relation types. The method comprises receiving a request for the policy decision, the request specifying a first object of the objects and request information, obtaining a policy matching to the request information and being applicable to a second object of the objects, obtaining at ealst one propagation rule associated to the policy, the at least one propagation rule specifying at least one relation type of the one or more relation types, verifying if a relation path exists, the relation path linking the first object and the second object, and consisting of one or more of the relations, verifying if the one or more relations of the relation path are in accordance with at least one of the at least one specified relation type, and if said relation path are in accordance, applying the policy to the first object for taking the policy decision.

0007A publication <patcit id="pcit0003" dnum="US20020088000A"><text>US 2002/0088000</text></patcit> discloses a method for controlling access to image metadata. The method includes associating users who will access the image with roles, and associating the roles with individual metadata elements. In response to receiving a request to access to the metadata by a particular user, the user's role is determined from the request and the user's role is compared to the roles associated with the metadata elements to determined which metadata elements to make available to the user.

0008A publication <patcit id="pcit0004" dnum="US20060010483A"><text>US 2006/0010483</text></patcit> discloses a method for defining role types by association with certain permissible actions. Therefore, a role type can then be bound to nodes of hierarchical tree that represent computer-based resources such as dynamic object spaces. Once bound to a node, instances of that role type are created that will be inherited by hierarchical descendant of that node unless a role type block has been established for the corresponding role type.

0009A publication "Access Control: Policies, Models, and Mechanisms" by Pierangela Samarati and Sabrina de Capitani di Vimercati discloses different access control policies corresponding to different criteria for defining what should and what should not be allowed and to different definitions of what ensuring security means. The publication lists the basic concepts behind access control design and enforcement, and points out different security requirements that may need to be taken into consideration.

0010However, these solutions are not suitable for metadata-based folder hierarchy, as in a dynamic document management system. This is because in the dynamic document management system, the objects are not statically located in the folder structure but their existence in the document space varies according to the circumstance. Therefore, a different kind of an ACL solution is needed for the requirements of the metadata-based document management system.

Summary of the Invention

0011The invention is specified in the appended independent claims.

0012In the following an ACL solution for metadata-based file arrangement is disclosed. The solution approaches the problem from two points of view. At first, access control lists are dynamically formed by means of security components being referred via metadata items of the object. Secondly the solution introduces a model for defining ACL's by means of pseudo-users. This model can be utilized by the security component of the first solution as well.

0013Various aspects of the invention include two methods, an apparatus, a computer system, and two computer readable medium comprising a computer program stored therein, which are characterized by what is stated in the independent claims. Various embodiments of the invention are disclosed in the dependent claims.

0014According to a first aspect, a method for a computer system storing electronic objects being defined by metadata items, comprises deriving access rights from one or more security components originating from respective metadata items of at least one object, and determining the effective access rights for the object by means of the security components.

0015According to a second aspect, an apparatus comprises a processor, a memory including computer program code, the memory and the computer program code configured to, with the processor, cause the apparatus to perform at least the following: to store electronic objects being defined by metadata items, to derive access rights from one or more security components originating from respective metadata items of at least one object, and to determine the effective access rights for the object by means of the security components.

0016According to third aspect, a computer system comprises at least one processor, at least one memory including computer program code, the memory and the computer program code configured to, with said at least one processor, cause the computer system at least to perform: to store electronic objects being defined by metadata items, to derive access rights from one or more security components originating from respective metadata items of at least one object, and to determine the effective access rights for the object by means of the security components.

0017According to fourth aspect, a computer readable medium comprises computer program instructions stored thereon, wherein said instructions, when executed, are for storing electronic objects being defined by metadata items, for deriving access rights from one or more security components originating from respective metadata items of at least one object, and for determining the effective access rights for the object by means of the security components.

0018According to fifth aspect, a method for a computer system storing electronic objects being defined by metadata items, comprises determining access rights for an object by means of one or more pseudo-users.

0019According to sixth aspect, a computer readable medium comprising computer program instructions stored thereon, wherein said instructions, when executed, are for determining access rights for an object by means of one or more pseudo-users.

0020According to an embodiment, an object refers to the object's own access control list, wherein the effective access rights for said object are determined by means of security components as part of the object's own access control list.

0021According to second embodiment, a security component originates directly from the object's metadata item.

0022According to third embodiment, a security component originates indirectly from the object's metadata item.

0023According to fourth embodiment, the security component originates from a metadata item of more than one cascaded object.

0024According to fifth embodiment, the more than one security components are combined, wherein the effective access rights are determined as an intersection of the more than one security components.

0025According to sixth embodiment, more than one security components are combined, wherein the effective access rights are determined according to one of the following rules: one overrides the others, each supplements the effective access right, one restricts the others, one defines the maximum, one defines the minimum rights, or any combination of those.

0026According to sixth embodiment, access rights are defined by means of pseudo-users in said security component.

0027According to sixth embodiment, the persons being allowed to access the document are identified by resolving pseudo-users from the metadata items of the object.

0028According to seventh embodiment, the persons being allowed to access the document are identified by resolving pseudo-users from the metadata items of more than one cascaded object.

0029According to eighth embodiment, the computer system comprises a client and a server.

0030Other embodiments as well as advantages of present solutions are disclosed in the detailed description which follows the description of drawings.

Description of the Drawings

0031In the following, various embodiments of the invention will be described in more detail with reference to the appended drawings, in which <dl id="dl0001"><dt>Fig. 1</dt><dd>shows a simplified example of a document management system;</dd><dt>Fig. 2</dt><dd>shows an example of an object having metadata items and an ACL;</dd><dt>Figs. 3a, 3b</dt><dd>show an example for defining ACL for the object of <figref idref="f0002">Fig. 2</figref>;</dd><dt>Figs. 4a, 4b</dt><dd>show an example for defining ACL for the object of <figref idref="f0002">Fig. 2</figref> by means of two security components;</dd><dt>Fig. 5</dt><dd>shows another example of an object having metadata items and an ACL;</dd><dt>Fig. 6a</dt><dd>shows yet further example for defining ACL for an object; and</dd><dt>Fig. 6b</dt><dd>shows the effective access rights for the object of <figref idref="f0008">Fig. 6a</figref>.</dd></dl>

Detailed Description of the Embodiments

0032In the following, several embodiments of the invention will be described in the context of dynamic document management system. It is to be noticed, however, that the invention is not limited only to such a system. In fact, the different embodiments have applications widely in any metadata based environment (i.e. file arrangement), where security and access rights are expected.

Document management system

0033In this context, the term document management system (DMS) refers to a file arrangement that stores objects that are defined by metadata (i.e. properties). Other terms that are typically used for document management system are content management system (CMS) and data management system. In the present disclosure the term "document management system" is a general term referring also to content and data management systems. Such systems comprise various features for managing electronic documents, e.g. storing, versioning, indexing, searching for and retrieval of documents. It is appreciated that there are both dynamic and static document management systems. The difference between dynamic and static systems is the way they store files. In the static systems files are stored e.g. in a constant treelike hierarchy that defines relationships for folders and documents stored in the tree. In the dynamic systems the files may be given identifications that define their existence in the system. The observed location of the files is not constant, but may vary in a virtual space depending on the situation.

0034Before describing the invention in a more detailed manner, a few terms are defined in order to ease the reading and understanding of the invention. In this disclosure, the term "document" relates to a medium (a file) that has been created by a certain application and that has been associated with metadata. For example, a piece of text created by using the Microsoft Word application is a file. "Metadata" refers to information on a document's properties. For example, a creator of the file or a creation date may represent the metadata. The term "object" refers to a document, and is composed of the content of the object as well as of the metadata of the object. Documents and other metadata defined objects are located statically or virtually in the file arrangement. Virtual location is defined by giving a document location(s) based on its metadata, which then addresses the document into a certain virtual folder depending on the route the document is approached. Therefore the content of each folder depends on the current property values of objects and may vary according to a use case and is thus dynamic.

0035An example of a file arrangement is illustrated in <figref idref="f0001">Figure 1</figref>. This file arrangement is a document management system that comprises a document management server 100 and client devices 101, 102, 103, which are all interconnected. The interconnection can be wired or wireless and it may be substantially always on or it may be disconnected occasionally. The server 100 is configured to store objects (e.g. documents) that can be retrieved by the client devices 101, 102, 103. The server and client devices each typically includes at least one processor and at least one memory (computer readable medium) for storage of at least computer program code for execution by the at least one processor. The client device can be any electronic device capable of computing, such as e.g. a personal computer, a laptop, a mobile device.

0036As an example, in <figref idref="f0001">Fig. 1</figref> document D1 is retrieved by client device 101, whereas document D2 is stored by the client device 103 to the document management server 100. The document management server 100 is configured mainly to store documents, but in use the document management server may have other functions as well, e.g. it controls access rights, registers modifications made to documents and allows connections to other systems. In <figref idref="f0001">Fig. 1</figref>, there are one server. However, in some cases, the computer system may comprise more than one server where the document management system is divided. An electronic document stored in the document management system is an example of an object. Such an object is given metadata items (i.e. property values) e.g. a name of creator, a type of a document, a project which the document belongs to, a security class, a client etc.

0037As was mentioned, the document management system can be dynamic so that the folders are virtual, and the documents are virtually located in the folders depending on the user's viewpoint that builds on top of metadata. The present solution can however be utilized in a file management system statically storing folders that comprises files. Documents can have more than one location in the dynamic document management system but the document as such is the same document throughout the locations. In other words, the document is stored into the document management system only once, but is given multiple locations based on its metadata items. Therefore, term "location" should be interpreted both physical and virtual location depending on the file arrangement to cover both dynamic document management system and file management system. However, in order to utilize the present solution, the objects (e.g. documents, folders) have to be associated with metadata. This means that each e.g. document has a property structure defining at least one piece of metadata (i.e. metadata item) for the document.

0038An example of an object comprising metadata items is illustrated in <figref idref="f0002">Fig. 2</figref>. In here, the object is a document "<nplcit id="ncit0001" npl-type="s"><text>Meeting_minutes.doc" created by Carl Smith</text></nplcit> acting as a secretary of the meeting for project "Summer party". The project manager for this project is Holly Quinn (not shown in <figref idref="f0002">Fig. 2</figref>). It is realized that the object's metadata 200 comprises metadata items for the object, which metadata items define a creator, a project, a type of document, a security class, a client and an id number for the document. Each of these metadata items can be typed (or input by any known method) or selected from a predetermined list of values.

0039It can be seen that the object 200 refers to an ACL 204 that comprises a default component 202 allocating full access right to Carl Smith. It is appreciated that the ACL can be associated with the object by other means also, e.g. by inclusion, by linking, by direct reference, by indirect reference, etc.

Dynamic metadata-driven access control lists

0040Let us turn to <figref idref="f0003">Fig. 3a</figref> where "Meeting_minute.doc" shown in <figref idref="f0002">Fig. 2</figref> is used as an example. In <figref idref="f0003">Fig. 3a</figref> an object comprising metadata items 300 for project "Summer Party" is illustrated. The "Summer Party" project comprises a metadata item for a project manager the value of which is Holly Quinn. Other metadata items define that the party is held on July, 14 in Andorra every odd year. The client of the project is HorseWhisp Inc. It is realized that the project refers to a security component 303 that defines access rights so that read-write-access ("RW") is allocated to Holly Quinn and read-access ("R") is allocated to Summer Party Members. It is appreciated that the security component can be associated with the object (e.g. project) by other means also, e.g. by inclusion, by linking, by direct reference, by indirect reference, etc.

0041According to the present solution, this security component 303 of "Summer party" project defines rights to access any object referring to the "Summer Party" project (i.e. any object having a metadata item defining "Summer Party"), including "Meeting_minute.doc". Therefore, Holly Quinn can read and write "Meeting_minute.doc" and participants of the project "Summer party" can read "Meeting_minute.doc". The access rights originating from a security component of the object's metadata item can be called "propagatable permissions/access rights" because they propagate to the object's own ACL, as shown in <figref idref="f0004">Figure 3b</figref>. The object "Meeting_minute.doc" has a property "Project", the value of which is "Summer party". The "Summer party" project refers to a security component 303 that defines access to objects referring to the said project. Therefore, the ACL 204 of object 200 is fulfilled with the content of the security component 303. As a result of this, the ACL 204 of the object 200 comprises its own default component 202 allocating full access right to Carl Smith and the propagated component 302 allocating read-write access right to Holly Quinn and read access right to Summer Party Members. It is appreciated that this security component is kind of a viral component that can be spread among the objects of the document management system as long as those objects refer to metadata items that further refers to (or is associated by other way to) a security component. It is also appreciated that propagation can be physical or virtual. The difference between these is that in physical propagation the security component is physically copied or transmitted to the ACL of the object before actually evaluating the access rights. On the other hand, in virtual propagation, the security component is dynamically incorporated from the metadata item while the object ACL is being evaluated.

0042<figref idref="f0005">Figure 4a</figref> illustrates the same example as shown in <figref idref="f0002">Figs 2</figref> and <figref idref="f0003 f0004">3</figref>, but provides more information for "Meeting_minute.doc". In <figref idref="f0005">Figure 4a</figref>, an object "Secret" 400 refers to a security component 403 that gives RW rights to an executive team at the most. Because "Meeting_minute.doc" has a property value "Secret", this security class object 400 further defines access rights to the document "Meeting_minute.doc". It is realized (see <figref idref="f0006">Fig. 4b</figref>) that now "Meeting_minute.doc" has an ACL 204 that is defined by object's own default component 202 and by two propagated components: one 302 allocating "RW" to Holly Quinn and "R" to Summer Party Members; and the other 402 allocating RW rights to executive team at the most. The resulted effective access rights for the object can be determined according to predetermined rules comprising instructions on how separate components are disposed to each others.

0043It is to be noticed in this example that any object having a reference to the "Summer party" metadata item can have the access rights according to the security component of that particular project. Similarly, any object having a reference to the "Secret" metadata item can have the access rights according to the security component of that particular security class. However, additionally it is possible to configure by which properties, security components can be propagated to the object's ACL. For example, a project metadata item might be referred by several properties, such as "Customer Project" and "Project for Tracking Purposes", but only the "Customer Project" property would be configured to enable propagation.

0044By the first solution, the access right determination propagates easily throughout the document management system when the originating security component is modified. However, the resulted ACL for the object can be also modified by the user if the propagated components allow the user to do so. For instance, the security component of the "Secret" metadata item might be configured to reject any modification because of its dominantly confidential nature.

0045As mentioned earlier, the effective access rights can be determined according to predetermined rules. For example, in <figref idref="f0005">Figs. 4a</figref>, <figref idref="f0006">4b</figref>, the effective access rights for the document in question can be determined as a partial intersection of the three components within the ACL 204. This means that RW access rights are appointed to Carl Smith or Holly Quinn <i>only if</i> they are also members of the executive team. In such a case, the full control being allocated to Carl Smith is reduced to RW, because the security component of "Secret" defines the maximum rights. Similarly, such Summer Party Members who are also members of Executive Team are given permissions for the object. However, in such a case, the R permission of such Summer Party Members is not broadened to RW. It is worth mentioning that in some cases "Max:Executive Team" may choose not to indicate any particular access rights. In such a situation, the access rights of persons are preserved from other security components, but the maximum set of effective persons are determined according to their membership in the Executive Team.

0046In some cases, the effective access rights can be formed by combining each propagated component being referred whereby each propagated component supplements the complete access rights of the object as in example of <figref idref="f0003">Figs. 3a</figref>, <figref idref="f0004">3b</figref>. It is appreciated that any security component can restrict, supplement, override or define the maximum or the minimum restriction for the other security components or determined according to any combination of those. The nature of the security component depends on the use case and can be specified separately.

0047In the example shown in <figref idref="f0005">Figs. 4a</figref>, <figref idref="f0006">4b</figref>, there are two security components that define the access rights for the document. However, there could be yet more security components for one object. Each security component has its own determining factor. For example, it is possible to set the security component of the security class "Secret" as the dominant security component, which always restricts the other components. On the other hand, it is possible to refer to a metadata item called "note" that has a security component "min:Everyone:R". This may override other security components and give everyone a read access. To overcome any conflict occurring between components, the system may comprise an ACL conflict management policy that can be configured to set priorities to the security components.

0048In addition, it is possible to use any security component originating via indirect metadata item references across several objects. This means that the metadata item of the object does not include any security component by itself but comprises a metadata item that either refers to a security component or comprises yet another metadata item including a security component. Basically, such a chain of security components can be as long as security components can be found along the path across cascaded objects.

0049The idea behind this first solution of the invention is to retrieve security components based on the metadata of the object, and to combine them to automatically define the access rights for the object. However, as was mentioned earlier, sometimes the user may desire to set or modify the resulted access rights of the object manually. In such a simple case, the manually set access rights affect only the object in question and do not propagate any further. On the other hand, if the user wishes to change the content of the security component of e.g. the project, then the ACL of any object referring to that project can be automatically updated accordingly. This automatic update can occur immediately after the security component has been changed, or after a certain time period. In some cases, the automatic update may also be ignored.

0050In this solution the access right settings do not depend on the physical location of the object in the document management system, as in the solutions of related art, but on the ACL composed from security components derived by the means of the metadata of the object. This ACL can then be included in the object's metadata on object level and/or version-specifically.

Metadata-driven access role assignment

0051<figref idref="f0007">Figure 5</figref> illustrates an example of the present solution from another point of view. It is realized that the content of <figref idref="f0007">Fig. 5</figref> resembles the content of <figref idref="f0002">Fig. 2</figref>. However, what is different is that the ACL 502 of object 501 allocates access rights to pseudo-users - "Creator", "Manager" - instead of person identities. The term "pseudo-user" is an attribute that refers to a metadata item representing a user or a user group. This attribute is called "pseudo-user" as long as the user item lacks a value. It can be easily recognized that this kind of solution makes it possible to define ACL even though the object would not have any value for the metadata items in question. For example, Carl Smith will receive full rights at the moment "Carl Smith" is given as a value to "Creator" metadata item. Similarly, Elliot Morris will receive RW access rights at the moment "Elliot Morris" is given as a value to "Manager" metadata item. Because of the present solution, modifications of the values for "Creator" and "Manager" can be automatically resolved into the object's ACL without requiring the user to directly modify the effective access rights in the ACL. If Holly Quinn would take the place of Elliot Morris, the user only has to define "Holly Quinn" as the value of "Manager", and RW rights would automatically be appointed to Holly Quinn.

0052<figref idref="f0008">Figure 6a</figref> illustrates how the solution of <figref idref="f0007">Fig. 5</figref> can be utilized by the first solution (shown in <figref idref="f0002 f0003 f0004 f0005 f0006">Figs 2-4</figref>). In this example, a security component 603 is created. This security component allocates access rights to the pseudo-users e.g. according to notation <i>"ReferringObject.Role:AccessRight</i>"<i>.</i> In <figref idref="f0008">Fig. 6a</figref> the security component 603 defines "ReferringObject.SubcontractorRepresentative:R" refers to a metadata item "subcontractror representative" of the referring (target) document; "ReferringObject.OutsourcingCoordinator:FULL" refers to a metadata item "outsourcing coordinator" of the referring (target) document; and "ReferringObject. Project. ProjectManager:R" refers to a metadata item "project" of the referring (target) document. This security component 603 is related to the outsourcing contract object 600 that defines type for documents.

0053Now, Michael McBoss creates a new document "contract.doc" 601 comprising metadata items. One of the metadata items defines that the type of the document is an "Outsourcing Contract". Also, the document "contract.doc" refers to a project "Rubber Duck Quality Control" 606 having Gary Gantt as its project manager. Michael McBoss sets further metadata items to the document, e.g. Subcontractor Representative is Sammy van Slave and Outsourcing coordinators are Michael McBoss and Kyle Kapitan. It is to be noticed that the object 601 also comprises an ACL 604 having a default component, where - according to the second solution - a pseudo-user "Creator" receives full rights.

0054At the time the metadata items of "contract.doc" have values for outsourcing coordinator and subcontractor representative, the access rights will be emerged. It is to be noticed that the security component 603 may have been created before the object "Contract.doc". Therefore it does not have to pay any attention to identities of persons but it can exist independently. At the time the security component 603 is propagated to any object, it will affect to the access rights of any object whose metadata items can be used in resolving the pseudo-user references.

0055<figref idref="f0009">Figure 6b</figref> now shows the resolved access rights 605 for object 601. As a result of the propagation, Sammy van Slave gets read permission, Michael McBoss gets full rights, Kyle Kapitan also gets full rights and Gary Gantt gets read permission. In practice, the resolving can be performed physically, as shown in <figref idref="f0009">Fig. 6b</figref>, or dynamically (virtually), or by mixing these two extremes.

0056The flexibility of the second solution can be realized from <figref idref="f0008">Figs. 6a</figref> and <figref idref="f0009">6b</figref>. For example, when the project manager changes because Gary Gantt is leaving the company, and Flo C. Hart takes over as Project Manager of Rubber Duck Quality Control, the change is automatically propagated to the "contract.doc", and therefore read access is automatically given to Flo C. Hart instead of Gary Gantt.

IN CONCLUSION

0057In the previous, two types of solutions for metadata-based security model have been disclosed.

0058In the first solution, the access rights for an object are derived from referred metadata items that further refers to a security component comprising information on access rights. In the second solution, the access rights are derived from pseudo-users. The second solution can also be utilized in the first solution, so that the security component comprises notation for pseudo-users and their access rights.

0059In previous, the solutions contain examples where either the security component or the pseudo-user is one step apart from the referring object. However, it possible to have more than one metadata reference levels between the security component and the referring object and/or more than one metadata reference levels between the security component and the pseudo-user.

0060The various embodiments of the invention can be implemented with the help of computer program code that resides in a memory and causes the relevant apparatuses, such as the server and the client device, to carry out the invention. These solutions can be performed in one device only or it can be divided depending on how much data is stored in the client device. In addition, the devices and the system can comprise other devices and operations that enhance their performance. For example, human-machine-interaction can be configured to any stage of the solution, when appropriate. It is obvious that the present invention is not limited solely to the above-presented embodiments, but it can be modified within the scope of the appended claims.