JP2005275759A - Electronic document management system, user attribute management device, electronic document management device, electronic document management method and electronic document management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To perform access control in each XML element even when a user attribute or the XML element of an access control object is added, deleted or changed. <P>SOLUTION: A client 1 sends a request to an XML document management server 2. The XML document management server 2 retrieves whether the XML element of the control object is present in the requested XML document or not, acquires a control object URI, and inquires of a user attribute management server 4 whether may display the XML element of the control object or not. The user attribute management server 4 returns OK to the XML document management server 2 when a user ID is included in an attribute permitted to the inquired authority object URI, and returns NG when not included. The XML document management server 2 acquires a requested XML document, deletes the non-permitted XML document, and returns it to the client 1. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to an electronic document management system, a user attribute management device, an electronic document management device, an electronic document management method, and an electronic document management program.

  In recent years, XML (eXtensible Markup Language) has been attracting attention as a successor language of HTML (Hypertext Markup Language), which is a description language for Web pages on the Internet, and electronic documents described in XML are provided to clients via a network. Service is known. XML is characterized in that a user can define attribute information and logical structure of data using a unique tag.

  2. Description of the Related Art Conventionally, a server that controls information that provides the above-described electronic document according to the access authority of a client uses a CGI (Common Gateway Interface) based on information such as a URL (Uniform Resource Locators) and a user ID included in a request from the client. ) Etc., XML documents were acquired / analyzed and processed / edited. However, such server-side program development requires specialized knowledge such as servers and CGI. Therefore, when the configuration of XML tags changes or when XML tags to be controlled are added or deleted, the changes must be reflected in the XML analysis part of the CGI program, and the development costs can be ignored. It wasn't. For this reason, in the prior art, it is necessary to modify an application when an XML element or user attribute for performing access control is added / deleted / changed.

Therefore, in order to control whether or not to provide information to the requester of information, the requester classification information for recognizing the requester and classifying a plurality of requesters is used to determine whether or not to provide information to the requester. There is a technology for reading out access control information to be controlled for each part of the information, controlling whether to provide the information for each part of the information based on the access control information, and providing the information to the request source (for example, Patent Documents) 1).
JP 2001-331373 A

  However, since the above-described prior art (Patent Document 1) is a method of writing access control information into an electronic document itself such as HTML or XML, the control tag is changed or the policy is changed. In some cases, it is necessary to correct the electronic document. The editing of the control information on the electronic document has a risk of erroneously correcting the electronic document itself. As described above, the prior art has a risk of erasing the electronic document itself, and there is a problem that management becomes difficult when there are many users or when the amount of electronic documents is large.

  The present invention has been made in consideration of such circumstances, and its purpose is to perform access control for each XML element even when an XML element or user attribute subject to access control is added, deleted, or changed. To provide an electronic document management system, a user attribute management device, an electronic document management device, an electronic document management method, and an electronic document management program that can be made possible.

  The present invention has been made to solve the above-described problems. The present invention is a document management system that provides an electronic document in response to a request from a client. Access restriction information storage means for storing restriction information indicating whether access is possible, and whether a component of an electronic document requested by a user of the client is accessible based on a request from the client. Authority confirmation means for confirming based on the restriction information in the access authority information storage means, acquisition means for obtaining an electronic document corresponding to the request from the client, and the acquisition means based on the confirmation result by the authority confirmation means Document processing means for deleting inaccessible components among the components of the electronic document acquired by Characterized by comprising a providing means for providing an electronic document which is processed by the document processing unit to the client.

  Further, the present invention provides the electronic document management system according to claim 1, wherein the access restriction information storage means stores restriction information for each hierarchical structure when the constituent elements of the electronic document have a hierarchical structure. It is characterized by doing.

  The present invention also provides an access restriction information storage unit that stores restriction information indicating which users can access each component of the electronic document, and a component of the electronic document requested by the user of the client. And authority confirmation means for confirming whether access is possible based on restriction information in the access authority information storage means.

  In addition, the present invention provides a document management apparatus that provides an electronic document in response to a request from a client, an acquisition unit that acquires an electronic document corresponding to the request from the client, and an electronic device requested by the client. A document processing means for deleting an inaccessible constituent element among the constituent elements of the electronic document acquired by the acquiring means based on whether or not the constituent element of the document is accessible to the user of the client; Providing means for providing the client with an electronic document processed by the document processing means.

  The present invention also provides a document management method for providing an electronic document in response to a request from a client, and stores restriction information indicating which users can access each component of the electronic document. In addition, based on the request from the client, it is confirmed based on the restriction information whether the component of the electronic document requested by the user of the client is accessible, and corresponds to the request from the client. Acquiring an electronic document, deleting an inaccessible component among the components of the acquired electronic document based on the confirmation result, and providing the processed electronic document to the client To do.

  In addition, according to the present invention, which user can access each component of the electronic document, the step of receiving a request from the client and whether the component of the electronic document requested by the user of the client can be accessed. A step of confirming based on restriction information indicating whether or not, a step of obtaining an electronic document corresponding to a request from the client, and based on the confirmation result, among the components of the obtained electronic document, The step of deleting an inaccessible component and the step of providing the processed electronic document to the client are executed by a computer.

