Systems, methods and computer program products for authorizing common gateway interface application requests

• US 6,049,877 A
• Filed: 07/16/1997
• Issued: 04/11/2000
• Est. Priority Date: 07/16/1997
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: White, John Gregg
• Primary Examiner(s): Beausoliel, Jr., Robert W.
• Assistant Examiner(s): Baderman, Scott T.
• Application Number:
  US08/895,350
• Time in Patent Office: 1,000 Days
• Field of Search: 395/187.01, 713/201, 713/159, 713/172, 713/185, 709/203, 709/227, 709/228, 709/229, 709/302, 364/241.8
• US Class Current: 726/5
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 9/3234 involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853

Abstract

Systems, methods, and computer program products for authorizing a client request to a web server to execute a CGI application are provided. A web server receives a client request to execute a CGI application from a client. Authentication routines shared by a set of CGIs are executed by the requested CGI application to determine if the request is accompanied by an authentication token. If one is not received, then the CGI attempts to authenticate the client. Upon successful authentication, the CGI creates an authentication token using an authentication key and transmits the token to the client. The authentication token contains token data which is verifiable by the CGI application. Subsequent client requests to execute this or other CGI applications in this set of CGIs instrumented with the authentication routines are accompanied by the authentication token. The requested CGI executes its authentication routines to validate the authentication token and returns the requested output.

Claims

1. A method of authorizing a client request to a web server to execute any one of a plurality of CGI applications hosted by a web server having an application programming interface (API), wherein each CGI application in a set comprises a user authentication routine that executes independently from the web server API, wherein a client carries out the steps of:

sending a client request to execute a first CGI application within the set to the web server;

receiving from the web server an authentication token created by the first CGI application user authentication routine, wherein the authentication token authorizes execution of the first CGI application and each CGI application within the set for a predetermined time duration; and

responsive to receiving the authentication token created by the CGI application user authentication routine from the web server, storing the authentication token for use with subsequent CGI application execution requests to the web server; and

wherein the web server carries out the steps of;

receiving the client request to execute a first CGI application from the client;

responsive to receiving the client request, executing the first CGI application user authentication routine to create the authentication token containing information verifiable by the user authentication routine of each CGI application within the set;

executing the first CGI application; and

sending the authentication token created by the first CGI application user authentication routine to the client with results of the first CGI application execution.

2. A method according to claim 1, wherein the authentication token is an HTTP cookie.

3. A method of authorizing a client request to a web server to execute any one of a plurality of CGI applications within a first set hosted by a web server having an application programming interface (API), wherein each CGI application within the first set comprises a user authentication routine that executes independently from the web server API, said method comprising the steps of:

receiving a client request to execute a first one of the CGI applications in the first set;

responsive to receiving the client request, executing a CGI application user authentication routine to create an authentication token that can be shared by each of the CGI applications within the first set and that authorizes execution of any one of the CGI applications in the first set when subsequent client requests are made to execute any of the CGI applications in the first set during a predetermined time duration;

executing the first CGI application; and

sending the authentication token created by the CGI application user authentication routine to the client with results of the CGI application execution.

4. A method according to claim 3, further comprising the steps of:

receiving from the client the authentication token created by the CGI application user authentication routine with a subsequent client request to execute a second CGI applications in the first set;

responsive to receiving the subsequent client request and authentication token created by a CGI application user authentication routine, verifying via a user authentication routine within the requested CGI application that the received authentication token is valid; and

responsive to verifying that the received authentication token is valid, executing the second CGI application; and

sending results of the second CGI application execution to the client.

5. A method according to claim 3, wherein said step of executing the CGI application user authentication routine to create an authentication token comprises the steps of:

requesting the client to send user identification information to the web server;

receiving user identification information from the client; and

verifying the user identification information received from the client.

6. A method according to claim 3, wherein the authentication token is an HTTP cookie.

7. A data processing system for authorizing a client request to a web server to execute any one of a plurality of CGI applications within a set hosted by a web server having an application programming interface (API), wherein each CGI application within the set comprises a user authentication routine that executes independently from the web server API, said data processing system comprising:

means for receiving a client request to execute a first CGI application within the set from the client;

means, responsive to said client request receiving means, for executing a CGI application user authentication routine for the first CGI application to create an authentication token that authorizes execution of any one of the CGI applications within the set for a predetermined duration of time;

means for executing the first CGI application; and

means for sending the authentication token created by the CGI application user authentication routine to the client with results of the first CGI application execution.

8. A data processing system according to claim 7, further comprising:

means for receiving from the client the authentication token created by the CGI application user authentication routine with a subsequent client request to execute a second CGI application with the set;

means, responsive to said authentication token receiving means, for verifying via a CGI application user authentication routine for the second CGI application that the received authentication token is valid; and

means, responsive to said verifying means, for executing the second CGI application.

9. A data processing system according to claim 7, wherein said means for executing the CGI application user authentication routine to create an authentication token comprises:

means for requesting the client to send user identification information to the web server;

means, responsive to said means for requesting user identification information, for receiving user identification information from the client; and

means, responsive to said user identification information receiving means, for verifying the user identification information received from the client.

10. A data processing system according to claim 7, wherein the authentication token is an HTTP cookie.

11. A computer program product for authorizing a client request to a web server to execute any one of a plurality of CGI applications within a set hosted by a web server having an application programming interface (API), wherein each CGI application within the set comprises a user authentication routine that executes independently from the web server API, said computer program product comprising:

a computer usable medium having computer readable program code means embodied in said medium for receiving a client request to execute a first CGI application within the set from the client;

the computer usable medium having computer readable program code means embodied in said medium, responsive to said client request receiving means, for executing a CGI application user authentication routine for the first CGI application to create an authentication token containing information verifiable by any of the CGI applications within the set and that authorizes execution of any of the CGI applications in the set within a predetermined duration of time;

the computer usable medium having computer readable program code means embodied in said medium for executing the first CGI application; and

the computer usable medium having computer readable program code means embodied in said medium for sending the authentication token created by the CGI application user authentication routine to the client with results of the first CGI application execution.

12. A computer program product according to claim 11, further comprising:

computer readable program code means embodied in said medium for receiving from the client the authentication token created by the CGI application user authentication routine with a subsequent client request to execute a second CGI application;

computer readable program code means embodied in said medium, responsive to said authentication token receiving means, for verifying via a CGI application user authentication routine for the second CGI application that the received authentication token is valid; and

computer readable program code means embodied in said medium, responsive to said verifying means, for executing the second CGI application.

13. A computer program product according to claim 11, wherein said computer readable program code means embodied in said medium for executing the CGI application user authentication routine to create an authentication token comprises:

computer readable program code means embodied in said medium for requesting the client to send user identification information to the web server;

computer readable program code means embodied in said medium, responsive to said user identification information requesting means, for receiving user identification information from the client; and

computer readable program code means embodied in said medium, responsive to said user identification information receiving means, for verifying the user identification information received from the client.

14. A computer program product according to claim 11, wherein the authentication token is an HTTP cookie.