JPH06214862A - Document access method for client/server system - Google Patents

Abstract

PURPOSE:To completely and surely protect security by performing the access control of a document file provided in a server node in the unit of a user and the unit of an area in a document. CONSTITUTION:A server node 101 of a host center in a block A is provided with a document file 102 to be managed at the host center. A server node 103 in a block B is also provided with a document file 104. A user managing table and a document managing table are incorporated in the document file 104, and the access right for each of read, update and print is set in the unit of the user and a prescribed area in the document. When document access requests are received from client nodes 105, 106 and 107, the server node 103 judges whether the user requesting the access can access the area in the document requested with the access or not by collating the user managing table and the document managing table. Other server nodes 108 and 113 are similarly operated as well.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention includes a server node that has a document file and provides services such as reading, updating, and printing of documents, and a user's service request sent to the server node to receive the service. The present invention relates to a document access method in a client / server system composed of client nodes.

[0002]

2. Description of the Related Art Conventionally, in a document editing apparatus such as a word processor, there is an intra-document area access control system which prohibits modification of a part of a document, as described in Japanese Patent Laid-Open No. 243172/1989. . In this method, access rights can be set for each area such as text, graphics, images, and tables that make up a document, and information that cannot be changed by others can be written in a document shared by a plurality of users. The access right check is determined based on the user's password input and the access right flag in the document area so that the specific data cannot be partially written.

[0003]

In the above-mentioned prior art,
Since access control is performed for the writing right of a document, only writing to a specific area by a specific user can be permitted, and writing other than that can be prohibited, but no consideration is given to reading or printing of a document. For this reason, all users can read and print all documents without any restrictions on screen display and printing of documents. This is less problematic to the left when the user who uses it is specified to a certain extent and is limited like a word processor.
There is a problem in providing various services such as reading, updating, and printing of documents to many users in an open system environment like a server system.

An object of the present invention is to allow a client / server system to read, write (update), print, etc., in a document file included in a server node in units of a user and in a predetermined area in a document. It is to prevent unauthorized access by an unauthorized user in an open system environment almost completely and to easily manage security.

[0005]

In order to achieve the above object, the invention of claim 1 is provided with a document file and a server node for providing services such as reading, updating, and printing of documents, and user services. In a client-server system composed of a client node that sends a request to a server node and receives a service, the server node manages an access right for each service to a document file for each user and a document file Having a document management table that manages access rights for each service for each predetermined area, when a user's service request is received from a client node, the user management table and the document management table are compared to provide the service requested by the user. It is characterized by determining whether it is possible .

According to a second aspect of the present invention, the access rights of the user management table and the document management table are divided into a plurality of levels, and the server node responds to the service request of the user by the access right level of the user and the access right level of the user. The service is provided according to the access right level of the area of the document.

According to a third aspect of the present invention, the server node further includes a user management table / access right management table for managing access rights for each user to the user management table, and a predetermined area for the document management table. Having a document management table / access right management table for managing access right for each service, and receiving a service request of the user management table or the document management table of a user from a client node, the user management table / access right management table Alternatively, it is characterized by referring to the document management table / access right management table to determine whether or not a service requested by the user can be provided for the user management table or the document management table.

[0008]