As described above, according to the present invention, for each component of the electronic document, restriction information indicating which users can access is stored in the access restriction information storage means, and the authority confirmation means The electronic document requested by the client user can be accessed based on the restriction information stored in the access authority information storage unit, and the document processing unit can check whether the component is accessible based on the confirmation result by the authority confirmation unit. The inaccessible components are deleted from the components of the electronic document acquired by the acquiring unit, and the electronic document processed by the document processing unit is provided to the client by the providing unit.
Therefore, even when an access control target XML element or user attribute is added / deleted / changed, an access control for each XML element can be achieved.

Further, according to the present invention, when the constituent elements of the electronic document have a hierarchical structure, the access restriction information storage unit stores restriction information for each hierarchical structure.
Therefore, even when an access control target XML element or user attribute is added / deleted / changed, an access control can be performed for each XML element and hierarchical structure.

Further, according to the present invention, for each component of the electronic document, restriction information indicating which users can access is stored in the access restriction information storage means, and the authority confirmation means stores the client user. Is checked based on the restriction information stored in the access right information storage means.
Therefore, even when an access control target XML element or user attribute is added / deleted / changed, an access control can be performed for each XML element and hierarchical structure.

Further, according to the present invention, an electronic document corresponding to a request from a client is acquired by the acquisition unit, and a component of the electronic document requested by the client is accessible to the user of the client by the document processing unit. Based on whether or not there is, an inaccessible component is deleted from each component of the acquired electronic document, and the processed electronic document is provided to the client by the providing means.
Therefore, even when an access control target XML element or user attribute is added / deleted / changed, an access control can be performed for each XML element and hierarchical structure.

Further, according to the present invention, for each component of the electronic document, restriction information indicating which users can access is stored, and based on a request from the client, the user of the client Based on the restriction information, whether the constituent element of the requested electronic document is accessible is obtained, an electronic document corresponding to the request from the client is obtained, and the obtained electronic document is obtained based on the confirmation result. Among the components, the inaccessible components are deleted, and the processed electronic document is provided to the client.
Therefore, even when an access control target XML element or user attribute is added / deleted / changed, an access control can be performed for each XML element and hierarchical structure.

Further, according to the present invention, which user can access for each component of the electronic document, the step of receiving the request from the client and whether the component of the electronic document requested by the user of the client is accessible A step of confirming based on restriction information indicating whether or not, a step of acquiring an electronic document corresponding to a request from the client, and a step of acquiring each component of the acquired electronic document based on the confirmation result Of these, the computer is caused to execute a step of deleting inaccessible components and a step of providing the processed electronic document to the client.
Therefore, even when an access control target XML element or user attribute is added / deleted / changed, an access control can be performed for each XML element and hierarchical structure.

  Hereinafter, the best mode for carrying out the present invention will be described.

