JP2008225941A - Session management device, program and storage medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a session management device, ensuring the sacurity of a WEB site to be provided, and improving the operability of a user. <P>SOLUTION: A session management server 15 creates a unique user session ID 29 for every user when a user accesses from a terminal device 5 to a server A 11, and creates a service session ID31 unique to every service account. In screen transition related to a server A 11 of the same group, both the user session ID 29 and the service session ID 31 are authenticated. When linked to the WEB site provided by the related server B 19, the service session ID 31 is used as link information. In returning from the related link WEB site to the WEB site of the server A 11, an account corresponding to the service session ID 31 as link information is retrieved, and the WEB site of the server A 11 can be again used by the account concerned. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a session management apparatus that manages session information.

  Conventionally, integrated management using a domain (domain controller) has been proposed as authentication / account management. The user has a unique account on the domain and can access the WEB site under the domain. An account on a domain is not valid in another domain.

It is difficult to integrate all of these into one domain, such as when there are multiple existing WEB site provisioning servers, each of which owns an identity system, or when there are users who use multiple accounts Met.
Therefore, there is a method of performing authentication by identity cooperation between WEB site providing servers instead of the integrated management by domain.

In addition, in order to link different WEB site providing servers, there is an information processing system that uses service session information and places a service cooperation server to generate a task session indicating the cooperation between the WEB site providing servers (for example, [[ (See Patent Document 1].)
In addition, in order to enable a service across different WEB site providing servers, a method for managing a series of operations in a task session with a portal site and managing each WEB site providing server as a thread session. (For example, refer to [Patent Document 2].)
In addition, there is a system that guarantees that the user is an authorized user to the related WEB site by one-time user authentication at the main WEB site and prevents direct access to the sub WEB site without going through the main WEB site. (For example, see [Patent Document 3].)

JP 2006-195791 A JP 2004-178466 A JP 2002-014927 A

  However, when user information is included in the linkage information when accessing the related WEB site, the method of taking over the linkage information on the network is dangerous such as leakage of user information or unauthorized access using the leaked information. There is a problem with safety.

  In addition, WEB site providing servers that are already operated with different identity systems may become one group due to a corporate merger or the like. It is possible to perform authentication linkage by identity linkage between WEB sites. For example, you can log out from the services of all the WEB site providing servers you use, or all WEB where the same user is logged in with different accounts There is a problem that it is difficult to perform integrated management such as logging out from the site providing server or linking sessions.

  Moreover, the system shown in Patent Document 1 uses service session information as information for associating cooperation between WEB site providing servers, instead of user information having a risk of leakage of personal information. However, the system according to Patent Document 1 generates a task session indicating cooperation of service session information by placing a service cooperation server separately. Therefore, the system according to Patent Document 1 has a problem that the introduction of a task session indicating cooperation complicates the system configuration and increases the processing load of the entire system.

  The method shown in Patent Document 2 is for a portal site to manage a predetermined set of web services including processing procedures, and it is not assumed that a user arbitrarily accesses a related WEB site. There is a problem.

  In the conventional example and the system shown in the above patent document, when the same user logs in to the same WEB site providing server using a plurality of different accounts, the WEB site management side recognizes it as a different user. was there. Therefore, management with a sense of unity is difficult even though the same user is accessing.

  In addition, the systems shown in the conventional examples and the above-mentioned patent documents have a problem that it is difficult to link with related WEB sites in service account units. For example, when the same user logs in with a different account and each account accesses a different related WEB site, the cookie information is overwritten each time the access is made, so the account accessed when returning to the original WEB site There is no guarantee that you can return to the original WEB site. Therefore, there is a problem that the operability regarding the cooperation of the WEB site is bad for the user.

  The present invention has been made in view of the above problems, and an object of the present invention is to provide a session management apparatus capable of ensuring the safety of a provided WEB site and improving user operability. .

  In order to achieve the above-described object, the first invention is provided between at least one information providing server that provides various types of information and at least one terminal device that is connected to the information providing server via a network and belongs to a user. A session management apparatus that manages a session that is a communication unit of the user, and when the user accesses the information providing server from the terminal device, a unique first session ID for each user and the information providing server provide Session ID creation means for creating a unique second session ID for each service to be performed; session ID transmission means for sending the first session ID and the second session ID to the terminal device of the user that is the access source; One session ID and at least one second session ID are associated with each other Session registration means for registering as management information, the first session ID and the second session ID sent from the user terminal device, and the registered first session ID and second session ID. A session management unit, comprising: a session verification unit that verifies and determines the use authority of the user in the information providing server.

The first session ID (user session ID) is an identification ID created for each user. When the user logs in to the information providing server once from the terminal device and accesses with a different account, the first session ID is not created because the first session ID has already been created for the user.
The second session ID (service session ID) is an identification ID created for each service provided by the information providing server. The second session ID is created every time the user logs in to the service provided by the information providing server from the terminal device.
The account is a user ID for logging in systematically. One user may have a plurality of accounts for the same information providing server.

  When the user accesses the information providing server from the terminal device, the session management device according to the first aspect of the invention provides a unique first session ID for each user and a unique second session ID for each service provided by the information providing server. Create The session management device sends the first session ID and the second session ID to the access source terminal device, and registers the first session ID and the second session ID in association with each other as session management information. The session management device collates the first session ID and second session ID sent from the user terminal device with the registered first session ID and second session ID, and determines the use authority in the user information providing server. judge.

  In the first invention, even when the user accesses the information providing server from a terminal device with a different account, the same first session ID is created, so the session management server determines that the access is from the same user. be able to. Therefore, the session management server can integrally manage access from the same user.

The session management device uses the second session ID as linkage information when the user accesses another information providing server via the information providing server accessed from the terminal device, and the information providing server and the other information providing server May be linked.
By using the second session ID as linkage information, it is possible to prevent the risk of leakage of information related to the user to the linkage destination information providing server.

In addition, when the user accesses the cooperation source information providing server again from the terminal device via the cooperation destination information providing server, the session management device receives various information on the user terminal device based on the service indicated by the second session ID. May be provided.
Thereby, a user's terminal device becomes possible [cooperation with the information provision server for every service which 2nd session ID shows], and can improve the operativity of a terminal device.

Moreover, the session management apparatus may restrict or disable the use authority of the user in the information providing server when the collation result of the first session ID and the second session ID is not appropriate.
Thereby, since the information providing server discriminates the user having the right to use, it is possible to prevent unauthorized access and information leakage and to ensure safety.

In addition, the session management device performs simple authentication compared to the authentication at the time of login for the user when the verification result of the second session ID is appropriate and the verification of the first session ID is not possible. May be.
Thereby, if the collation result of the second session ID from the cooperation destination is appropriate, the user can return to the cooperation source with simple authentication. Simple authentication is authentication performed using, for example, at least one of a user ID and a password.

Further, the session management device may record the first session ID in cookie information that can be referred to by the information providing server and cause the terminal device to hold the first session ID.
Further, the session management apparatus may record the second session ID in a parameter of net position information such as a URL (Uniform Resource Locator) and send it to the terminal apparatus.

The second invention is a program for causing a computer to function as the session management device of the first invention.
A third invention is a computer-readable recording medium on which a program for causing a computer to function as the session management device of the first invention is recorded.

  ADVANTAGE OF THE INVENTION According to this invention, the session management apparatus which can ensure the safety | security of the WEB site to provide and can improve a user's operativity can be provided.

  Hereinafter, a preferred embodiment of a session management apparatus according to the present invention will be described in detail with reference to the accompanying drawings. In the following description and the accompanying drawings, the same reference numerals are given to components having substantially the same functional configuration, and redundant description is omitted.

(1. Configuration of session management system 1)
First, the configuration of the session management system 1 will be described with reference to FIG.
FIG. 1 is a configuration diagram of the session management system 1.
The session management apparatus according to the present invention is a session management server that manages a session of an information providing server in the session management system 1.

  The session management system 1 includes a terminal device 5 and a server (A1) 11-1, a server (A2) 11-2,... Further, a plurality of terminal devices 5 and servers may be connected.

  The terminal device 5 belongs to the user 3. The server (A1) 11-1, the server (A2) 11-2,... Belong to the business operator (A1) 9-1, the business operator (A2) 9-2,. The business operator (A1) 9-1, the business operator (A2) 9-2,... Are in a partnership relationship as a group A13, and the terminal device 5 includes a server (A1) 11-1 and a server (A2) 11-2. It is possible to access (screen transition) between WEB sites provided by... As if they were provided by a single server.

  That is, when the user 3 logs in to any of the servers A11 (server (A1) 11-1, server (A2) 11-2,...) Belonging to the group A13, all the servers A11 seem to be integrated into one WEB. A site providing server is configured, and the user 3 is equivalent to logging in and using this single WEB site providing server.

  The session management server 15 manages session information that is information related to access of all the servers A11 in the group A13.

  The server B19 and the session management server 21 belong to the business operator B17. The session management server 21 manages session information that is information related to access of the server B19.

Next, the configuration of the session management system 1 will be described in more detail with reference to FIG.
FIG. 2 is a diagram showing the configuration of the session management system 1 in detail.

(1-1. Configuration of Terminal Device 5)
The terminal device 5 is a device such as a computer that can be connected to the server A 11, the server B 19, the session management server 15, and the session management server 21 via the network 7.

The terminal device 5 includes a WEB page request unit 25 and a WEB page display unit 27. The WEB page requesting means 25 is a means for requesting a WEB page from the server A11 or the server B19 of the provider that provides the WEB page. The WEB page display means 27 is a means for displaying the WEB page 55 provided from the server A11 or the WEB page 83 provided from the server B19.
The terminal device 5 receives and stores the session information 23 (FIG. 4) related to the session provided together with the WEB page 55. Details of the session information 23 will be described later.

(1-2. Configuration of Session Management Server 15)
The session management server 15 includes a session acquisition unit 33, a session collation unit 35, a user session ID creation unit 43, a service session ID creation unit 45, a session registration unit 47, a cooperation unit 49, and a computer having session management information 37 in the storage unit. Etc.

  The session management server 15 registers and manages session information related to all servers A11 in the session management information 37 (FIG. 5). The session management server 15 acquires the user session ID 29 and the service session ID 31 sent from the terminal device 5, and transmits the user session ID 29 and the service session ID 31 to the terminal device 5.

The session acquisition unit 33 acquires information (user session ID 29, service session ID 31) related to a session sent from the terminal device 5 together with the WEB page request.
The session collation unit 35 collates the information regarding the session acquired by the session acquisition unit 33 with the registration information of the session management information 37 (FIG. 5).

The user session ID creation unit 43 creates a user session ID 29 that is unique identification information for each user 3. For creating the user session ID 29, identification information (for example, a user ID) related to the user may be used.
The service session ID creating unit 45 creates a service session ID 31 that is unique identification information for each service that the user 3 logs in from the terminal device 5.
The session registration unit 47 registers the created user session ID 29 and service session ID 31 in the session management information 37.
The cooperation unit 49 provides the service session ID 31 registered in the session management information 37 as the cooperation information to the server A11 when the WEB page 55 is created.
Details of the session management information 37 will be described later.

(1-3. Configuration of Server A11)
The server A11 is a device such as a computer having user authentication means 39, WEB page creation means 51, and user information 41, content information 53, and the like in a storage unit.
The user authentication means 39 collates the authentication information (user ID, password, etc.) sent from the terminal device 5 with the user information 41 (FIG. 7), and determines whether or not the user 3 of the terminal device 5 is a valid user. Certify.
The WEB page creation means 51 takes out the corresponding content from the content information 53 and creates a WEB page 55. The content information 53 is content such as characters, numerical values, video, images, and audio.

(1-4. Configuration of Session Management Server 21)
The session management server 21 is a device such as a computer having session management information 71 and the like in a session acquisition unit 63, a session verification unit 65, a session ID creation unit 73, a session registration unit 75, a cooperation unit 77, and a storage unit.

  The session management server 21 registers and manages the session information of the server B19 in the session management information 71 (FIG. 6). The session management server 21 acquires the session ID 61 and the service session ID 31 as cooperation information sent from the terminal device 5 of the user 3, and transmits the session ID 61 and the service session ID 31 as cooperation information to the terminal device 5.

The session acquisition unit 63 acquires information regarding the session sent from the terminal device 5 together with the WEB page request.
The session collation unit 65 collates the information regarding the session acquired by the session acquisition unit 63 with the registration information of the session management information 71 (FIG. 6).

The session ID creation means 73 creates a session ID 61 that is unique identification information for identifying access.
The session registration means 75 registers the created session ID 61 in the session management information 71.
The cooperation unit 77 provides the cooperation information 103 (service session ID 31) registered in the session management information 71 to the server B19 when the WEB page 83 is created.
Details of the session management information 71 will be described later.

(1-5. Configuration of Server B19)
The server B19 is a device such as a computer having user authentication means 67, WEB page creation means 79, and user information 69, content information 81, etc. in the storage unit. Since each configuration is the same as that of the server A11, description thereof is omitted.

(2. Hardware configuration)
Next, the hardware configuration of the terminal device 5, the server A11, the server B19, the session management server 15, and the session management server 21 will be described with reference to FIG.
FIG. 3 is a hardware configuration diagram of the terminal device 5, the server A 11, the server B 19, the session management server 15, and the session management server 21. Note that the hardware configuration shown in FIG. 3 is merely an example, and various configurations can be adopted depending on the application and purpose.

  The terminal device 5, the server A 11, the server B 19, the session management server 15, and the session management server 21 include the CPU 151, the memory 153, the storage unit 155, the display unit 157, the input unit 159, the output unit 161, and the communication unit 163 via the system bus 165. Connected and configured.

  A CPU 151 (Central Processing Unit) is an arithmetic device (four arithmetic operations, comparison operations, etc.), and a device that performs hardware and software operation control.

  The memory 153 is a memory such as a RAM and a ROM. A RAM (Random Access Memory) stores a ROM (Read Only Memory), an OS (Operating System) program read from the storage unit 155, an application program, and the like. The RAM functions as a main memory and work area for the CPU 151.

  The storage unit 155 is a device that stores various data, and is, for example, a hard disk. The storage unit 155 stores programs executed by the CPU 151, data necessary for program execution, an OS, various databases, and the like.

  The display unit 157 is a display device, such as a CRT monitor or a liquid crystal panel. The display unit 157 includes a logic circuit (such as a video adapter) for realizing the video function of the computer.

  The input unit 159 is an input device for various data, such as a keyboard and a mouse. The output unit 161 is an output device for various data, for example, a printer. Drive devices that perform data input / output with various media can also be used as the input unit 159 and the output unit 161.

The communication unit 163 is a communication control device that connects and communicates with an external device via the network 165. For example, Internet communication using TCP / IP is possible.
The system bus 165 is a path that mediates transmission / reception of control signals, data signals, and the like between the devices.

  The terminal device 5, the server A 11, the server B 19, the session management server 15, and the session management server 21 store programs (application programs, OS programs, etc.) stored in the storage unit 155, ROM, or storage medium in the RAM of the memory 153. Various processes are executed under the control of the CPU 151 after loading.

(3. Configuration of Session Information 23, Session Management Information 37, Session Management Information 71, and User Information 41)
(3-1. Session information 23)
Next, the session information 23 held by the terminal device 5 will be described with reference to FIG.
FIG. 4 is a diagram illustrating an example of the configuration of the session information 23.
Information relating to the session sent together with the WEB page 55 provided by the server A11 and the WEB page 83 provided by the server B19 is stored as session information 23 in the storage unit 155 of the terminal device 5.

  The session information 23 includes items such as a user session ID 87, a service session ID 89, a session ID 91, an expiration date 93, and an account 95. The user session ID 87 and the service session ID 89 store the user session ID 29 and the service session ID 31 sent together with the WEB page 55 from the server A 11, and the expiration date 93 stores the expiration date of the user session ID 29 and the service session ID 31. The In the account 95 item, an account (for example, “user1 @ A1”) of the user 3 logged into the server A11 from the terminal device 5 is stored.

  In the session ID 91 item, the session ID 61 sent together with the WEB page 83 from the server B 19 is stored, and the expiration date of the session ID 61 is stored in the expiration date 93. When the user 3 logs in to the server B 19 from the terminal device 5, an account (for example, “bar @ B”) is stored in the item of the account 95.

  The expiration date 93 is updated every time the terminal device 5 accesses the server A11 or the server B19. Further, when the expiration date 93 elapses, the user session ID 29 and the service session ID 31 or the session ID 61 are invalidated.

(3-2. Session management information 37)
Next, the session management information 37 held by the session management server 15 will be described with reference to FIG.
FIG. 5 is a diagram illustrating an example of the configuration of the session management information 37.
The session management information 37 is information related to a session stored in the storage unit 155 of the session management server 15 of the group A13.

  The session management information 37 includes items such as a user session ID 87, a service session ID 89, an expiration date 93, an account 95, and a cooperation destination 97. In the items of the user session ID 87 and the service session ID 89, a user session ID 29 and a service session ID 31 generated by the session management server 15 when the user 3 logs in to the group A13 (any one of the servers A11) from the terminal device 5 are stored. In the expiration date 93, the expiration dates of the user session ID 29 and the service session ID 31 are stored.

  In the account 95 item, an account (for example, “user1 @ A1”) of the user 3 logged in to the group A13 (any one of the servers A11) is stored. The cooperation destination 97 stores a cooperation destination (for example, “server B”) when a transition is made from the WEB site provided by the group A13 (any one of the servers A11) to the WEB site provided by another server.

The expiration date 93 is updated every time the user 3 accesses any of the servers A11 by the terminal device 5. When the expiration date 93 has elapsed, the user session ID 29 and the service session ID 31 are invalidated.
Further, the value of the user session ID 87 is unique for each user 3. Further, the value of the service session ID 89 is unique for each service (account 95) to be provided.

(3-3. Session management information 71)
Next, the session management information 71 held by the session management server 21 will be described with reference to FIG.
FIG. 6 is a diagram illustrating an example of the configuration of the session management information 71.
The session management information 71 is information related to a session stored in the storage unit 155 of the session management server 21 of the business operator B17.

  The session management information 71 includes items such as a session ID 99, an expiration date 93, an account 95, a cooperation source 101, and cooperation information 103. The item of session ID 99 stores the session ID 61 generated by the session management server 21 when the user 3 accesses the business operator B 17 (server B 19) by the terminal device 5, and the expiration date 93 indicates the expiration date of the session ID 61. Saved.

  In the account 95 item, an account (for example, “bar @ B”) when the user 3 logs in to the server B 19 by the terminal device 5 is stored. The cooperation source 101 stores the cooperation source (for example, “server A1”) when accessing the server B19 from the WEB page provided by the group A13 (any one of the servers A11). The cooperation information 103 stores the value (for example, “SS11”) of the service session ID 31 sent as the cooperation information from the terminal device 5 at the time of cooperation.

  The expiration date 93 is updated every time the user 3 accesses the server B 19 by the terminal device 5. Further, when the expiration date 93 elapses, the session ID 99 is invalidated.

(3-4. User information 41)
Next, the user information 41 held by the server A11 will be described with reference to FIG.
FIG. 7 is a diagram illustrating an example of the configuration of the user information 41.
The user information 41 is information about the user stored in the storage unit 155 of the server A11.

The user information 41 has items such as an account 95 and a password 105. Detailed information (name, address, transaction information, etc.) regarding the user 3 may be stored in the user information 41 for each account 95, but description thereof is omitted here.
In the account 95 item, an account (user ID) when the user 3 logs in to the server A11 is stored. The same user 3 may have a plurality of accounts (user IDs) for the same server A11.
In the item of the password 105, an identification ID for performing user authentication with both the account (user ID) is stored.

(4. Operation of session management system 1)
Next, the operation of the session management system 1 will be described with reference to FIGS. The screen displayed on the display unit 157 of the terminal device 5 will be described with reference to FIGS. 12 to 18 as appropriate.
The terminal device 5 receives content from the server A11 and the server B19 based on the operation of the input unit 159 by the user 3. The terminal device 5 displays the screen A provided from the server A11 and the screen B provided from the server B19 on the display unit 157.

(4-1. Session management during login)
FIG. 8 is a flowchart showing session management when the session management server 15 logs in.
A top screen 301 is displayed on the display unit 15 of the terminal device 5. The top screen 301 is, for example, a screen of a predetermined WEB site provided by a securities company or the like. The terminal device 5 makes a login request to the server A11 (group A13) via the top screen 301.

FIG. 12 is a diagram illustrating a top screen 301 provided by the server A11.
When an account (user ID) and password are input on the top screen 301 and the “login request button” 107 is clicked, a login request is transmitted from the terminal device 5 to the server A11 and the session management server 15 (step 1001).

  If the terminal device 5 has already logged in to the server A11 using another account (user ID), a unique user session ID 29 has already been created for each user 3 by the server A11. Simultaneously with the login, the user session ID 29 is also sent to the server A11.

  The user authentication means 39 of the server A11 compares the account (user ID) and password sent from the terminal device 5 with the values registered in the user information 41 (FIG. 7), and performs user authentication (step 1002).

  The session acquisition unit 33 of the session management server 15 acquires session information sent from the terminal device 5, and the session verification unit 35 determines whether or not the acquired user session ID 29 has been registered with the session management information 37 (FIG. 5). Collate.

  If the user session ID 29 has not been sent from the terminal device 5 or if the sent user session ID 29 has not been registered or is not valid (NO in step 1003), the user session ID creation means 43 newly creates a user session. ID 29 is created (for example, user session ID 29 “US01”), and session registration means 47 registers it in session management information 37 (step 1004).

  If the user session ID 29 has been registered and is valid (within the expiration date) (YES in step 1003), or if a new user session ID 29 is created and registered in step 1004, the service session ID creation means 45 is newly created. A service session ID 31 is created (for example, service session ID 31 “SS11”), and the session registration unit 47 registers it in the session management information 37 (step 1005). The session registration unit 47 registers the expiration date 93 of the service session ID 31 and the user account 95 (for example, “user1 @ A1”) in the session management information 37 at the same time.

The WEB page creation means 51 of the server A11 creates a WEB page 55 by extracting the content from the content information 53 and sends it to the terminal device 5 (step 1006). The server A11 sends the service session ID 31 to the terminal device 5 together with the WEB page 55. Further, a user session ID 29 may be sent.
The terminal device 5 displays the WEB page (server A provision screen (1) 302) on the display unit 157 (step 1007).

FIG. 13 is a diagram showing a server A providing screen (1) 302 provided by the server A11.
On the server A provision screen (1) 302, buttons and links for accessing a WEB site provided by the server A11 and other related servers are displayed.
For example, a “market price information” button 109 is an access button to a market price information screen provided by another related server (server B19).

  The server A provided screen (1) 302 (FIG. 13) is a screen displayed when the user 3 logs in to the server (A1) 11-1 from the terminal device 5 with the account “user1 @ A1”.

  The terminal device 5 stores the user session ID 29 and the service session ID 31 sent together with the WEB page 55 in the session information 23 (step 1008).

  FIG. 14 shows a screen in which the user 3 logs into the server (A1) 11-1 from the terminal device 5 using an account “user2 @ A1” different from the account “user1 @ A1”. When the account (user ID) “user2 @ A1” and the password are input on the server A providing screen (2) 303 (FIG. 14) and the login button 107 is clicked, the user 3 uses the account “user2 @ A1” as the server. (A1) It is possible to log in to 11-1.

  In this case, the user session ID 29 is already registered in the session management information 37 (FIG. 5) when logging in with the account “user1 @ A1”. Accordingly, only a new service session ID 31 “SS12” is created and registered as the record 205 (FIG. 5).

  FIG. 15 shows a screen in which the user 3 uses the server (A1) 11-1 from the terminal device 5 with both the accounts “user1 @ A1” and “user2 @ A1”. The server (A1) 11-1 side grasps that the same user 3 is logged in because the values of the user session ID 29 corresponding to the two accounts “user1 @ A1” and “user2 @ A1” are the same. To do.

  Through the above process, the session management server 15 creates a new service session ID 31 for each service (for each service account) provided by the server A11 when the user 3 requests a login from the terminal device 5 to the server A11 of the group A13. And register. If the user session ID 29 is not registered, the session management server 15 newly creates and registers a user session ID 29.

  As described above, since the session management server 15 creates a unique user session ID 29 for each user 3, the user session ID 29 can be used for integrated processing for each user 3.

  For example, as in the record 204 and the record 205 of the session management information 37 (FIG. 5), even if the value of the account 95 is different, the value of the user session ID 87 is the same. I understand. Also, the record 206 logged in with the account 95 “foo @ A2” to a different server A11 (server (A2) 11-2) in the group A13 has the same user session ID 87 value as the records 204 and 205. Thus, it can be seen that the access is from the same user 3.

  In addition, since the session management server 15 creates a unique service session ID 31 for each service (for each service account), it can be used for integrated processing for each service that provides the service session ID 31.

  In addition, the session management server 15 uses the user session ID 29 and the service session ID 31 in combination as session information, so that appropriate use according to the scene, such as integrated management for each user or management for each service, is possible. is there. As will be described later, when linking to other related WEB sites, it is possible to ensure safety against information leakage by using only the service session ID 31 as linkage information.

(4-2. Session management when updating WEB pages)
FIG. 9 is a flowchart showing session management when the WEB page of the session management server 15 is updated. The update of the WEB page indicates a re-display of the WEB page, a screen movement to another WEB page, or the like.
After logging in to the server A11, the terminal device 5 requests a web page update request provided by the server A11 or a web page provided by any server A11 belonging to the group A13 (step 2001).

  The terminal device 5 sends the user session ID 29 and the service session ID 31 sent from the server A11 after login to the server A11 and the session management server 15 together with the WEB page request.

  The session acquisition unit 33 of the session management server 15 acquires a session, and the session verification unit 35 collates the user session ID 29 sent from the terminal device 5 of the user 3 with the service session ID 31 based on the session management information 37 ( Step 2002). When the validity including the expiration date of the user session ID 29 and the service session ID 31 is authenticated, the WEB page creation means 51 of the server A11 creates a WEB page 55 and sends it to the terminal device 5 (step 2003). The session management server 15 updates the corresponding expiration date 93 of the session management information 37.

  Through the above process, the user 3 sends the user session ID 29 and the service session ID 31 to the session management server 15 when making a WEB page request from the terminal device 5 to any server A11 in the group A13. The session management server 15 authenticates the validity of the user session ID 29 and the service session ID 31 based on the session management information 37, and then sends the WEB page 55 to the terminal device 5 together with the user session ID 29 and the service session ID 31 whose expiration date has been updated. send.

  As described above, the session management server 15 is a user issued at the time of login when the terminal device 5 logged in to any server A11 in the group A13 requests WEB page display or update provided by any server A11. Authentication of both session ID 29 and service session ID 31 is requested.

  Therefore, for example, by using the service session ID 31 leaked from the terminal device 5, unauthorized access from the terminal device trying to use any server A <b> 11 of the group A <b> 13 can be prevented.

  In the screen transition between different servers A11, the login process can be performed in each server A11, but the login process may not be performed in consideration of operability. In this case, instead of holding the user information 41 for each server A11, the user information 41 may be centrally managed by the session management server 15.

(4-3. Session management during screen transition to the linked server)
FIG. 10 is a flowchart showing session management when a WEB page provided by the server B19 is requested from a WEB page provided by the server A11.
After logging in to the server A11, the terminal device 5 requests the WEB page provided by the server B19 from the WEB page provided by the server A11 (step 3001).

  For example, in the server A providing screen (1) 302 (FIG. 13) provided by the server A11 displayed on the terminal device 5, the “market price” is an access button to the market price information screen provided by another related server (server B19). The “information” button 109 is clicked.

  The terminal device 5 sends the service session ID 31 to the session management server 15 of the server A11. The session management server 15 registers the cooperation destination 97 in the record of the corresponding service session ID 31 in the session management information 37 (step 3002). For example, in the case of the service session ID 31 “SS11”, “Server B” is registered in the cooperation destination 97 of the record 204.

  Further, the terminal device 5 sends the service session ID 31 together with the WEB page request to the session management server 21 of the server B 19 as linkage information. In the case of the first access from the terminal device 5, the session ID creation means 73 of the session management server 21 creates a session ID 61, and the session registration means 75 registers the session ID 61 in the session management information 71 (FIG. 6) (step 3003). ).

  Also, the session management server 21 registers the service session ID 31 sent from the terminal device 5 in the session management information 71 as the linkage information 103 (step 3004).

  For example, the created session ID 31 “S31” is registered in the item of session ID 99 of the record 207 of the session management information 71, “server A1” is registered in the cooperation source 101, and the service session ID 31 “SS11” is transmitted to the cooperation information 103. Is registered.

The WEB page creation means 79 of the server B19 creates a WEB page 83 by extracting the content from the content information 81 (step 3005). The WEB page 83 is sent to the terminal device 5 together with the session ID 61 and the service session ID 31 as linkage information.
The terminal device 5 displays the WEB page (server B provision screen 305) on the display unit 157 (step 3006).

FIG. 16 is a diagram illustrating a server B provision screen 305 provided by the server B.
On the server B provision screen 305, market price information 111 is displayed. The “Go to XX securities order screen” button 112 is an access button to a screen provided by the server A11.

  The terminal device 5 stores the session ID 61 “S31” sent together with the WEB page 83 as the record 203 in the session ID 91 item of the session information 23 (step 3007).

  Through the above process, when the user 3 requests the WEB page provided by the server B 19 from the WEB page provided by the server A 11 by the terminal device 5, the session management server 15 of the server A 11 sets the cooperation destination 97 as the session management information 37. Register with. The session management server 21 of the server B 19 that is the cooperation destination registers the service session ID 31 created by the server A 11 as the cooperation information 103. The session management server 21 creates and registers a session ID 61, and the server B 19 sends a session ID 61 and a service session ID 31 as cooperation information to the terminal device 5 together with the WEB page 83.

Thus, when the user 3 requests the WEB page provided by the server B19 from the WEB page provided by the server A11 from the terminal device 5, the service session ID 31 is transmitted from the server A11 as linkage information. For example, even if the service session ID 31 is leaked, since both the user session ID 29 and the service session ID 31 need to be authenticated in order to use the server A11 of the group A13, it is possible to prevent unauthorized use by a malicious user. it can. That is, by using only the service session ID 31 as linkage information to other related WEB sites, safety against information leakage can be ensured.
Note that the login process may be performed in the server B19 at the time of cooperation from the server A11 to the server B19, or the login process may not be performed in consideration of operability.

(4-4. Session management during screen transition to the collaboration source server)
FIG. 11 is a flowchart showing session management when a WEB page provided by the server A11 is requested from a WEB page provided by the server B19.
After logging in to the server A11, the terminal device 5 makes a screen transition in cooperation with the WEB page provided by the server B19, and requests the WEB page provided by the server A11 again (step 4001).

  For example, in the server B provision screen 305 (FIG. 16) provided by the server B 19 displayed on the terminal device 5, the “To Stock Order Screen” button 112 for accessing the order screen provided by the server A 11 is clicked.

  The terminal device 5 searches the record 201 from the session information 23 based on the service session ID 31 “SS11” sent from the server B 19 as the cooperation information, and extracts the user session ID 29 created by the session management server 15.

  The terminal device 5 transmits the user session ID 29 “US01” and the service session ID 31 “SS11” to the server A11 and the session management server 15 together with the WEB page request.

  The session collation unit 35 of the session management server 15 collates the user session ID 29 “US01” and the service session ID 31 “SS11” based on the session management information 37 (step 4002).

  In addition, the session verification unit 35 searches for an account 95 “user1 @ A1” corresponding to the service session ID 31 “SS11” (step 4003). The WEB page creation means 51 creates a WEB page 55 for the searched account 95 “user1 @ A1” (step 4004).

  The created WEB page 55 is sent to the terminal device 5 together with the user session ID 29 and the service session ID 31. The terminal device 5 displays the WEB page (server A provision screen 306) on the display unit 157 (step 4005).

FIG. 17 is a diagram showing a server A providing screen 306 provided by the server A11.
On the server A providing screen 306, order information 113 is displayed. Also, “user1” is displayed on the terminal device 5, and the terminal device 5 can return to the server A11 with the account “user1 @ A1” when linked to the server B19.

  The terminal device 5 may adopt a method in which the service session ID 31 is sent to the server A11 and the session management server 15 together with the WEB page request and the user session ID 29 is not sent. In this case, instead of collating the user session ID 29 and the service session ID 31 in step 4002, the server A11 may request the terminal device 5 for simple authentication after the collation of the service session ID 31.

  FIG. 18 is a diagram showing a server A provision screen 307 for simple authentication. When a password is entered in the password input field 115, the user authentication means 39 of the server A11 performs user authentication again based on the user information 41 (FIG. 7). The user ID confirmation process performed at the time of login is omitted.

  Further, when the user session ID 29 and the service session ID 31 in step 4002 are collated, for example, when the user session ID 29 and the service session ID 31 are invalidated after the expiration date 93 has passed, the above simple authentication is performed, and the user session ID 29 and the service session ID 31 again. The service session ID 31 may be validated.

  Through the above process, after the terminal device 5 logs into the server A11, the screen transitions in cooperation with the WEB page provided by the server B19, and the terminal device 5 requests the WEB page provided by the server A11 again. The user session ID 29 is extracted from the session information 23 based on the service session ID 31 sent as.

  The terminal device 5 transmits a user session ID 29 and a service session ID 31 to the server A11 and the session management server 15 together with the WEB page request. When the session management server 15 succeeds in collating the user session ID 29 and the service session ID 31, the server A 11 sends the created WEB page 55 to the terminal device 5 together with the user session ID 29 and the service session ID 31.

  As described above, by using the service session ID 31 as the cooperation information, the terminal device 5 can easily return to the original server A11 after transitioning to the server B19 that is the cooperation server. Also, since the WEB page 55 is sent to the account 95 corresponding to the service session ID 31 “SS11”, the terminal device 5 can use the server A11 with the account when linked.

  Since the service session ID 31 is unique for each service (for each service account), the terminal device 5 can use the original server A11 with the account at the time of transition from the transition destination server B19. Confusion when using the services of the server A11 and the server B19 can be reduced and operability can be improved.

(5. Screen transition of server A11 and server B11)
Next, with reference to FIG. 19, screen transitions between the provision screen from the server A11 and the provision screen from the server B11 will be described.
FIG. 19 is a diagram illustrating screen transitions between the provision screen from the server A11 and the provision screen from the server B19.

  When the terminal device 5 logs in to the server A11, a screen 302 is displayed. When the link button 117 to the server B19 is clicked, the information of “cooperation destination server B” is registered in the session management information 37, and the service session ID is transmitted from the server A11 as the cooperation information to the server B19. In the session management information 71 of the server B 19, the service session ID and the information of “cooperation source server A 1” are registered as the cooperation information 103.

A provision screen 305 from the server B 19 is displayed on the terminal device 5. When the link button 119 to the server A11 on the screen 305 is clicked, the service session ID that is registered in the session management information 71 and the information of the “cooperation source server A1” are extracted and stored in the server A11. Sent.
The server A11 collates the service session ID with the session management information 37, and when the collation is successful, displays the screen 306 on the terminal device 5.

(6. Succession of user session ID 29 and service session ID 31)
The takeover of the user session ID 29 and the service session ID 31 is not limited as long as the user session ID 29 and the service session ID 31 can be transmitted and received together with the WEB page request (request) and the WEB page transmission (response). For example, in a WWW (World Wide Web) system, it may be recorded in cookie information or a URL (Uniform Resource Locator) parameter for transmission / reception. In addition, when recording in a URL parameter, it may be embedded in a link on a WEB page.

  In a browser application that displays a WEB page, cookie information is usually overwritten each time an information providing server under the management of one session management server is accessed. On the other hand, URL parameters are easy to refer to.

The user session ID 29 is not desirably referred to by a group site other than the group A13. Therefore, it is desirable to record in the cookie information of the browser instead of the URL parameter. The user session ID 29 is unique for each user 3, and there is no problem even if the cookie information is overwritten with the same value.
On the other hand, since a service session ID 31 may be assigned for each service (for each service account) provided to one user 3, there is a possibility that if the service session ID 31 is recorded in cookie information, it is overwritten with a different value. is there. Therefore, it is desirable to record in URL parameters. Since only the service session ID 31 without the user session ID 29 restricts or disables the authority to use the server A 11, even if the user session ID 29 is referred to by a third party, it is possible to prevent the security effect. .

(7. Effects, etc.)
As described above in detail, in the session management system 1 according to the embodiment of the present invention, the user session ID 29 and the service session ID 31 are used according to the scene, thereby improving customer convenience and preventing information leakage. Safety can be ensured.

  In the group A13 that collates both the user session ID 29 and the service session ID 31 and permits the use of the service, only the service session ID 31 is used as linkage information when linking to other servers. Therefore, it is possible to secure safety against unauthorized use of the group A13.

  In addition, since the service session ID 31 is uniquely created for each provided service (for each service account at the time of login), the service session ID 31 is used as linkage information when returning to the original server again by linking to another server. By taking over, you can return to the original server with the account when linked to other servers. Therefore, confusion of the user 3 can be reduced and operability can be improved.

  In addition, when the same user 3 logs in to the server A11 of the group A13 with different accounts, the same user session ID 29 is created, so that integrated management such as simultaneous logoff can be performed using the user session ID 29, for example. Thus, the convenience of the user 3 is improved.

  The preferred embodiments of the session management system according to the present invention have been described above with reference to the accompanying drawings, but the present invention is not limited to such examples. It will be apparent to those skilled in the art that various changes or modifications can be conceived within the scope of the technical idea disclosed in the present application, and these are naturally within the technical scope of the present invention. Understood.

Configuration diagram of session management system 1 Detailed configuration diagram of session management system 1 The figure which shows the hardware constitutions of the session management server 15, the session management server 21, server A11, server B19, and the terminal device 5. The figure which shows the session information 23 (terminal device 5) The figure which shows the session management information 37 (session management server 15) The figure which shows the session management information 71 (session management server 21) The figure which shows the user information 41 (server A11) Flow chart showing session management at the time of login of the session management server 15 A flowchart showing session management when the WEB page of the session management server 15 is updated. The flowchart which shows the session management at the time of requesting the WEB page which server B19 provides from the WEB page which server A11 provides The flowchart which shows the session management at the time of requesting the WEB page which server A11 provides from the WEB page which server B19 provides The figure which shows the top screen 301 which server A11 provides The figure which shows the server A provision screen (1) 302 The figure which shows the server A provision screen 302,303 The figure which shows the server A provision screen 302,304 The figure which shows the server B provision screen 305 The figure which shows the server A provision screen 306 The figure which shows the server A provision screen 307 The figure which shows the screen transition of the provision screen from server A11, and the provision screen from server B19.

Explanation of symbols

1 ......... Session management system 3 ......... User 5 ......... Terminal device 7 ......... Networks 9-1, 9-2,...
11-1, 11-2, ... Server A
13 ... Group A
15 ... Session management server 17 ... Business B
19 ... Server B
21... Session management server 23... Session information 25... WEB page request means 27... WEB page display means 29 and 87.
31, 89 ……… Service Session ID
33, 63 ......... Session acquisition means 35, 65 ... ... Session verification means 37, 71 ... ... Session management information 39, 67 ... ... User authentication means 41, 69 ... ... User information 43 ... ... User session ID creation means 45... Service session ID creation means 47, 75... Session registration means 49, 77... Cooperation means 51, 79 ...... Web page creation means 53, 81 ...... Content information 55, 83 ……… Web pages 61, 91, 99 ……… Session ID
73 ......... Session ID creation means 93 ......... Expiration date 95 ......... Account 97 ... …… Cooperation destination 101 ... …… Cooperation source 103 ... …… Cooperation information 107 ... …… Login request button 109 ……… "Market price" Information "button 111, 113 ......... Information display 115 ......... Password input field 117 ......... Link button to server B19 119 ......... Return to server A11 button 151 ......... CPU
153 ......... Memory 155 ......... Storage unit 157 ......... Display unit 159 ......... Input unit 161 ......... Output unit 163 ......... Communication unit 201-208 ......... Record 301 ......... Top screen 302- 304, 307 ... …… Screen A
305 ... Screen B

Claims (8)

A session management device that manages a session as a communication unit between at least one information providing server that provides various types of information and at least one terminal device that is connected to the information providing server via a network and belongs to a user. And
A session for creating a unique first session ID for each user and a unique second session ID for each service provided by the information providing server when the user accesses the information providing server from the terminal device ID creation means;
Session ID transmission means for transmitting the first session ID and the second session ID to the terminal device of the user who is the access source;
Session registration means for registering one first session ID and at least one second session ID in association with each other as session management information;
The information providing server of the user by collating the first session ID and the second session ID sent from the terminal device of the user with the registered first session ID and the second session ID Session verification means for determining usage authority in
A session management apparatus comprising:   When the user accesses another information providing server via the information providing server accessed from the terminal device, the information providing server and the other information providing server are used using the second session ID as linkage information. The session management apparatus according to claim 1, further comprising a cooperation unit that cooperates.   When the user accesses the cooperation source information provision server again from the terminal device via the cooperation destination information provision server, the cooperation unit is configured to connect the user terminal based on the service indicated by the second session ID. The session management apparatus according to claim 2, wherein the various types of information are provided to the apparatus.   The session verification unit restricts or disables the use authority of the user in the information providing server when a verification result of at least one of the first session ID and the second session ID is not appropriate. The session management apparatus according to any one of claims 1 to 3.   When the second session ID verification result is appropriate and the first session ID cannot be verified, the session verification unit performs simple authentication for the user as compared to authentication at the time of login. The session management apparatus according to any one of claims 1 to 4, wherein the session management apparatus is characterized in that:   The said 2nd session ID transmission means records the said 2nd session ID in the parameter of net position information, and transmits to the said user's terminal device, The one in any one of Claim 1-5 characterized by the above-mentioned. Session management device.   A program that causes a computer to function as the session management device according to any one of claims 1 to 6.   A computer-readable recording medium having recorded thereon a program that causes the computer to function as the session management device according to any one of claims 1 to 6.

Images