JP2001101111A - Method for managing user in www hierarchical client- server type system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent illegal double log-in without doubly managing user information by an intranet server and a center server in a three-layer client-server type system or the like and to make it possible to execute log-in again by the same user ID when a web browser is ended without executing log-out. SOLUTION: The center server specifies a user by the cession ID of a client and the URL of an intranet server transmitting the cession ID and manages user's log-in/log-out information or the like. The intranet server periodically checks cession with the client, and when the cession is disconnected, transmits a log-out request to the center server, which executes the automatic log-out of the user concerned.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a WWW (World).
Wide Web) for a user management method in a hierarchical client / server type system.

[0002]

2. Description of the Related Art A conventional WWW client-server system is generally a client-server system on the Internet (including an extranet) or an intranet, as seen in, for example, a WWW-based education support system. It is a target.
The user logs in directly to the server from the client personal computer, and proceeds with the learning using the learning support system and contents provided as CGI. In addition, session management is performed between the client PC and the server to prevent unauthorized double login.

[0003]

The method of directly logging in from the client to the center server increases the overhead as the number of clients increases, which is not desirable from the viewpoint of load distribution. So, for example,
As a three-tier client server configuration of an intranet server-internet server (center server), it is conceivable to reduce the concentration on the center server and distribute the load to the intranet server. In this case, the method of indirectly logging in to the center server from the client PC via the intranet server and managing the login on the center server is that if the web browser is terminated without logging out, re-login with the same user ID Can not. For this purpose, it is necessary to double manage information for associating a user ID with a session ID and login information on the intranet server and the lanter server. In addition, if the user ID or password is used as a key without performing the double login process of the intranet server, if the user enters the login state on the center server, there is a problem that unauthorized use can be made without authentication from other users. I do.

An object of the present invention is to provide a user management method which can easily solve the above-mentioned problems in a client-server system of three or more layers by WWW.

[0005]

In order to achieve the above object, the present invention mainly specifies a user by a session ID of a client and a URL of an intranet server, and performs information management such as login / logout of the user. Characteristics. The automatic logout is performed by disconnecting the client session.

[0006]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below in detail with reference to the drawings. In the present embodiment, WWW
It is assumed that a client-server type education support system using a server and a WWW browser is used.

FIG. 1 is a system configuration showing an embodiment of the present invention configured using a WWW server and a WWW browser. This is because, in an intranet environment, an intranet server manages a plurality of client devices in the intranet environment.
FIG. 2 shows a three-layer client / server configuration for managing each intranet server.

In FIG. 1, reference numerals 11a, 11b, and 11c denote client devices (personal computers) as learning terminals. Reference numeral 12 denotes an intranet server that provides services to the clients 11a, 11b, and 11c, and communicates with the clients 11a, 11b, and 11c via the network 14a. Reference numeral 13 provides services to the intranet server 12, and indirectly outputs the client PCs 11a and 11a.
b, 11c, and communicates with the intranet server 12 via the network 14b. 15a and 15b are routers for connecting networks.

FIG. 2 shows an example of the configuration of the client 11a. The configuration of the clients 11b and 11c is the same.
In FIG. 2, reference numeral 21 denotes a WWW browser, and a student (user) logs in and logs out using the WWW browser 21. Reference numeral 22 denotes a network device that performs communication through a network. 23 is the Internet.

FIG. 3 shows an example of the configuration of the intranet server 12. 31 is a WWW server that executes various processes, 32
Is a magnetic disk device for storing various programs used by the WWW server 31 and a temporary file 32a. 33
a is a session management program for performing session management. 33b is a login request program for making a login request to the center server. A logout request program 33c issues a logout request to the center server.
33d is a student screen generation program for generating a student screen. Reference numeral 34 denotes a network device that performs communication through a network. 35 is the Internet.
Note that the intranet server sends the intranet server 1 to the center server 13 when the WWW server 31 is activated.
A logout request is made for all the students (users) who have logged in from the URL 2.

FIG. 4 shows an example of the configuration of the center server 13.
41 is a WWW server that executes various processes, 42 is a WWW
This is a magnetic disk device that stores various programs and data used by the server 41. 43 is a magnetic disk drive 4
2 is a user management table for managing user information on the user information table 2; 44a is a session management program for performing session management. Reference numeral 44b denotes a login program for performing a login in response to a login request from the intranet server. A logout program 44c performs logout in response to a logout request from the intranet server. 4
Reference numeral 5 denotes a network device that performs communication through a network. 46 is the Internet. When the WWW server 41 is started, the center server 13 performs a logout process for all users on the user management table 43.

FIG. 5 shows an example of the configuration of the user management table 43 in the center server 13. In FIG. 5, 51, 5
.. Are user records, which exist only for all students (users) who receive services in this system. One user record includes a user ID, a password, a session ID (client session ID), a URL (URL of an intranet server), a login date and time, a logout date and time, and other user information. Here, the user ID and the password are registered in advance. The session ID, URL, and login date and time are updated at the time of login, and the logout date and time are updated at the time of logout.