A. Embodiment A-1. Configuration of Embodiment Hereinafter, an embodiment of an XML document management system of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing a schematic configuration of the XML document management system of the present embodiment. In FIG. 1, a client 1 is a personal computer (PC) or server that uses an XML document. The client 1 sends a request to the XML document management server 2 and acquires an XML document as a result.

  The XML document management server 2 searches the XML document control target URI database 3 to determine whether there is a control target XML element in the requested XML document, obtains the control target URI, and sends it to the user attribute management server 4. The user is inquired as to whether or not the user has access authority. If the user does not have access authority, the XML document obtained by removing the XML element subject to access control from the requested XML document is transmitted to the client 1. If there is no access control target XML element or if the user has access authority for all control target URIs, the requested XML document is transmitted to the client 1 as it is. The XML document control target URI database 3 stores the URL of the XML document and the control target URI in association with each other.

  The user attribute management server 4 manages the access control target XML element and accessible user attribute information by the user attribute database 5. The user attribute database 5 stores restriction target URIs and user attributes in association with each other. The user attribute is information that associates a user ID with a role name. The role name is an attribute that designates a range of users to be controlled, and corresponds to, for example, a department or job title in a company. This is information indicating whether the user can access the element to be controlled by associating the control target URI with the user attribute.

  In the present embodiment, as shown in FIG. 1, a plurality of XML document management servers 2 may be provided in the XML document browsing system.

A-2. Detailed Configuration Next, FIG. 2 is a block diagram showing a detailed configuration of the XML document management server 2 and the user attribute management server 4. The XML document management server 2 includes a control unit 2-1, an authority inquiry unit 2-2, an XML document acquisition unit 2-3, an XML document processing unit 2-4, an XML document control target URI database 3, and an XML document database 2-5. Consists of. The control unit 2-1 receives the request from the client 1, calls the authority inquiry unit 2-2, the XML document acquisition unit 2-3, and the XML document processing unit 2-4 and finally transmits the XML document to the client 1. .

  The authority inquiry unit 2-2 searches the XML document control target URI database 3 from the XML document URL requested from the client 1 to obtain the control target URI, and displays whether the control target XML element may be displayed. The user attribute management server 4 is inquired, and an inquiry result from the user attribute management server 4 (that is, referenceable / impossible for each control target URI) is returned to the control unit 2-1.

  The XML document acquisition unit 2-3 acquires the requested XML document from the XML text database 2-5 (may be from the network). The XML document processing unit 2-4 deletes an XML element that is not permitted to be accessed by the user from the XML document acquired by the XML document acquisition unit 2-3.

  The user attribute management server 4 includes an authority confirmation unit 4-1 and a user attribute database 5. The authority confirmation unit 4-1 confirms whether the corresponding user can access the element to be controlled according to the attribute information in the user attribute database 5.

  Next, FIG. 3 is a conceptual diagram showing an example of URLs of the XML document management server 2 and the user attribute management server 4. In the illustrated example, the URL of the user attribute management server 4 is “http://www.usermanager.com/”, and the URL of the XML document management server 2 is “http://www.xmlserver.com/”. And

  Next, FIG. 4 is a conceptual diagram showing a correspondence example between the request URL of the XML document and the control target URI. In the illustrated example, for the request URL “http://www.xmlserver.com/a.xml”, the control target URI “http://www.xmlserver.com/a.xml/personal information list / personal information "Basic salary" is associated with the URI to be controlled "http://www.xmlserver.com/a.xml/Personal information list / Personal information @ {name = '% ID'} / Basic salary". In this example, two control target URIs are set for one request URL, but a plurality of request URLs can be set.

  Next, FIG. 5 and FIG. 6 are conceptual diagrams showing examples of user attributes and authority information indicated by the control target URI, which are stored on the user attribute management server 4. In the example shown in the figure, the control target URI “http://www.xmlserver.com/a.xml/personal information list / personal information / basic salary” has a role name “any”, can be referred to / cannot be “not allowed”, is controlled. In the target URI “http://www.xmlserver.com/a.xml/personal information list / personal information / basic salary”, the role name “general affairs”, referable / impossible “permitted”, control target URI “http: / /www.xmlserver.com/a.xml/Personal information list / Personal information @ {name = '% ID'} / Basic salary ”is associated with the role name“ general ”and referable / impossible“ possible ” Yes. Also, the role name and the user ID are associated with each other. In the illustrated example, the role name “general” is associated with the user ID “Taro Yamada”, and the role name “general affairs” is associated with the user ID “Taro Tanaka”. Yes. (Because Taro Yamada is described first in the following explanation)

  Here, the role name is an attribute that specifies a range of users to be controlled. That is, the role name “any” is controlled by all users, the role name “general” is, for example, a user who belongs to a general office in the company, and the role name “general affairs” is, for example, belonging to the general affairs department in the company Become a user.

  A case where the XML document has a hierarchical structure will be described. For example, if the URI to be controlled is set as "http://www.xmlserver.com/a.xml/personal information list / personal information @ {name = '% ID'} / basic salary / professional salary" For a user whose name matches the user ID,

