JP4989935B2 - Session management method, server used therefor, session management program, and recording medium recording the program - Google Patents

Description

  The present invention relates to a technique for session management in an application.

  Conventionally, a Web client (hereinafter referred to as “client” as appropriate) using a Web application provided by a Web server (hereinafter referred to as “server” as appropriate) is a desktop PC (Personal) connected to a wired LAN (Local Area Network). Computer). However, in recent years, with the widespread use of mobile terminals such as notebook PCs and mobile phones, there are increasing opportunities to use Web applications via wireless LANs, mobile phone networks, etc. using these as clients.

Servers and clients usually communicate using HTTP (HyperText Transfer Protocol). In that case, for example, as represented by an online shopping site or the like, the client makes a page request (request) to a plurality of Web pages.
Since this HTTP is a stateless protocol that only returns a response to a page request, on the server side, for each page request of the client, the identification of the client that sent it and the data that the client sent Need to hold. Therefore, the server has a session management function of identifying a client using an identifier and holding data transmitted from the client during a session in a memory, thereby holding data identifying the client.
FIG. 10 is a sequence diagram showing the flow of session management processing in a conventional Web application. Examples of known session management functions include functions provided by Microsoft's ASP (Active Server Pages), Sun Microsystems' JSP (Java (registered trademark) Server Pages), servlets, and the like.

In conventional session management, when a server receives a login page request (request) from a client that logs in to its own Web application, the server transmits a login page to the client. Thereafter, when the server receives a page request with authentication information from the client, the server verifies the authentication information from the client. Then, an object for session management (session data information object) is generated on the memory, an ID that is an identifier corresponding to the generated object is assigned, and the assigned ID is added to the header part of the response message to request "HTML1" that is the page that has been sent to the client.
The client inputs data to the form displayed on the browser screen based on “HTML1” included in the received response message, and transmits the next page request to the server. At that time, the ID added to the header part of the response message is added to the page request to the server.

  The server compares the ID included in the page request received from the client with the ID assigned to the object on its own memory, identifies the client, acquires the object within the valid period, and updates the update date and time. Update. Further, the data transmitted from the client is stored in the object corresponding to the ID, and the data is retained. After storing the data, the server adds an ID to the header part of the response message, and transmits the requested page “HTML2” to the client.

In conventional session management, the session validity period is the same as the object validity period in which data is stored on the server memory. For example, in FIG. 10, the valid period of the session is set to 5 minutes as an example.
In the middle of FIG. 10, after the server transmits “HTML2” to the client (S1001), when the client interrupts the page request for 6 minutes (6 minutes of no operation time) (S1002), the object is finally acquired. Since the valid period of the object exceeds 5 minutes after the update time (update date and time), the server invalidates the object on the memory (S1003). This terminates the client session (session timeout). After the object is invalidated, the server cannot acquire data held by the object. That is, since the session timeout and the loss of the data transmitted by the client are equivalent, when the client resumes the page request after the session timeout (S1004), the client logs in again and re-registers “HTML1”. "" And the data must be transmitted (S1005).

Patent Document 1 discloses a technique in which a session is continued by repeating transmission / reception of a page request at regular intervals after a user's initial page request in a client, regardless of a user's operation.
Patent Literature 2 creates a session ID for identifying a session, and transmits a cookie creation request message including the session ID to the client. Accordingly, a technique for identifying a client using a session ID is disclosed.
Japanese Patent Laying-Open No. 2003-233585 (FIG. 5) Japanese Patent Laying-Open No. 2005-10913 (FIG. 1)

  In the conventional session management function, the effective period of a session is set to be as short as several minutes in order to reduce security risks such as session hijacking that occurs when an ID is wiretapped and to release memory resources of the server.

In the technique described in Patent Document 1, when the browser of the client is terminated or the page request cannot be transmitted / received due to movement or the like, the data transmitted to the server is transmitted after the valid period of the session. It will be invalidated. In that case, the client needs to re-enter data in the input form and send it to the server.
In the technique described in Patent Document 2, the session validity period and client transmission data are managed as one object. In this case, in a mobile environment where the client's page request is frequently interrupted due to movement or the like, the server data is lost each time the session time-out occurs. The input form data must be re-entered and sent to the server.

In such an environment where session timeouts can occur frequently, data transmitted from the client to the server during the session is lost each time the session timeout occurs. Therefore, the client needs to retransmit the data of the input form every time, and the convenience of the Web application viewed from the client cannot be said to be high.
In order to solve this problem, a method of extending the valid period of the session indefinitely is conceivable, but in this method, in addition to wasting memory resources indefinitely, the security risk of the Web application is also increased. It is not valid.

  In view of the above problems, an object of the present invention is to improve convenience of a client while maintaining security in an application executed by communication between a server and a client.