In the user management table and the document management table of the server node, access rights such as reading, writing, and printing are set for each user and each document area. The server node receives the document access request from the client node, compares the document management table with the user management table, and determines whether the service, that is, the user who has requested the access, can access the requested document area. , And returns the result to the client node. As a result, the user can access the area ((read / write / print, etc.) only within the area of the document to which access is permitted. That is, the reading, writing, printing, etc. of the document in the open system environment can be performed. Access control can be realized in document area units and user units.

[0009]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail below with reference to the drawings.

FIG. 1 is a network block diagram of a client / server system showing an embodiment of the present invention. Here, in the area A, there is a host center and the server node 101 is installed. The server node 101 is a mainframe host computer or the like, and has a file 102 relating to documents managed by the host center and a backup file 102B for the file 102.
A server node 103 is installed in the B district and has a document file 104 and a backup file 104B thereof. The server node 103 is a personal computer, a workstation or the like. The server node 103 is connected to the client nodes 105, 106, 107 via a line 124 such as a LAN.
Connected with. Client nodes 105, 10
Reference numerals 6 and 107 are personal computers, workstations and the like.
Similarly, in the C district, the D district, and the B district, the server node 10
8 and 113 have document files 109 and 114 and backup files 109B and 114B, and the client nodes 110 through lines 125 and 126 such as LAN.
112, 115-117, respectively.

The server node 101 in the area A is connected to the server node 103 in the area B by a line 120 to a WAN (public network etc.) to a line 121, and the server nodes 108 and 113 in the areas C and D are the same. On line 120
-WAN (public network) -line 122, line 120-WA
N (public network, etc.) to line 123 are connected to each other. Communication lines are ISDN, DDX-C, DDX-P, dedicated lines, and the like.

The document management of the server node and the operation examples of the user, the client node and the server node will be described in detail below by taking the client / server system in the B area as an example.

FIG. 10 shows a user ID / password management table 1000 on the document file 104 of the B district server node 103. In FIG. 10, the user ID
In the / password management table 1000, user IDs / passwords of all users who can access the document files managed by the server node 103 are registered, and read, update, and print access rights are provided for each user ID / password. It is set at four levels P1 to P4.
For example, P1 is a level at which confidential documents can be accessed, P2
Indicates a level at which a secret document other than the extremely confidential is accessible, P3 at a level at which an external confidential document can be accessed, P4 at a level at which only unregulated documents can be accessed. In addition, the user ID / password management table 1100 contains the user I
The initial registration date and time of the D / password, the registrant, and the latest change date and time and the registrant can be set.

FIG. 11 shows a document access right management table 1 in the document file 104 of the B district server node 103.
100, the access right of the document managed by the server node 103 in the B area is set. In FIG. 11,
For a document, the access right level for reading, updating, and printing can be set for each area such as file unit, page unit, and sentence / figure / section / unit. There are four access right levels, for example, P1 is confidential, P2 is confidential, P3 is confidential, and P4 is unregulated. Further, it is possible to set whether or not to display a handling message (for example, “confidential”, “confidential”, etc.) on the display screen or printed paper. You can also set the owner of documents and files.

FIG. 12 shows an access right management table 1200 of the user ID / password management table on the document file 104 of the B district server node 103. This is the user ID / password management table 10 of FIG.
The access (display, change, print, etc.) rights to 00 are set at four levels for each user ID / password. The right level is, for example, that Q1 can handle a P1 level access right, Q2 can handle a P2 level access right, Q3 can handle a P3 level access right, and Q4 can handle a P4 level access right. this is,
The system administrator on the server node 103 side sets in advance.

FIG. 13 shows an access right management table 1300 of the document access right management table in the document file 104 of the B district server node 103. Access to the document access right management table 1100 of FIG. 11 (display, change, print, etc.). ) The rights are set at four levels. The right level is, for example, Q1 is an access right level equivalent to P1, Q2 is an access right level equivalent to P2, Q3 is an access right level equivalent to P3, Q4 is an access right level equivalent to P4, and the like. This is also set in advance by the system administrator of the server node 103 according to the in-house document handling rule.

Area A, Area C, Area D server node 10
Reference numerals 1, 108 and 113 also have the same user ID / password management table, document access right management table, user ID / password management table access right management table, and document access right management table access right management table as in FIGS. Tables are document files 102 and 10, respectively
Hold on 9,114.

Upon receiving the user's access request from the client nodes 105 to 107, the server node 103 in the B district reads the management tables shown in FIGS. A different instruction to the client node. In the following description, the client node is 105 and the user is user I.
Let D be NW101.

2 to 4 are flowcharts showing operation examples of the user NW 101, the client node 105, and the server nodes 103 and 101 when the user reads a document.

First, when the user NW 101 of the client node 105 reads a document, the user NW 101 turns on the power of the client node 105 (20
1) Start up the initial screen (202). This allows
The client node 105 displays a user ID / password input request message on the screen (203).
When the user NW 101 inputs the own user ID / password (204), the client node 105 immediately inputs the input user ID / password.
3 to 205 (205).