<Basic salary>
<Professional salary> ○○○ </ Professional salary>
<Age salary> ××× </ age salary>
</ Basic salary>

Among the XML documents described as above, the content (here, “XXX”) described in the XML element of <professional salary> is the control target. The age salary is not designated as a control target because it is not specified in the control target URI even in the same hierarchy.
For example, if the control target URI is set as "http://www.xmlserver.com/a.xml/personal information list / personal information @ {name = '% ID'} / basic salary", the name For the user whose ID matches the user ID, the professional salary and age class enclosed by <professional salary> and </ professional salary> are controlled.
If the control target URI is set as, for example, “http://www.xmlserver.com/a.xml/personal information list / personal information / basic salary”, <professional salary> and </ Function salary and age class enclosed by “Professional salary> are subject to control.

B. Operation of Embodiment Next, the operation of the XML document management system of the present embodiment will be described with reference to FIG. First, the client 1 sends a request to the XML document management server 2 (S1). At this time, the URL of the XML document and the user ID are transmitted.

  Next, the XML document management server 2 searches whether there is an XML element to be controlled in the requested XML document, and acquires a control object URI (S2). The XML document management server 2 inquires of the user attribute management server 4 (http://www.usermanager.com/) whether or not the XML element to be controlled may be displayed in order to inquire about the XML element display (S3). . At this time, all control target URIs and user IDs included in the requested XML document are sent out.

  As a result of the inquiry, the user attribute management server 4 determines whether the user can access the control target URI from the role to which the inquired control target URI and user ID belong. If the access to the XML document management server 2 is OK and the access is impossible, NG is returned (S4). At this time, all requested URI results are returned simultaneously.

  The XML document management server 2 acquires the requested XML document from the file system, database, or other application (S5). Next, the XML document management server 2 processes the XML document based on the inquiry result (S6). When the inquiry result is NG, the XML element to be controlled is deleted. Then, the XML document management server 2 returns the requested XML document to the client 1 (S7).

B-1. Example 1
For example, a case where a user whose name is “Taro Yamada” accesses is described. It is assumed that the XML document management server 2 stores the XML text shown in FIG. 7 as a.xml. In this case, the client 1 transmits the URL “http://www.xmlserver.com/a.xml?ID=“Taro Yamada” ”as a request. In response to the above request, the XML document management server 2 uses the request URL (http://www.xmlserver.com/a.xml) as key information and the authority target URI “http://www.xmlserver.com/a .xml / personal information list / personal information / basic salary ”,“ http://www.xmlserver.com/a.xml/personal information list / personal information @ {name = '% ID'} / basic salary ”( (See FIG. 4).

  Next, the XML document management server 2 sends “http://www.xmlserver.com/a.xml/” as a control target URI to the user attribute management server 4 (http://www.usermanager.com/). Personal information list / personal information / basic salary ”,“ http://www.xmlserver.com/a.xml/personal information list / personal information @ {name = '% ID'} / basic salary ”and user ID“ Taro Yamada ".

  In the user attribute management server 4, since the role name of the user ID “Taro Yamada” is “general” (see FIG. 6), the evaluation shown for “Taro Yamada” is the control shown in FIG. Among the target URIs are the first and third lines. First, the first line (impossible) is evaluated, and all <basic salary> portions are NG. Next, the third line (possible) is evaluated and <basic salary> is OK only for one's part.

  Next, the XML document management server 2 acquires the XML document shown in FIG. In the above-described example, the basic salary information element of “Taro Yamada” is “can be referred to” and is left as it is, while the basic salary elements other than “Taro Yamada” (that is, Taro Tanaka and Taro Suzuki) are “not referable”. Therefore, the basic salary information elements other than “Taro Yamada” are deleted. As a result, the processed XML document is as shown in FIG. Therefore, the XML document shown in FIG. 8 is returned to the client 1.

B-2. Example 2
Next, a case where a user whose name is “Taro Tanaka” accesses will be described. In this case, the client 1 transmits the URL “http://www.xmlserver.com/a.xml?ID=“Taro Tanaka” ”as a request. In response to the above request, the XML document management server 2 uses the request URL (http://www.xmlserver.com/a.xml) as key information and the authority target URI “http://www.xmlserver.com/a .xml / personal information list / personal information / basic salary ”,“ http://www.xmlserver.com/a.xml/personal information list / personal information @ {name = '% ID'} / basic salary ”( (See FIG. 4).

  Next, the XML document management server 2 sends “http://www.xmlserver.com/a.xml/” as the authority target URI to the user attribute management server 4 (http://www.usermanager.com/). Personal information list / personal information / basic salary ”,“ http://www.xmlserver.com/a.xml/personal information list / personal information @ {name = '% ID'} / basic salary ”and user ID“ Taro Tanaka ".

  Since the user ID “Taro Tanaka” has the role name “General Affairs” (see FIG. 6), the user attribute management server 4 is evaluated for “Taro Tanaka” as shown in FIG. Among the controlled URIs, the first and second lines. First, the first line (impossible) is evaluated, and all <basic salary> portions are NG. Next, the second line (possible) is evaluated, and all <basic salary> portions are OK.

  Next, the XML document management server 2 acquires the XML document shown in FIG. In the acquired XML document, elements that are not permitted are deleted. In this case, since all the basic pay elements can be referred to, there are no elements to be deleted. Therefore, the XML document shown in FIG. 9 (that is, the same as FIG. 7) is returned to the client 1.

B-3. Example 3
Next, a case where a user whose name is “Taro Suzuki” accesses will be described. In this case, the client 1 transmits the URL “http://www.xmlserver.com/a.xml?ID=“Taro Suzuki” ”as a request. In response to the above request, the XML document management server 2 uses the request URL (http://www.xmlserver.com/a.xml) as key information and the authority target URI “http://www.xmlserver.com/a .xml / personal information list / personal information / basic salary ”,“ http://www.xmlserver.com/a.xml/personal information list / personal information @ {name = '% ID'} / basic salary ”( (See FIG. 4).

  Next, the XML document management server 2 sends “http://www.xmlserver.com/a.xml/” as the authority target URI to the user attribute management server 4 (http://www.usermanager.com/). Personal information list / personal information / basic salary ”,“ http://www.xmlserver.com/a.xml/personal information list / personal information @ {name = '% ID'} / basic salary ”and user ID“ Taro Suzuki ".

  Since the role name of the user ID “Taro Suzuki” is not registered in the user attribute management server 4 (see FIG. 6), what is evaluated for “Taro Suzuki” is the control target shown in FIG. This is only the first line of the URI. Therefore, the first line (impossible) is evaluated, and all <basic salary> portions are NG.

  Next, the XML document management server 2 acquires the XML document shown in FIG. Then, elements that are not permitted are deleted from the acquired XML document. In this case, since all the basic pay elements cannot be referred to, all the basic pay elements are deleted. Therefore, the XML document shown in FIG. 10 is returned to the client 1.

C. Other Embodiments Next, other embodiments of the present invention will be described. FIG. 11 is a block diagram showing a configuration of a traceability system to which an XML document management system according to another embodiment of the present invention is applied. In addition, the same code | symbol is attached | subjected to the part corresponding to FIG. 1 (or FIG. 2), and description is abbreviate | omitted. Traceability is a mechanism for writing and reading information relating to distribution in each distribution process in order to clarify processes such as cultivation, breeding, processing, manufacture, and distribution. Thereby, for example, it becomes possible to ensure food safety. Used mainly for logistics management. For example, if this system is applied to a traceability system, when a manufacturer, retailer, or consumer wants to see information about a product, the information that can be viewed according to the respective positions of the manufacturer, retailer, or consumer. It is possible to limit.

  In the figure, the product 20 is provided with RFID (product ID for uniquely identifying the product), and a product ID for identifying the product wirelessly from the reader 13 on the manufacturer side or the reader 15 on the retailer side. To get. Manufacturers and retailers make requests to the PML (Physical Markup Language) document management server 10 via the network 21 in order to view the browsing of product information from the respective servers 12 and 14. The PML document management server 10 corresponds to the XML document management server 2 shown in FIG. 1 (or FIG. 2), and the user responds to a request (browsing of product information) from the manufacturer server 12 or the retailer server 14. The attribute management server 4 is inquired whether the user has access authority. A PML document is an extended version of XML and is basically equivalent. When the user does not have access authority, the PML document management server 10 removes the PML element (product information) that is the access control target from the requested PML document, and then sends it to the manufacturer server 12 or the retailer server 14. return. Thereby, for example, the material of a part with a product can be restricted such that a maker and a retailer can see, but a consumer cannot see.

  The prior art has a function of controlling access to only a specific element of an XML document. However, when an XML element or user attribute for access control is added, deleted, or changed, the application must be corrected. On the other hand, according to the system of the present embodiment, each element of the XML document that is an access control target provided by the XML document management server 2 is specified so as to be identifiable by a newly defined URI (Uniform Resource Identifier). It is possible to set permission / denial of access to user attributes. As a result, even when an access control target XML element or user attribute is added / deleted / changed, it is possible to set (or reset) the URI and the user attribute without modifying the application. The effect that it is possible to control each access is obtained.

  In the above-described embodiment, the XML document management server 2 and the user attribute management server 4 described above are executed in a computer system. A series of processing steps by the XML document management server 2 and the user attribute management server 4 are stored in a computer-readable recording medium in the form of a program, and the computer reads and executes the program. Thus, the above processing is performed. That is, each processing means and processing unit in the XML document management server 2 and the user attribute management server 4 is processed by a central processing unit such as a CPU reading the above program into a main storage device such as a ROM or a RAM. It is realized by executing arithmetic processing.

  Here, the computer-readable recording medium means a magnetic disk, a magneto-optical disk, a CD-ROM, a DVD-ROM, a semiconductor memory, or the like. Alternatively, the computer program may be distributed to the computer via a communication line, and the computer that has received the distribution may execute the program.

It is a block diagram which shows the schematic structure of the XML document browsing system by this embodiment. FIG. 3 is a block diagram showing detailed configurations of an XML document management server 2 and a user attribute management server 4. It is a conceptual diagram which shows an example of URL of the XML document management server 2 and the user attribute management server 4. FIG. It is a conceptual diagram which shows the example of a response | compatibility with request URL and control object URI of an XML document. 4 is a conceptual diagram illustrating an example of a user attribute indicated by a control target URI stored on the user attribute management server 4. FIG. It is a conceptual diagram which shows an example of the authority information stored on the user attribute management server 4. 3 is a schematic diagram illustrating an example of an original XML document stored in a document management server 2. FIG. 6 is a schematic diagram illustrating an XML document returned to the client 1 in Embodiment 1. FIG. In Example 2, it is a schematic diagram which shows the XML document returned to the client. In Example 3, it is a schematic diagram which shows the XML document returned to the client 1. FIG. It is a block diagram which shows the structure of the traceability system to which the XML document management apparatus by other embodiment of this invention is applied.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Client 2 ... XML document management server (acquisition means, document processing means, provision means)
3 ... XML document control target URI database 4 ... User attribute management server (authority confirmation means)
5. User attribute database (access restriction information storage means)
2-1. Control unit (providing means)
2-2 ... Authority inquiry unit 2-3 ... XML document acquisition unit (acquisition means)
2-4 ... XML document processing section (document processing means)
2-5 ... XML document database 4-1 ... Authority confirmation section (authority confirmation means)
10 ... PML document management server (acquiring means, document processing means, providing means)
11 ... Product information PML document database 12, 14 ... Server 13, 15 ... Reader 20 ... Product 21 ... Network

Claims (6)

A document management system that provides an electronic document in response to a request from a client,
Access restriction information storage means for storing restriction information indicating which users can access each component of the electronic document;
Authority confirmation means for confirming whether or not the component of the electronic document requested by the user of the client is accessible based on the request from the client based on the restriction information in the access authority information storage means;
Obtaining means for obtaining an electronic document corresponding to a request from the client;
Document processing means for deleting inaccessible constituent elements among the constituent elements of the electronic document obtained by the obtaining means based on the confirmation result by the authority confirmation means;
An electronic document management system comprising: providing means for providing the client with an electronic document processed by the document processing means. 2. The electronic document management system according to claim 1, wherein, when the constituent elements of the electronic document have a hierarchical structure, the access restriction information storage unit stores restriction information for each hierarchical structure. Access restriction information storage means for storing restriction information indicating which users can access each component of the electronic document;
User attribute management apparatus comprising: authority confirmation means for confirming whether or not a component of an electronic document requested by a user of a client is accessible based on restriction information in the access authority information storage means . A document management device that provides an electronic document in response to a request from a client,
Obtaining means for obtaining an electronic document corresponding to a request from the client;
Based on whether or not the component of the electronic document requested by the client is accessible to the user of the client, the inaccessible component is deleted from the components of the electronic document acquired by the acquisition unit Document processing means,
An electronic document management apparatus comprising: a providing unit that provides the client with an electronic document processed by the document processing unit. A document management method for providing an electronic document in response to a request from a client,
For each component of the electronic document, limit information indicating which users can access is stored,
Based on the request from the client, confirm whether the component of the electronic document requested by the user of the client is accessible based on the restriction information;
Obtaining an electronic document corresponding to the request from the client;
Based on the confirmation result, the inaccessible components are deleted from the components of the acquired electronic document,
An electronic document management method comprising: providing the processed electronic document to the client. Accepting a request from a client;
Checking whether the components of the electronic document requested by the user of the client are accessible based on restriction information indicating which users are accessible for each component of the electronic document;
Obtaining an electronic document corresponding to the request from the client;
Deleting an inaccessible component among the components of the acquired electronic document based on the confirmation result;
An electronic document management program causing a computer to execute the step of providing the processed electronic document to the client.

Images