JP2001160033A - SCREEN TRANSITION MANAGEMENT METHOD IN WWW(World Wide Web) APPLICATION - Google Patents

Abstract

PROBLEM TO BE SOLVED: To judge the validity of a request for the transition of a task screen from plural clients in a task, using a WWW. SOLUTION: When a request is issued from a client, an one-time ID generated by a preliminarily decided rule is embedded with 'hidden' being one of the attributes of the <INPUT> tag of an HTML. This one-time ID is constituted of all alphabets, numbers, and the other special characters valid on a unique WWW as a system, and the ID itself is constituted as the string of meaningless random alphabet, numbers, and the other special characters. Thus, the ID is related with the log-in ID of a client by a task program on a server (and a host), so that it is possible to judge which client and which task screen the communication is operated from.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to screen transition management on the WWW, and more particularly to a method for managing screen transitions in conventional one-transmission complete WWW communication.

[0002]

2. Description of the Related Art A characteristic of a WWW browser is that a free screen transition such as returning to a previous screen or proceeding to the next screen can be performed by a client internal process. Therefore, from the business screen 1 to the business screen 2, the business screen 2
In the business process that is established only by sequentially transiting from the business screen to the business screen 3, a “return” operation or the like is performed to retransmit previously sent items from the client to the server (and the host). Inconsistency may occur in the business process of

[0003]

An object of the present invention is to determine the validity of a business screen transition request from a plurality of clients in a business using the HTML format on the WWW.

[0004]

According to the present invention, the above problem is solved by giving an ID (referred to as a one-time ID) for each business screen as information hidden in the business screen responding to the client. Solved. This method embeds a one-time ID generated according to a predetermined rule in a business screen responding to a request from a client, using hidden, which is one of the attributes of an <INPUT> tag of HTML. It is something to keep. The one-time ID here is a unique WW for the system.
It consists of all alphabets, numbers, and other special characters valid on W. The ID itself is a sequence of meaningless random letters, numbers, and other special characters, but the server (and host) By associating the communication with the login ID of the client by the above business program, it is possible to determine from which business screen of which client the communication is performed.

[0005]

FIG. 1 is a flow chart showing a method of applying the present invention. FIG. 1 shows a process of responding to a corresponding business screen 1 from a login request from a WWW browser (client) in business processing using the WWW, and further from the business screen 1 to a transition to a business screen 2 as a result of the business processing. Here, the business screen is basically the one described in the HTML format.

First, a client login request screen C
From step 1, the user inputs a user ID and a password for the corresponding job, and makes a login request C2. The server (and the host) that has received the login request C2 performs a user ID and password determination process S1, issues a one-time ID1 if valid, and registers it on the screen transition management table (S2). The one-time ID here is an arbitrary number of digits defined by the system and consists of all alphabetic characters, numbers, and other special characters that are valid on the WWW. The ID itself has a special meaning. Make it not exist.

FIG. 2 shows an image of the screen transition management table. The screen transition table contains the user ID for which the client has requested login, and the generated one-time ID.
Register

Next, in S3, the first business screen 1 is responded to the client after performing the business processing 1 (login processing). At this time, the information hidden in the business screen 1 is returned in S2. The issued one-time ID1 is embedded.

FIG. 3 shows a method of embedding the issued one-time ID in the business screen. In the HTML format, input information is usually transmitted and received as form data. An <INPUT> tag is used as an input field for inputting form data. One-time ID is one of the attributes of the <INPUT> tag, and is embedded in a business screen with a hidden invisible field hidden. Sent to the client. One-time I at client
A business screen with D is displayed, but the one-time ID is not displayed on the screen because it is embedded in the invisible field.

[0010] The user inputs items necessary for the business on the business screen 1 (C4) displayed on the client, and after completing the input, makes a business processing request C5 to the server (and the host). At this time, as the form data transmitted to the server (and the host), in addition to the information input by the user, the one-time ID 1 embedded in S3 as hidden information is also transmitted.

Next, as a determination process in S4, the server (and the host) compares the one-time ID transmitted from the client with the one-time ID registered in the screen transition management table in response to the business process request C5. If they are the same, the request is determined to be valid. On the other hand, in the business process request C5, when the one-time ID transmitted from the client and the one-time ID registered in the screen transition management table are different, it is considered that an invalid screen transition has been performed in the client, and the client Error screen C indicating that
Respond 6.

In the determination process of S4, the one-time ID
Is determined to be valid, the server (and the host) generates a one-time ID 2 for embedding in the business screen 2 to be transmitted to the client next, and then registers it in the screen transition management table in step S5. A normal business process is performed in the process of S6 by replacing the previous one-time ID1, and a business screen 2 in which the newly generated one-time ID2 is embedded is generated and responded to the client.

Similarly, in the server (and the host), a one-time ID is provided each time a business process request is made from a client.
Is determined, and if it is valid, a new one-time ID is generated, replaced with the previous one-time ID registered in the screen transition management table, and embedded in the business screen.
Send it to the client and the client will see the correct business screen.

[0014]

According to the present invention, when managing screen transitions in business processing, the server (and host) must keep track of terminal numbers and business screen transition order.
In the WWW, it was difficult to control the transition order of terminal numbers and business screens. In this method, since the unique one-time ID is embedded in the business screen, it is possible to perform business processing while referring to the one-time ID and conscious of the terminal regardless of the terminal number. In addition, since the one-time ID is newly generated uniquely each time transmission / reception occurs, it is possible to maintain consistency from the free screen transition in the internal processing of the client which is a characteristic of the WWW browser just by referring to the one-time ID. It is possible. Further, since the one-time ID is made up of meaningless alphabetic characters, numbers, and special character strings, it is possible to cope with intentional theft of the ID by a third party.

[Brief description of the drawings]

FIG. 1 is a diagram showing a flow of business screen transition to which the present invention is applied.

FIG. 2 is a diagram showing a screen transition management table image used in the present invention.

FIG. 3 is a diagram showing an example of embedding a business screen of a one-time ID in the present invention.

Claims (1)

[Claims] 1. A method for judging whether a business screen transition request from a WWW browser is valid or not, wherein a user ID and a password for which a login request has been made from the WWW browser. A business screen transition management method, comprising: a means for determining whether a screen transition request from the user is valid when the screen transition request is valid.