The server node 103 receives the user ID / password and retrieves the user ID / password from the document file 104.
The password management table 1000 (FIG. 10) is read (206), and the user ID / password consistency check is performed (207, 207 '). When the consistency cannot be obtained, the server node 103 transmits a message that the document cannot be accessed with the user ID / password to the client node 105 (208). The client node 105 receives the message from the server node 103 and displays it on the screen (209). On the other hand, when the user ID / password is consistent, the server node 103 stores the user ID / password in the area A host center in order to deal with the case where the target document may be managed by the host center. Server node 101
Send to.

Area A server node 101 is a user ID
When the / password is received (210), the user checks whether the corresponding user ID / password is registered in the document file 102 managed by himself (211 and 212).
Then, the area A server node 101 uses the document file 10
2 is transmitted to the B district server node 103 (212), and if registered, the document file 102 is used to determine whether the user ID / password is an accessible document. Then, the access right management table of the document is read and matched with the already acquired user ID / password management table to create a matching result table (213). Further, the A district server node 101 determines a document accessible by the user based on the matching result table, and transmits the corresponding document list to the B site server node 103 (214). The format of the matching result table and the document list created by the server node 101 is basically the same as that of the matching result table 1 and the document list 1 created by the server node 103 described later.

The area B server node 103 receives the document list from the area A server node 101, reads the document access right management table 1100 (FIG. 11) from the area B document file 104, and acquires the already acquired user ID.
/ Make a match with the password management table 1000 to create a match result table (this is called match result table 1) (215). Further, in consideration of the reception result from the area A server node 101, a document list accessible by the user (referred to as document list 1) is created and transmitted to the client node 105 (216). Matching result table 1 and document list 1
The creation mechanism will be described later with reference to FIGS. 14 and 15.

The client node 105 displays the received document list 1 on the screen (217), and outputs a message prompting the user to input the document name to be accessed (218). When the user inputs the document name (219),
The client node 105 checks whether the input document name exists on the document list 1 (220), and if it exists, issues a transmission request of the corresponding document to the server node 103 (221). The server node 103 reads the corresponding document from the document file 104 (222), and displays a handling message on the document or masks a portion that cannot be displayed on the document based on the created matching result table 1 (223). , Sends the relevant document to the client node 105 (224). The client node 105 displays the received document on the screen (225), and the user starts the document operation (226).

On the other hand, when the document name input by the user does not exist in the document list 1, the client node 105
A message inquiring whether the document is newly created is output (227). When the user inputs YES or NO (228), the client node 105 judges this (229), and if NO (not a newly created document), outputs a message indicating that there is no corresponding document (23).
0). If YES (it is a newly created document), the client node 105 notifies the server node 103 of a new document creation request (231). Server node 103
Upon receiving the request to newly create a document, refers to the matching result table 1 to determine whether the corresponding user can create a new document (232, 233), and sends the determination result to the client node 105 ( 234). The client node 105 judges the reception result (23
5) If a new document cannot be created, a message prompting for the input of another document name or the like is displayed (236). If a new document can be created, the client node 105 displays a new document screen (237), and the user starts inputting a new document (238).

FIG. 5 shows the user NW 101, the client node 105, and the like when the user modifies and stores the document.
6 is a flowchart showing an operation example of server nodes 103 and 101.

When the user modifies and stores the displayed document, in response to the document storage request (302) following the user's document input end (301), the B district client node 105 sends the storage request to the server. It transmits to the node 103 (303). Upon receiving the storage request, the B district server node 103 refers to the created matching result table 1 and determines whether the user can change the document (304, 305), and sends the determination result to the client node 105. It is transmitted (306). Client node 1
05 determines the reception result (307), and if the document cannot be changed (stored), displays on the screen that the document cannot be stored (308).

On the other hand, if the document can be changed, the client node 105 displays a message prompting the user to confirm the storage (309) and confirms the user's storage (310).
In response, the storage request for the document and the document to be stored are transmitted to the server node 103 (311). The server node 103 is
Upon receiving this, the owner of the stored document is determined based on the matching result table 1 (312 and 313), and the owner is A
In the case of the server node 101 of the district host center,
The storage request and the stored document are transmitted to the area A server node 101. On the other hand, Area A server node 101
Checks whether or not there is a change in the part that does not have the right to change, based on the already created matching result table (314,
315). After passing the check, the document is stored (31
7) If the portion without the change right is changed, the portion that cannot be stored and the fact that the portion cannot be stored are transmitted to the B district server node 103 (316).

When the owner of the document to be stored is the B district server node 103 (313), the B district server node 1
03 refers to the matching result table 1 and checks whether or not there is a change in a portion that does not have a change right (318,
319). When it is confirmed that the portion without the change right has not been changed (319), the document is stored (321).
If the portion without the right to change is changed, the transmission sentence from the A district server node 101 is also taken into consideration, and the portion which cannot be stored and the fact that it cannot be stored are transmitted to the client node 105 (320). The client node 105 screen-outputs the received unstorable part and the message stating that it cannot be stored (322).

FIG. 6 is a flowchart showing an operation example of the user NW 101, the client node 105, and the server node 103 when the user prints a document.