FIG. 6 is a transfer sequence showing a series of processes in login. Hereinafter, the log-in operation of the present system will be described with reference to FIG. FIG. 6 shows the client (1
1a), the processing contents of each of the intranet server 12 and the center server 13, and arrows indicate the exchange of data.

The top page screen 6 of the client 11a
When a login screen request is issued from the client 1, the intranet server 12 transfers the login screen 63 to the client 11a. Further, a session between the WWW browser of the client 11a and the WWW server of the intranet server 12 is established, and a session ID is issued from the session management program 62a on the intranet server 12.

A login screen 63 of the client 11a inputs a user ID and a password on the login screen 63,
Login request to intranet 12 server (user ID
And password).

The login request program 64 on the intranet server 12, which has received the login request from the client 11a, makes a login request (user ID, password, session ID) to the center server 13.
When the login request program 64 is activated, the session management program 62b is activated to acquire a session ID required for a login request from the center server 13.

The login program 65a on the center server 13 that has received the login request from the intranet server 12 refers to the user management table 43 and authenticates the user with the received user ID and password. If the user ID and the password are correct, the corresponding user record in the user management table 43 is updated. The update items are three items of the received session ID, URL, and login date and time. The URL is obtained from an environment variable of the intranet server 12 that has transmitted the login request. When the login is successful, the login program 65 successfully logs into the intra server 12 (session I
D).

In FIG. 6, reference numeral 65b denotes an example of updating a record in the user management table 43. In this example, when a user with a user ID “001” and a password “111” logs in, the client 11
a, the URL of the intranet server 12 is updated to “www.b.com”, the login date and time is updated to the current date and time “19990602120,000”, and the login date and time are changed from the logout date and time. Login state by making new. The record 65d is an updated user record.

The student screen generation program 66 on the intranet server 12 which has received the login success (session ID) from the center server 13 transmits the received session I
A student screen 67 is generated for the client 11a.
Then, the attendee screen 67 is transferred. Also, the session ID of the successful login is registered in the temporary file 68 on the intranet server 12.

Thereafter, when the service request is transferred from the client 11a, the intranet server 12 first obtains a session ID. Session I acquired
It is checked whether D exists in the temporary file 68 on the intranet server 12. If it exists, it determines that it is in the login state and responds. If it does not exist, it rejects the response.

FIG. 7 is a transfer sequence showing a series of processes in logout. Hereinafter, the logout operation of the present system will be described with reference to FIG. FIG. 7 shows the processing contents of each of the client (referred to as 11a), the intranet server 12, and the center server 13, and arrows indicate the exchange of data.

The logout request program 72 on the intranet server 12, which has received the logout request from the student screen 71 of the client 11a, makes a logout request (session ID) to the center server 13. When the logout request program 72 is started, the session management program 73 is started and the center server 13 is started.
Of a session ID required for a logout request of the user.

The logout program 74a on the center server 13 which has received the logout request from the intranet server 12 stores the user management table 43 in the session I
The corresponding record is updated by searching with D and URL.
The update item is one item of the logout date and time. The URL is obtained from the environment variable of the transmitted intranet server 12. When the logout is successful, the logout program 74a transfers a successful logout (session ID) to the intranet server 12.

In FIG. 7, reference numeral 74b denotes an example of updating a record in the user management table 43. In this example, when the user with the user ID “001” logs in, the session ID is “2001” and the URL is “www.b.co.”
m ”is registered. If this session ID is "200
1 ", the password is" 111 ", and the URL is" www.
b. com ”for the logout date and time of the record“ 19 ”.
990602140000 ", and the logout date and time is made newer than the login date and time, thereby setting the logout state. The record 74c is a record before update, and the record 74d is a record after update.

The logout confirmation screen generation program 75 on the intranet server 12 that has received the logout success from the center server 13 generates a logout confirmation screen 76 of the received session ID, and
The logout confirmation screen 76 is transferred to a. Further, the intranet server 12 deletes the session ID for which the logout has succeeded from the temporary file 68 on the intranet server 12.

FIG. 8 is a transfer sequence showing a series of processing in double login. Hereinafter, an operation of preventing double login of the present system will be described with reference to FIG. FIG. 8 shows the processing contents of each of another client (here, 11b), the intranet server 12, and the center server 13, and the arrows show the exchange of data. It is assumed that the user has already logged in with the same user ID.

On the client 11b, the login screen 8
1. The same user ID and password that are currently logged in are input to 1 and a login request (user ID and password) is made to the intranet server 12.

The login request program 82 on the intranet server 12, which has received the login request from the client 11b, makes a login request (user ID, password, session ID) to the center server 13.
When the login request program 82 is started, the session management program 83 is started, and a session ID required for a login request of the center server 13 is obtained.

The login program 84a on the center server 13 that has received the login request from the intranet server 12 refers to the user management table 43 and authenticates the user with the received user ID and password.
If the user ID and the password are correct, the corresponding user record in the user management table is updated. The update items are the received session ID, the URL acquired from the environment variables of the intranet server, and the login date and time.
Note that the URL of the intranet server is obtained from the environment variables of the intranet server.