In order to solve the above-described problem, one of the solutions according to the present invention is a first method in which, in an application executed by communication between a server and a client, the server manages session information based on a session request from the client. Information and second information for managing data received from the client are generated on the storage means, and each identifier (first and second identifier) for uniquely identifying each of the information and the validity period on the storage means And information to manage.
The server verifies the information for managing the validity period included in the first information and the second information at a predetermined interval, and invalidates the information that is out of the validity period by making it impossible to acquire.
Transmission / reception between the server and the client includes information to which each identifier is added. The server acquires valid first information or second information by collating with the identifier received from the client, and identifies the client. If the first information is invalid and the second information is valid, the server newly generates or updates the first information.
Note that “the object is valid” indicates that “the object can be properly used in the application program”, and “the object is invalid” indicates that “the object cannot be acquired in the application program (cannot be used)”.

  As a result, the server can continuously use the data held in the second information, and can transmit the information requested by the client even after the session time-out. As a result, it is not necessary to re-enter the data transmitted by the client every time a session times out, and convenience is improved.

  Further, when the first information is invalid and the second information is valid, the server authenticates the client before the first information is newly generated or updated, so that two identifiers are obtained. Security risks against unauthorized access such as session hijacking when wiretapped can be reduced.

  ADVANTAGE OF THE INVENTION According to this invention, the convenience of a client can be improved, maintaining a security in the application performed by a server and a client communicating.

The best mode for carrying out the present invention (hereinafter referred to as “embodiment”) will be described in detail.
In the description of the present embodiment, a shopping site Web application implemented using a Sun Microsystems servlet is used as an example. In the servlet, an object for managing the session validity period and holding data is realized as an object of a class implemented in the Java (registered trademark) language.

(First embodiment)
FIG. 1 is a diagram illustrating a configuration example of hardware and a network according to an embodiment of the present invention.
In this embodiment, the client 200 makes a page request (request) via the network 300 to the server 100 that provides a Web application to the browser of the client 200 that is a general computer. In the middle of the page request processing, the client 200 does not communicate with the server 100 for a considerable time (for example, movement), and the page request is interrupted. Assume that the process is resumed. Note that the client 200 may be a notebook PC, a portable terminal, or the like.

FIG. 2 is a block diagram illustrating functions of the server in FIG. 1 in the present embodiment. 2 will be described with reference to FIG. 1 as appropriate.
The server 100 includes a transmission / reception unit 110, a storage unit (storage unit) 120, and a control unit 150.
The transmission / reception unit 110 includes a communication interface, for example, and acquires information transmitted from the client 200 (see FIG. 1) via the network 300 (see FIG. 1) and outputs the information to the control unit 150. A process of acquiring information from 150 and transmitting information to the client 200 via the network 300 is performed.

The storage unit 120 includes a memory such as a RAM (Random Access Memory) that is a temporary storage area used for arithmetic processing, and an auxiliary storage area such as an HDD (Hard Disk Drive).
In the memory, validity period information 121 for storing the validity period of the object, and a session information object (first information) 122 and a data information object (first information) are generated as objects generated in response to a session (page) request of the client 200. Second information) 123.
The session information object 122 is an object that manages session information with the client 200.
The data information object 123 is an object that manages data transmitted from the client 200.

  Although not shown, the auxiliary storage area stores a Web application program, a session management program, a processing result of the control unit 150, and the like. The session management program according to the present embodiment is started when the Web application program is started. The session management program is read into the memory and the control unit 150 functions to execute the session management program.

In the present embodiment, when the Web application program of the server 100 is started, the server 100 presets the validity period of the session and data on the memory. At this time, the effective period of the session is an effective period on the memory of the object (session information object 122) that manages the session. When this period is exceeded, the object is invalidated. The data valid period is a period in which an object (data information object 123) for managing data transmitted from the client is retained in the memory. When this period is exceeded, the object is invalidated.
The information set as the valid period is read into the memory together with the session management program and used as the valid period information 121.

  FIG. 3 is a diagram illustrating an example of information stored in the validity period information. 3 will be described with reference to FIG. 2 as appropriate. The validity period information 121 stores information on the validity period of the session information object 122 (see FIG. 2) and the validity period of the data information object 123 (see FIG. 2). In the present embodiment, as an example, the session information object 122 will be described with an effective period of 1 minute and the data information object 123 with an effective period (holding period) of 10 minutes.

FIG. 4 is a diagram schematically illustrating the object. 4 will be described with reference to FIGS. 1 and 2 as appropriate.
FIG. 4A is a diagram showing a set of session information objects effective in memory in a table format. The session information object 122 stores information on the session ID, generation date / time, and update date / time. The session information object 122 is generated for each session of the client 200, and the update date and time is updated by the client identification unit 155 described later each time a page request is made from the client 200.