When the user NW 101 prints a document, the user selects a document name to print from the document list 1 accessible by the user and inputs a print request (401), B
The district client node 105 transmits a print request to the server node 103 (402). The B district server node 103 refers to the matching result table 1 and determines whether the relevant user can print the relevant document (403, 40).
4), the determination result is transmitted to the client node 105 (405). Based on this determination result, the client node 105 outputs a message to the effect that printing cannot be performed on the screen if the user does not have the print right (406).

On the other hand, if the user has the print right, the client node 105 issues a message prompting the input of the print destination printer (407), receives the printer name input (408) from the user, and sends the designated printer name to the server. It is transmitted to the node 103 (409). Server node 10
3 confirms that the corresponding printer can output (410), refers again to the result table 1 collated, masks the handling message and the unprintable portion (411), and prints the print document to the client node. 105
(412). The client node 105
When the print document is received from the server node 103, a message prompting the user to confirm the print is displayed (413),
Upon receipt of a print confirmation input from the user (414), printing is performed (415).

The matching result table 1 and the document list 1 created / referenced by the server node 103 when the user NW 101 reads / changes (updates) / prints a document will be described with reference to FIGS. 14 and 15. .

FIG. 14 shows an example of the matching result table 1. This is the user ID of the document file 104 in FIG. 10 when the B district server node 103 receives the first document access request from the client node 105.
/ The password management table 1000 and the document access right management table 1100 of FIG. 11 are read, these two tables are compared, the level of the right level is compared, and access is enabled / disabled. The matching result table 1 is held in the server node 103 until the processing of the corresponding user NW 101 ends. The right level is
It is assumed that P1, P2, P3, and P4 are higher in this order, and in the high-low comparison, access is possible when the user's right level ≧ document right level, and inaccessible when user right level <document right level. For example, user NW101
1 is P1 and the reading right level in FIG. 1 is P2, the user NW101 does not have the reading right in FIG. 1 on the LAN / CD1051 page. On the other hand, LAN / CD1052
If the page read right level is P2, P2 = P2, and thus the user NW 101 can read the LAN / CD1052 page. Similarly, it is determined whether access is possible or not. Also, regarding handling display and handling printing,
Considering the handling message and masking of areas that cannot be displayed / printed from the document access right management table 1100,
6 illustrates a layout during screen display / printing.

FIG. 15 shows a document list 1 accessible by the user.
Is. Here, the B district server node 103 is shown in FIG.
A user NW101 created for transmission to the client node 105 based on the matching result table 1
Shows a list of documents that can be accessed by. This is displayed on the screen of the client node 105, and the user NW10
1 selects a document to be read, written or printed from among these.

Next, an operation when the user accesses (displays, changes, prints) the user ID / password management table (user ID / password right list) will be described.

In FIG. 7, the user NW 101 has the user ID /
11 is a flowchart showing an operation example of the user NW101, the client node 105, and the server nodes 103, 101 when displaying a list of password management tables (FIG. 10).

When the user NW 101 displays a list of the user ID / password management table, the user NW 10
1 to request display of user ID / password right list (5
01), the client node 105 of B district
Is the user ID / password of the user and the user I
A D / password right list display request is transmitted to the B district server node 103 (502). The server node 103 is
When the request is received from the client node 105, the access right management table 1200 (FIG. 12) of the user ID / password management table in the document file 104 is read and the matching result table 2 is created (504), and the client node 105 is also read. The user ID / password received from is transmitted to the area A server node 103 (503). The area A server node 101 reads the user ID / password management table in the document file 102, and searches whether the user ID / password transmitted from the area B server node 103 is registered (505, 505 '). If it is not registered, the fact that it is not registered in the A district server node 101 is transmitted to the B district server node 103 (506). If registered, the area A server node 101 will access the access right management table (FIG. 12) of the user ID / password management table.
The same table) is read, and the right level of the relevant user and other users are matched, and a matching result table is created (507). Further, referring to this matching result table, a user ID right list accessible by the corresponding user is created and transmitted to the B district server node 103 (508). The B district server node 103 creates a user ID right list 2 that can be accessed by the corresponding user based on the created matching result table 2 and the user ID right list received from the A district server node 101, and the client node It is transmitted to 105 (509).
The client node 105 displays the received user ID right list on the screen (510).

The matching result table 2 and the user ID right list 2 created by the B district server node 103
The mechanism of creation will be described later with reference to FIGS. 16 and 17. Further, a detailed explanation of the matching result table and the user ID right list created by the A district server node 101 is omitted, but the creating method is the same as that of the B district server node 103.