In FIG. 8, reference numeral 84b denotes an example of updating a record in the user management table 43. Here, the user record 84c corresponds to the record 65d in FIG. Now
Since a login request is made from another client 11b, the session ID or the URL is always different. Therefore, since the login date and time are greater than the logout date and time, it is determined that the user is in the login state and the login is rejected. The login program 84a is connected to the intranet server 12
To the login failure (session ID).

The student screen generation program 85 on the intranet server 12 that has received the double login failure from the center server 13 generates a login failure screen 86 for the received session ID, and sends the login failure screen 86 to the client 11b. Perform a transfer.

FIG. 9 is a transfer sequence showing a series of processes in the session disconnection logout process. Hereinafter, the session disconnection logout processing operation of the present system will be described with reference to FIG. FIG. 9 shows the processing contents of the client (referred to as 11a), the intranet server 12, and the center server 13, and the arrows show the exchange of data. Here, it is assumed that the WWW browser is stopped while the client 11a is logged in.

The session management program 91 in the intranet server 12 periodically checks the session of the client. If the WWW browser of the client 11a is not running 92, the session management program 91 logs out to the logout request program 93 in the intranet server 12. Transfer the request (disconnected session ID). The logout request program 93 makes a logout request (session ID) to the center server 13.

The logout program 94a on the center server 13, which has received the logout request from the intranet server 12, stores the user management table 43 in the session I
The corresponding user record is updated by searching with D and URL. The update item is one item of the logout date and time. UR
L is obtained from the environment variable of the intranet server 12 that has transmitted it. If the logout is successful, a request to delete the session ID from the intranet server (session I
D).

In FIG. 9, reference numeral 94b denotes an example of updating a record in the user management table 43. Here, user I
The user whose D is “001” has a session ID “2001” and a URL “www.b.com” when logging in.
(See 65b in FIG. 6). Session I
D is “2001” and the URL is “www.b.co.
The logout date and time of the record of “m” is “199906”.
0240000 "to make the logout date and time newer than the login date and time, thereby setting the logout state.
The record 94c is a record before update, and the record 94d is a record after update.

The screen generation program 95 on the intranet server 12, which has received the session ID deletion request (session ID) from the center server 13,
D is deleted from the temporary file 96 on the intranet server 12.

Although the embodiment of the present invention has been described above, the present invention is not limited to a three-tier client / server configuration, but is generally applicable to an N-tier (N ≧ 3) client / server system.

[0038]

As described above, according to the present invention, in a three-layer or higher-layer WWW client-server system, a user is managed by a client session ID and an intranet server URL. Therefore, it is not necessary to double manage information for associating a user ID with a session ID and login information on the intranet server and the center server. Further, double login can be easily prevented. Furthermore, when the web browser is terminated in the logged-in state, the logout is automatically performed, so that the user can log in again after a certain period of time.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a three-tier client / server system using WWW according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating a configuration example of a client.

FIG. 3 is a diagram illustrating a configuration example of an intranet server.

FIG. 4 is a diagram illustrating a configuration example of a center server.

FIG. 5 is a diagram illustrating a configuration example of a user management table.

FIG. 6 is a transfer sequence diagram showing a series of processes in login.

FIG. 7 is a transfer sequence diagram showing a series of processes in logout.

FIG. 8 is a transfer sequence diagram showing a series of processes in preventing double login.

FIG. 9 is a transfer sequence diagram showing a series of processes of logout due to session disconnection.

[Explanation of symbols]

 11a, 11b, 11c Client 12 Intranet server 13 Center server 14a, 14b Ethernet (registered trademark) LAN 15a, 15b Router 21 WWW browser 22 Network device 23 Internet 31 WWW server 32 Magnetic disk device 33a Session management program 33b Login management program 33c Logout Management program 33d Student screen generation program 34 Network device 35 Internet 41 WWW server 42 Magnetic disk device 43 User management table 44a Session program 44b Login program 44c Logout program 45 Network device 46 Internet

Claims (4)

[Claims] 1. A user management method in a WWW hierarchical client-server system in which a plurality of client devices are connected to a center server via an intranet server, wherein the center server transmits a client session ID and the session ID. Intranet server U
A user management method for a WWW hierarchical client / server system, wherein a user is specified by RL and the user is managed. 2. The center server has a session ID and a UR.
2. The user management method for a WWW hierarchical client / server type system according to claim 1, wherein the user log-in date and log-out date and time are managed in correspondence with the user specified by L. 3. The center server according to claim 2, wherein, upon receiving the login request, if the login date and time is newer than the logout date and time of the managed user, the center server rejects the received login request. A user management method for a WWW hierarchical client / server type system. 4. When the intranet server confirms the disconnection of the session with the client, the intranet server sends a logout request to the center server, and the center server receiving the logout request logs out the corresponding user. WWW hierarchical client described in 1 to 3
User management method for server type system.