FIG. 4B is a diagram showing a set of data information objects effective in memory in a table format. The data information object 123 stores a data ID, a session ID corresponding to the data ID, a generation date / time, an update date / time, and data transmitted from the client 200. As with the session information object 122, the data information object 123 is updated by the client identification unit 155 described later every time the client 200 requests a page.
It should be noted that neither the session information object 122 in FIG. 4A nor the data information object 123 in FIG. 4B has its update date updated even if the valid period set in the valid period information 121 is exceeded. In this case, the object is invalidated by an object management unit 157 described later.

In this embodiment, “session information object is valid (on memory)” indicates a state where “the session information object can be properly used in the Web application program”, and “session information object is on (memory)”. “Invalid” indicates a state where “the session information object cannot be used in the Web application program”. Further, “data information object is valid (on memory)” indicates a state where “data information object is properly usable in the Web application program”, and “data information object is invalid (on memory)” This indicates a state where the “data information object cannot be used in the Web application program”.
Here, “unusable” refers to a state in which the server 100 cannot acquire the object, or a state in which data cannot be utilized even if acquired, and for example, setting or deleting an object that is inaccessible to an object on the memory. It is possible to do it.

  Returning to FIG. 2, the control unit 150 is configured by, for example, a CPU (Central Processing Unit) and the like, and controls the transmission / reception unit 110, and performs authentication of the information acquired through the transmission / reception unit 110, session management, and the like. A client authentication unit 151, an object generation unit (information generation unit) 152, an ID generation unit (identifier generation unit) 153, a validity period management information generation unit 154, a client identification unit 155, a data storage unit 156, an object management unit ( Information management unit) 157.

The client authentication unit 151 verifies authentication information transmitted from the client 200 and performs authentication.
The object generation unit 152 includes a session information generation unit 1521 and a data information generation unit 1522, and generates an object on the storage unit 120 (memory) of the server 100. Specifically, the session information generation unit 1521 generates a session information object 122 that manages the session of the client 200, and the data information generation unit 1522 generates a data information object 123 that holds data transmitted from the client 200.

  The ID generation unit 153 includes a session ID generation unit 1531 and a data ID generation unit 1532, and generates and assigns an ID (identifier) that uniquely identifies each object generated by the object generation unit 152. Specifically, the session ID generation unit 1531 gives a session ID (first identifier) to the session information object 122, and the data ID generation unit 1532 assigns a data ID (second identifier) to the data information object 123. Give. The generated ID is exchanged with the client 200 using a technique such as Cookie.

  The effective period management information generation unit 154 includes a session effective period management information generation unit 1541 and a data effective period management information generation unit 1542, and information for managing the effective period of the object for each object generated by the object generation unit 152 Are generated and given respectively. Specifically, the session valid period management information generation unit 1541 updates the session information object 122 by the client identification unit 155 when the server 100 acquires the date and time generated on the memory. The data validity period management information generation unit 1542 gives the date and time generated on the memory to the data information object 123, and the update date and time updated by the client identification unit 155 when the object is acquired by the server 100. Give. When an object is generated, the same date and time as the generation date and time is set as the update date and time.

The client identification unit 155 compares the session ID and data ID transmitted from the client 200 with the session ID and data ID assigned to the object in the storage unit 120 of itself, and acquires the associated object. To identify the client 200. Further, the client identification unit 155 updates the update date / time of the acquired object to the latest date / time when the object was acquired by the server 100.
The data storage unit 156 stores the data transmitted from the client 200 in the data information object 123.