FIG. 8 shows that the user NW 101 has the user ID /
11 is a flowchart showing an operation example of the user NW101, the client node 105, and the server node 103 when changing the password management table (FIG. 10).

User I whose user NW 101 is displaying the screen
When changing the D / password management table (user ID right list), after the input from the user NW 101 is completed (6
01), when the request for changing the user ID right list (602) is received, the B area client node 105 receives the user NW.
The user ID / password of 101 and the change request are transmitted to the B district server node 103 (603). The B district server node 103 uses the already created matching result table 2
Based on (FIG. 16), it is determined whether the user has the right to change (604, 604 '). If the user does not have the right to change, the server node 103 sends a message to the effect that it cannot be changed to the client node 105 (605),
A message indicating that the client node 105 cannot be changed is displayed on the screen (606). If the user has change rights,
The server node 103 transmits a message to the effect that it can be changed and a transmission request for a list to be changed to the client node 105 (607). When the client node 105 transmits the list to be changed (608), the server node 103
Based on the matchmaking result table 2 (FIG. 16), check whether or not there is a change in the part that has no right to change (609,
609 '), if a portion without the change right is changed, a message indicating that there is an unchangeable portion and the portion are transmitted to the client node 105 (610),
The client node 105 displays this on the screen (61
1). When it is confirmed that all the changed parts have the right to change, the B district server node 103 becomes the client node 1
To 05, a change confirmation request is transmitted (612), and the client node 105 displays on the screen a message prompting the user to confirm the change (613). When the user inputs a change confirmation (614), the client node 105 transmits it to the server node 103 (615), and the server node 103 updates the user ID / password management table (616).

In FIG. 9, the user NW 101 has the user ID /
11 is a flowchart showing an operation example of the user NW 101, the client node 105, and the server node 103 when printing the password management table (FIG. 10).

When the user NW 101 prints the user ID / password management table (user ID right list), upon receiving a print request (701) from the user, the client node 105 sends the user ID / password and print request to the B area server node. It transmits to 103 (702).
The B district server node 103 determines whether or not the user has the printing right based on the created result table 2 (FIG. 16) (703, 703 ').
Client node 10 displays a message that it cannot print.
5 (704), and the client node 105 displays this on the screen (705). When the user has the print right, the client node 103 transmits a message indicating that printing is possible to the client node 105 (706), and the client node 105 displays a message prompting the user to input the print destination printer name (707). Upon receiving the printer name input (708) from the user, the client node 105 transmits it to the server node 103 (709). The server node 103 confirms whether the specified printer can output (710), creates a print document by referring to the created matching result table 2 (FIG. 16), and sends it to the client node 105 (71).
1). The client node 105 is the server node 10
The print document from # 3 is received, and a message prompting the user to confirm printing is displayed (712). When the user confirms printing (713), the client node 105 performs printing (714).

Next, the details of the matching result table 2 and the user ID right list 2 and the method of creating them will be described with reference to FIGS.

FIG. 16 shows an example of the matching result table 2. This is the B area server node 103 when accessing the user ID / password management table.
Of the user ID / password management table on the document file 104 (see FIG. 1).
2) is read, the corresponding user ID / password right and other user ID / password right are matched, the level of the right level is compared, and access is enabled / disabled. This matching result table 2 shows the corresponding user NW.
It is held in the server node 103 until the processing of 101 is completed. The right level increases in the order of Q1, Q2, Q3, and Q4. In the comparison of high and low, when the right level of the corresponding user ≧ access partner right level, access is possible, and when the corresponding user right level <other user right level, access It is impossible. For example, assuming that the display right of the user ID / password management table of the user NW101 is Q2 and the display right of the user OP110 is Q1, Q2 <Q1.
W101 cannot display the right of the user OP101 on the user ID / password management table. On the other hand, the change right of the user NW101 is Q2, while the change right of the user NW101 is user B.
Assuming that the change right of S320 is Q3, Q2> Q3
Therefore, the user NW 101 can change the access right of the user BS 320 on the user ID / password management table. Similarly, it is possible to determine whether access is possible or not.

FIG. 17 shows an example of the user ID right list 2. This is a table created by the server node 103 in response to the user ID / password right list display request from the user NW 101 based on the matching result table 2 in FIG. From FIG. 16, the user NW101
17 cannot display / change / print the access right list of the user OP110. Therefore, in FIG.
A user ID right list of user ID / password management tables of the user NW 101 other than 10, the user BS 320, the user BS 320, and the user OA 510 is displayed. The server node 103 transmits the user ID right list 2 of FIG. 17 to the client node 105 and displays it on the screen of the client node 105. The user NW 101 will access the users in the user ID / password management table shown in this list.

When the user accesses (displays / changes / prints) the document access right management table 1100 of FIG. 11, the operation of the user / client node / server node is basically that the user reads / updates / prints the document. It is similar to the case. However, the server node is the user and document access right management table 1 of FIGS. 12 and 13.
200 and 1300 are associated with each other to create a matching result table or list as shown in FIGS.

[0048]

According to the first aspect of the invention, in a network system composed of a server node and a client node, the server node responds to a document access from a plurality of users and a plurality of client nodes, and the server node is a user unit and a document area unit. By managing the access right and allowing the specific user to read, print, and write the specific data, it is possible to prevent the unauthorized access by the unauthorized user and easily realize the security management.

According to the second aspect of the invention, the server node manages the access right by assigning a level to each user and each document area, so that the access right level of the user is high or the access right level is high. It is possible to read, update, print, etc., while permitting access only to high places and automatically excluding inaccessible document areas.

Further, according to the invention of claim 3, the server node has an access right management table of a user right list and an access right management table of a file right list, and in the access right management table of the user right list, the user ID / Set the access right of the password management table to User I
By setting and managing for each D, and managing the access right of the access right management table of the file in the access right management table of the file authority list for each user ID and for each file or sentence, figure, clause, It is possible to prevent unauthorized access to the management table by an unauthorized user.

[Brief description of drawings]

FIG. 1 is a network block diagram of a client / server system showing an embodiment of the present invention.

FIG. 2 is a flowchart showing an operation example of a user, a client node, and a server node when a user reads a document.

FIG. 3 is a continuation of the flowchart of FIG.

FIG. 4 is a continuation of the flowchart of FIG.

FIG. 5 is a flowchart showing an operation example of a user, a client node, and a server node when a user changes a document.

FIG. 6 is a flowchart illustrating an operation example of a user, a client node, and a server node when a user prints a document.

FIG. 7 is a flowchart showing an operation example of a user, a client node, and a server node when a user displays a user ID / password management table.

FIG. 8 is a flowchart showing an operation example of a user, a client node, and a server node when the user changes the user ID / password management table.

FIG. 9 is a flowchart showing an operation example of a user, a client node, and a server node when a user prints a user ID / password management table.

FIG. 10 is an example of a user ID / password management table held by a server node.

FIG. 11 is an example of a document access right management table held by a server node.

FIG. 12 is an example of an access right management table of a user ID / password management table possessed by a server node.

FIG. 13 is an example of an access right management table of a document access right management table held by a server node.

14 is a table showing a matching result of the user ID / password management table of FIG. 10 and the document access right management table of FIG. 11.

FIG. 15 is an example of a document list table displayed on the screen of a client node that a specific user can access.

16 is an example of a table showing a matching result of the own user and another user in the access right management table of the user ID / password management table of FIG.

FIG. 17 is an example of a user ID right list that can be accessed by a specific user displayed on the screen of the client node.

[Explanation of symbols]

101, 103, 108, 113 server nodes 105, 106, 107, 110, 111, 112, 1
15, 116, 117 client node 102, 104, 109, 114 file 102B, 104B, 109B, 114B backup file 120, 121, 122, 123 communication line 1000 user ID / password management table 1100 document access right management table 1200 user Access right management table of ID password management table 1300 Access right management table of document access right management table

Claims (3)

[Claims] 1. A document file is provided for reading a document,
A document access method in a client / server system comprising a server node that provides services such as update and print, and a client node that sends a user service request to the server node and receives the service, wherein the server node It has a user management table for managing service-specific access rights to document files for each user and a document management table for managing service-specific access rights for each predetermined area of a document file, and receives user service requests from client nodes. Then, the user management table and the document management table are matched,
A document access method characterized by determining whether a service requested by the user can be provided. 2. The access right to the user management table and the document management table is divided into a plurality of levels, and the server node responds to a service request from a user.
2. The document access method according to claim 1, wherein the service is provided according to the access right level of the user and the access right level of the area of the document. 3. The server node includes a user management table / access right management table for managing access rights for each user to the user management table for each service, and an access right for each service for each predetermined area to the document management table. When a user has a document management table / access right management table for managing rights and receives a service request of the user management table or the document management table of a user from a client node, the user management table / access right management table or the document management table 3. The document access method according to claim 1, wherein it is determined whether a service requested by the user can be provided for the user management table or the document management table by referring to the access right management table.