The object management unit 157 includes a session information management unit 1571 and a data information management unit 1572, and determines whether the session information object 122 and the data information object 123 in the storage unit 120 are valid on the memory and the information of the valid period information 121. Management is performed based on the update date and time of each object.
Specifically, for example, when the session validity period is set to 1 minute in the validity period information 121, the session information management unit 1571 indicates that the session information object 122 (see FIG. 4A) is valid. Whether or not every minute. Whether or not it is valid is determined by determining whether or not the update date and time of the session information object 122 has been updated before the valid period exceeds 1 minute. If the update date / time is not updated even if the valid period exceeds one minute, the session information object 122 is invalidated.
If the data validity period is set to 10 minutes, the data information management unit 1572 verifies whether the data information object 123 (see FIG. 4B) is valid every 10 minutes. Whether or not it is valid is determined by determining whether or not the update date and time of the session information object 122 has been updated before the valid period of 10 minutes is exceeded. If the update date / time is not updated even after the valid period of 10 minutes is exceeded, the data information object 123 is invalidated.
Note that it is only necessary that the information on the invalid object cannot be acquired by the server 100. In the present embodiment, a method for deleting the object will be described as an example.

  FIG. 5 is a sequence diagram illustrating information transmitted and received between the client and the server and the flow of each process in the present embodiment. A description will be given along FIG. 5 with reference to FIGS. In the present embodiment, as described above, the client 200 issues a page request to the server 100 that provides the Web application via the network 300. Then, it is assumed that the page request is resumed to the server 100 as the client 200 </ b> A after the page request is interrupted without performing communication with the server 100 for a considerable time due to movement or the like during the page request processing.

  First, the client 200 requests a login page from the server 100 (S31), and based on the request, the server 100 transmits a login page requesting authentication information to the client 200 via the transmission / reception unit 110 (S32). ). As this login page, for example, a screen for inputting user information and authentication information such as a password can be considered.

  The client 200 inputs authentication information to the received login page and transmits it to the server 100 (S33). As a result, the first page is requested from the client 200 to the server 100 as a session request.

  The server 100 verifies the authentication information received from the client 200 by the client authentication unit 151 (S34). The verification method is not particularly limited. For example, authentication information (user information, password, etc.) that permits processing is stored in the storage unit 120 in advance, and verification is performed by checking with the stored information. A way to do this is conceivable.

As a result of the verification, if the server 100 is authenticated, that is, if it can be confirmed that the authentication information from the client 200 is valid, the server 100 uses the object generation unit 152 to store two objects (session information object 122, data information) on the storage unit 120. An object 123) is generated, and an ID (session ID, data ID) is generated by the ID generation unit 153 and assigned to each object (S35). Further, the valid period management information generation unit 154 gives the generation date and the update date to each object (see FIGS. 4A and 4B).
Specifically, the session information generation unit 1521 of the object generation unit 152 generates the session information object 122, and the data information generation unit 1522 generates the data information object 123. For the sake of explanation, it is assumed that the session information object 122 generated here is (P1) and the data information object 123 is (D1).
Then, the session ID generation unit 1531 generates a session ID for the session information object 122 (P1) and assigns the session ID to the session information object 122 (see “AE032”: FIG. 4A). Further, the data ID generation unit 1532 generates a data ID for the data information object 123 (D1) and assigns the data ID to the data information object 123 (see “DB5847”: FIG. 4B). For the sake of explanation, the session ID assigned to the session information object 122 (P1) is “ID1”, and the data ID assigned to the data information object 123 (D1) is “ID2”, which are also shown in FIG.
The data ID generation unit 1532 assigns the corresponding session ID information to the data information object 123 in order to associate the session ID with the data ID (see FIG. 4B).
Furthermore, the session valid period management information generation unit 1541 gives the generation date and the update date to the session information object 122 (see FIG. 4A). The data valid period management information generation unit 1542 gives the generation date and the update date to the data information object 123 (see FIG. 4B).

  As a result of the verification in step S34, if the server 100 is not authenticated, the server 100 may return to step before step S32 and transmit a message indicating that the authentication has not been performed to the client 200.

  After generating two objects in step S35 and adding ID and valid period information, the server 100 adds a session ID (ID1) and a data ID (ID2) to the response message, and sends them to the client via the transmission / reception unit 110. The requested page is transmitted (S36: HTML1 transmission). “HTML1” is information for displaying a product selection screen, for example.

FIG. 6 is a diagram illustrating an example of information transmitted and received between the client and the server in the present embodiment.
FIG. 6A is a diagram illustrating information transmitted from the server to the client in step S36. Here, two IDs are added to the Set-Cookie field of the response message. That is, the session ID (“AE032”) is added to the reference numeral 601 in FIG. 6A, and the data ID (“DB5847”) is added to the reference numeral 602. Information to which these two IDs are added is transmitted from the server 100 to the client 200. The session ID and data ID correspond to the information in FIG.

  Note that the process in which the valid period management information generating unit 154 assigns the generation date and the update date and time (information for managing the valid period) to each object in step S35 may be performed after the transmission process in step S36.

  Returning to FIG. 5, in step S <b> 37, the client 200 displays “HTML1” included in the response message transmitted from the server 100 on the screen. Then, the client 200 requests the next page by inputting necessary data (for example, a code of a product to be purchased) in the form on the displayed screen and transmitting it to the server 100 (S37).

FIG. 6B is a diagram illustrating information transmitted from the client to the server in step S37 of FIG.
According to FIG. 6B, a session ID is added at 603 and a data ID is added at 604 in the Cookie field of the request message transmitted from the client 200 to the server 100. In step S36, these IDs include the session ID (“AE032”: see reference numeral 601 in FIG. 6A) included in the response message received from the server 100 and the data ID (“DB5847”: FIG. 6A). ) (See reference numeral 602).
Further, the data selected by the client 200 (for example, the product code “book_001”) is added to the message data portion indicated by reference numeral 605.

Returning to FIG. 5, when the server 100 receives the information corresponding to the page request from the client 200, the server 100 stores two IDs (ID 1 and ID 2) included in the information transmitted from the client 200, and its own storage unit 120. The ID stored in the object is collated by the client identification unit 155 to acquire the object. Further, the client identification unit 155 updates the update date and time of the acquired object at the time when the object is acquired by the server 100.
More specifically, the client identification unit 155 stores the session information object 122 and the data information object 123 in the storage unit 120 (memory) based on ID1 (session ID) and ID2 (data ID) transmitted from the client 200. The object that matches each ID that has been searched is searched and collated. If a matching object exists, the object is acquired. Thereby, the client 200 is identified as 100 by the server. As a result of the search, if both objects corresponding to the two IDs (ID1, ID2) received from the client 200 are valid (that is, the server can acquire the session information object 122 and the data information object 123), the client The identification unit 155 updates the update date and time in the session information object 122 and the data information object 123 (S38: ID collation, object acquisition, update).

  Then, the server 100 stores the data (product code “book_001”) in the data information object 123 by the data storage unit 156 (S39). In the object in the first row in FIG. 4B, data “book_001” (reference numeral 605 in FIG. 6B) transmitted from the client 200 to the server 100 is held as data.

  Thereafter, the server 100 generates “HTML2” as the next page and transmits it to the client 200 via the transmission / reception unit 110 (S40: HTML2 transmission). “HTML2” is, for example, a page for displaying a list of products scheduled to be purchased and for changing the quantity or confirming the product. In the response message transmitted at this time, the session ID (“AE032”) and the data ID (“DB5847”) are added as in step S36.

The client 200 displays “HTML2” transmitted from the server 100 on a browser screen, and prompts for information input (S41).
The client 200 interrupts the process for 2 minutes due to movement or the like while inputting the form (for example, quantity) on the displayed screen.

The object management unit 157 of the server 100 determines whether two types of objects (session information object 122 and data information object 123) are valid on the storage unit 120 (memory), respectively, and the update date and time given to the object, Based on the information stored in the validity period information 121, the verification is performed periodically (1 minute for the session information object 122 and 10 minutes for the data information object 123), and the object whose validity period is exceeded is invalidated.
In this embodiment, since the session valid period is set to 1 minute, the server 100 has not updated the update date and time for 1 minute from the update by the last page request from the client 200 for the session information object 122. In this case, the session information management unit 1571 of the object management unit 157 invalidates the object. Here, the session information object 122 (P1) is invalidated. As a result, a session timeout occurs, and the server 100 cannot acquire information on the invalidated object.

FIG. 7 is a diagram schematically illustrating a state at the time of session timeout accompanying the expiration of the valid period of the session information object 122 (P1) of the information illustrated in FIG. FIG. 7A is a diagram showing a set of session information objects in a table format, and FIG. 7B is a diagram showing a set of data information objects in a table format.
According to FIG. 7A, the object with the session ID “AE032” has been deleted because it has been invalidated at the end of the validity period. In FIG. 7B, the data information object 123 (D1) is not invalidated because it is within the valid period.

  Returning to FIG. 5, the client 200 </ b> A completes the data input to the form two minutes after the movement or the like, and transmits the next page request including the input data to the server 100 (S <b> 42). At this time, the client 200A also adds two IDs (ID1, ID2) and transmits the same as in step S37.

When the server 100 receives the page request from the client 200, the server 100 uses the two IDs (ID1, ID2) included in the information transmitted from the client 200A and the ID assigned to the object in the storage unit 120 of itself. The client identification unit 155 performs collation.
In the server 100, with the expiration of the valid period, the session has already timed out, and the session information object 122 (P1) has been invalidated. Therefore, first, the server 100 determines that the session information object 122 corresponding to ID1 received from the client 200A cannot be acquired. Then, the data information object 123 including the data ID corresponding to ID2 received from the client 200A is searched, and the data information object 123 (D1) is checked by matching the session ID corresponding to this data ID with ID1 received from the client 200A. ) To identify the client 200A.
Accordingly, it can be seen that the data information object 123 (D1) corresponding to the received ID2 is valid, and the session information object 122 (P1) corresponding to ID1 is invalid (exceeding the valid period). The client identification unit 155 of the server 100 updates the update date and time of the valid data information object 123 (D1) (S43: ID verification, object acquisition, update).

  The server 100 generates an object for managing new session information on the storage unit 120 using the object generation unit 152, and assigns a session ID using the ID generation unit 153 (S44). Specifically, the session information generation unit 1521 of the object generation unit 152 generates a session information object 122 (P2). Then, the session ID generation unit 1531 of the ID generation unit 153 generates a session ID (ID1 ′) for the newly generated session information object 122 (P2) and assigns it to the session information object 122 (P2). Accordingly, the server 100 uses the newly generated session ID (ID1 ′) for future session identification of the client 200A. Further, the server 100 assigns the generation date / time and the update date / time to the session information object 122 (P2) by the effective period management information generation unit 154.

  The client identification unit 155 of the server 100 stores the data (for example, quantity) included in the information transmitted from the client 200A in the data of the data information object 123 (D1) by the data storage unit 156 (S45). .

  Then, the client identification unit 155 of the server 100 changes the session ID stored in the data information object 123 (D1) to the session ID newly generated in step S44 (S46). Note that the processing of steps S45 and S46 may be performed in the reverse order.

FIG. 8 is a diagram illustrating the state of the information illustrated in FIG. 4 at the end of the session. FIG. 8A is a diagram showing a set of session information objects in a table format. FIG. 8B is a diagram showing a set of data information objects in a table format.
FIG. 8A shows that a new session information object 122 (P2) is generated by receiving a page request from the client 200 after the validity period of the session information object 122 (P1) ends. .
According to FIG. 8B, the session ID of the data information object 123 (D1) is changed to the newly generated “ZY999”. Further, as indicated by reference numeral 801, the quantity data stored in step S45 is stored as “3” after “book_001”.

  Returning to FIG. 5, the server 100 transmits “HTML3” as the next page to the client 200 </ b> A via the transmission / reception unit 110 (S <b> 47: HTML3 transmission). “HTML3” is a page on which, for example, purchased products, quantities, amounts, etc. are displayed and settlement is made. The response message transmitted at this time includes the session ID (“ZY999”) of the newly generated session information object 122 (P2) and the data ID (“DB5847”) of the corresponding data information object 123 (D1). Added.

FIG. 6C is a diagram illustrating an example of information (“HTML3”) transmitted from the server to the client in step S47.
According to FIG. 6C, the information added to the Set-Cookie field in the response message transmitted from the server 100 to the client 200A is newly generated at reference numeral 606 as compared with FIG. A session ID (“ZY999”) is added. In other words, the session ID added as “AE032” in FIG. 6A is changed to “ZY999” in FIG. 6C and added.

  The client 200A displays “HTML3” transmitted from the server 100 on the browser screen (S48). Since the subsequent processing is the same as the processing in step S37 or step S41, the description thereof is omitted.

  In the present embodiment, since the data information object 123 has a valid period of 10 minutes, if there is no update for 10 minutes since the update by the last page request, the server 100 performs the data information management of the object management unit 157. The unit 1572 invalidates the data information object 123 (D1).

  When the page request is received from the client 200A after the data information object 123 (D1) becomes invalid, that is, when the page request in step S48 is made after exceeding 10 minutes from the previous update, A valid data information object 123 that matches the received data ID (ID2) cannot be acquired. There is also a possibility that the received data ID is invalid. Therefore, when the data information object 123 is invalid or the data IDs do not match, the server 100 desirably performs the same operation as the initial page request (S32, S34 to S36).

  According to the present embodiment described above, two objects, an object for managing a session and an object for managing data, are used. Then, by shortening the session validity period and setting the data retention period as the minimum time necessary for maintaining the convenience of the Web application, the client 200 sends a page request to the server 100 after the session time-out. However, if the page request is within the data holding period, the client 200 can continue the page request processing using the held data. Thereby, the convenience of the Web application for the client 200 can be improved.

  Further, memory resources associated with session and data processing are also invalidated after a certain period of time. Here, if the object is deleted as invalidation, the load of the memory resource is reduced and efficient use is possible.

(Second Embodiment)
FIG. 9 is a sequence diagram showing information transmitted and received between the client and the server and the flow of each process in the second embodiment. The second embodiment is different from the first embodiment in that an authentication process is added between steps S43 and S44 (the double line encircled portion in FIG. 9).
9 will be described with reference to FIGS. 1 to 8 as appropriate. In FIG. 9, the processing up to step S43 is the same as that in the first embodiment, and thus repeated illustration and description are omitted as appropriate.

In step S43, when the server 100 receives the information transmitted from the client 200A, the server 100 assigns the two IDs (ID1, ID2) included in the information transmitted from the client 200A and the object in its own storage unit 120. The client identification unit 155 checks the ID that has been set.
As described in the first embodiment, it can be understood that the session information object 122 (P1) corresponding to the received ID1 is invalidated and the data information object 123 (D1) corresponding to ID2 is valid here. . The server 100 acquires the valid data information object 123 (D1), identifies the client, and updates the update date and time.

Subsequently, the server 100 transmits a login page to request the client 200A to transmit authentication information again (S431).
The client 200A inputs authentication information to the received login page and transmits it to the server 100 (S432). As a result, the next page is requested from the client 200 to the server 100.

The server 100 verifies the authentication information received from the client 200A by the client authentication unit 151 (S433).
As a result of the verification, if the server 100 is authenticated, that is, if the authentication information from the client 200A is confirmed to be valid, the server 100 stores session information for managing the validity period of a new session on the storage unit 120 in step S44. The object 122 (P2) is generated by the object generation unit 152. The subsequent processing is the same as in the first embodiment.

  As a result of the verification in step S433, if the authentication is not successful, the process may return to step S431 and a message indicating that the authentication was not successful may be transmitted to the client 200A.

  The processing of steps S431 and S433 in the server 100 is the same processing as steps S32 and S34 of the first embodiment, and the processing of step S432 in the client 200A is the same processing as step S33 of the first embodiment.

According to the second embodiment described above, when a page request is transmitted from the client 200A to the server 100 after the session time-out, the server 100 authenticates the client 200A, whereby the validity of the client 200A is verified. Confirm. Then, when the client 200A is authenticated, the server 100 generates an object (session information object 122) that manages the validity period of the new session.
Thereby, even when information transmitted / received between the client 200 and the server 100 is eavesdropped, security risks such as session hijacking can be reduced, and security can be improved compared to the first embodiment. . According to the second embodiment, the processing in steps S431 to S433 (see FIG. 9) is necessary, but the data stored in steps S39 and S45 in the server 100 is not wasted. That is, even after the session valid period ends, if it is within the data valid period, the client 200A newly inputs and transmits the data input in steps S37, S41, and S42 (see FIG. 5) and transmitted to the server 100. Since no additional work is required, the client 200A can continue to use the data transmitted to the server 100, and convenience is improved.

  The server 100 can also be realized by executing a session management program that causes a general computer to execute the above-described steps S32, S34 to S36, S38 to S40, S43 to S47, S431, and S433. This program can be distributed via a communication line, or can be written and distributed on a recording medium such as a CD-ROM or a semiconductor chip. As for the program installation, the program may be downloaded and installed via a network via a communication device.

As mentioned above, although an example was shown about suitable embodiment of the present invention, the present invention is not limited to the above-mentioned embodiment.
For example, in this embodiment, in the server, the valid period of each object is set in advance as valid period information, and the object management unit updates the session information object and the data information object based on the set valid period. The date and time was verified, but not limited to this, the session information object and data information object are provided with information indicating the validity period, and the validity period is exceeded by updating the validity period for each page request from the client. You may invalidate the selected object.
It is also conceivable to adopt a method of including information indicating the validity period in an ID (identifier) transmitted and received between the server and the client. In this case, the server may determine whether or not the object is within the valid period using information indicating the valid period included in the ID transmitted from the client.

  In the present embodiment, the server has been described as deleting the object upon invalidation at the end of the validity period of each object. However, the present invention is not limited to this, and invalidation of the session information object is not performed without deleting the object. May not be acquired. And when ID is collated using a data information object, it is good also as making a session information object usable by updating a session information object from the state which cannot be acquired, and updating ID. In addition, it is good also as a structure provided with two or more servers, for example, and can change suitably in the range which does not deviate from the meaning of this invention.

It is a figure which shows the structural example of the hardware and network in embodiment of this invention. It is a block diagram which shows the function of the server in FIG. It is a figure which shows the example of the information stored in effective period information. It is a figure which shows an object typically. FIG. 4A is a diagram showing a set of session information objects effective in memory in a table format. FIG. 4B is a diagram showing a set of data information objects effective in memory in a table format. It is a sequence diagram which shows the information transmitted / received between the client and server in this embodiment, and the flow of each process. It is a figure which shows the example of the information transmitted / received between the client and server in this embodiment. FIG. 6A shows information transmitted from the server to the client. FIG. 6B shows information transmitted from the client to the server. FIG. 6C shows information transmitted from the server to the client. FIG. 5 is a diagram schematically illustrating a state at the time of session timeout accompanying the expiration of the valid period of the session information object in the information illustrated in FIG. 4. FIG. 7A is a diagram showing a set of session information objects in a table format. FIG. 7B is a diagram showing a set of data information objects in a table format. FIG. 5 is a diagram illustrating a state at the end of a session of the information illustrated in FIG. 4. FIG. 8A is a diagram showing a set of session information objects in a table format. FIG. 8B is a diagram showing a set of data information objects in a table format. It is a sequence diagram which shows the information transmitted / received between the client and server of 2nd Embodiment, and the flow of each process. It is a sequence diagram which shows the flow of a session management process in the conventional web application.

Explanation of symbols

100 server 110 transmission / reception unit 120 storage unit (storage unit)
121 Valid period information 122 Session information object (first information)
123 Data information object (second information)
150 Control Unit 151 Client Authentication Unit 152 Object Generation Unit (Information Generation Unit)
1521 Session information generation unit 1522 Data information generation unit 153 ID generation unit (identifier generation unit)
1531 Session ID generation unit 1532 Data ID generation unit 154 Effective period management information generation unit 1541 Session effective period management information generation unit 1542 Data effective period management information generation unit 155 Client identification unit 156 Data storage unit 157 Object management unit (information management unit)
1571 Session information management unit 1572 Data information management unit 200, 200A Client 300 Network

Claims (6)

In an application executed by communication between a server and a client, the server is a session management method for managing a session with the client,
The server
Based on the session request received from the client, first information for managing information on the session with the client, and second information for managing data received from the client are generated in a predetermined storage unit,
The first information is given a first identifier that uniquely identifies the first information, the second information is a second identifier that uniquely identifies the second information, and Giving the first identifier of the first information corresponding to the second information,
Sending the assigned first and second identifiers to the client that requested the session;
For each of the first information and the second information, information for managing the validity period is given,
Information for managing an effective period included in the first information and the second information is verified at a predetermined interval, and the storage unit stores the first information or the second information outside the effective period. Disabling the first information or the second information by making it impossible to obtain from
Based on the first identifier and the second identifier included in the information received from the client, referring to the storage means, and at least obtaining valid second information corresponding to each identifier To identify the client,
When the first information corresponding to the received first identifier is invalid and the second information corresponding to the received second identifier is valid, the first information is newly generated or Updated,
A first identifier corresponding to the newly generated or updated first information is newly generated or updated and given to the first information;
Giving information for managing the validity period to the newly generated or updated first information,
The session management method characterized by transmitting the newly generated or updated first identifier together with the corresponding second identifier to the client. The server
If the first information corresponding to the received first identifier is invalid and the second information corresponding to the received second identifier is valid, the client is authenticated,
When the authentication is successful, the first information is newly generated or updated,
A first identifier corresponding to the newly generated or updated first information is newly generated or updated and given to the first information;
Giving information for managing the validity period to the newly generated or updated first information,
The session management method according to claim 1, wherein the newly generated or updated first identifier is transmitted to the client together with the corresponding second identifier. In an application executed by communication between a server and a client, the server manages a session with the client,
Based on a session request received from the client, information generation for generating first information for managing information on a session with the client and second information for managing data received from the client in a predetermined storage unit And
The first information is given a first identifier that uniquely identifies the first information, the second information is a second identifier that uniquely identifies the second information, and An identifier generating unit for assigning the first identifier of the first information corresponding to the second information;
An effective period management information generating unit that provides information for managing an effective period for the first information and the second information,
A transmission / reception unit for transmitting the assigned first identifier and the second identifier to the client having requested the session;
Information for managing an effective period included in the first information and the second information is verified at a predetermined interval, and the storage unit stores the first information or the second information outside the effective period. An information management unit that invalidates the first information or the second information by making it impossible to acquire from
Based on the first identifier and the second identifier included in the information received from the client, referring to the storage means, and at least obtaining valid second information corresponding to each identifier A client identification unit for identifying the client,
When the first information corresponding to the received first identifier is invalid and the second information corresponding to the received second identifier is valid, the information generating unit Create or update a new
The identifier generation unit newly generates or updates a first identifier corresponding to the newly generated or updated first information, and gives the first information to the first information,
The effective period management information generation unit gives information for managing an effective period to the newly generated or updated first information,
The server having a function in which the transmission / reception unit transmits the newly generated or updated first identifier together with the corresponding second identifier to the client. Client authentication for authenticating the client when the first information corresponding to the received first identifier is invalid and the second information corresponding to the received second identifier is valid Part
When the authentication is successful, the information generation unit newly generates or updates the first information,
The identifier generation unit newly generates or updates a first identifier corresponding to the newly generated or updated first information, and gives the first information to the first information,
The effective period management information generation unit gives information for managing an effective period to the newly generated or updated first information,
The server according to claim 3, wherein the transmission / reception unit has a function of transmitting the newly generated or updated first identifier together with the corresponding second identifier to the client. A session management program for causing a computer to execute the session management method according to claim 1.   A computer-readable recording medium on which the session management program according to claim 5 is recorded.

Images