US 7,895,446 B2Grant
Secure data exchange between data processing systems
Issue Date:2011-02-22
•30 Claims
•6 Drawing Sheets
Abstract
A data transfer method performed at a proxy server includes intercepting a data request from a client computer that is directed to a target server, encrypting profile information, augmenting the data request by adding the encrypted profile information to the data request, and sending the augmented data request to the target server. A data transfer method that is performed at an information server includes receiving a data request from a proxy server, extracting profile information added to the data request by the proxy server, using the extracted profile information to generate a response, and sending the response to the proxy server.
Metadata
Assignee
- AOL Inc.
Inventors
- Larry T. Harada
- Mark A. Dolecki
- Christopher S. Purdum
- C. Hudson Hendren, III
Application Information
Application Number:US 11/535,056
Filing Date:2006-09-25
Priority Date:1999-06-01
Art Unit:2432
Classifications
IPC:
G06F21/00G06F17/30
Patent Drawings (6 sheets)
Description
Cross Reference to Related Applications
[0001] This application is a continuation of pending U.S. application Ser. No. 09/323,415, filed Jun. 1, 1999, and titled “Secure Data Exchange Between Data Processing Systems” which is incorporated herewith by reference.
Background
[0002] FIG. 1 shows a computer network 100 that includes both client computers 111-113 and server computers 131-133. The network 100 also includes data connections that allow the client computers to communicate with the servers. Those data connections include access connections 114-116, a service provider's point of presence (POP) 110, network 120, proxy server 117, and network 130. POP 110 includes data communications equipment that allows a client computer 111-113 to connect to the network 120. For example, POP 110 may include dial-up modem banks, cable modem banks, a T1 interface, wireless communications equipment, or other data transmission equipment.
[0003] After a client computer 111-113 has been connected to the network 120 (through POP 110) it may exchange data with other computers on the network 120. Computers on different networks 120 and 130 also can exchange data with each other by sending their data request to proxy server 117 which, in turn, can forward their request to the destination computer, obtain a response from the destination, and return the response to the requesting computer.
[0004] The servers 131-133 and clients 111-113 may communicate with each other using the hypertext transfer protocol (HTTP). HTTP is a data communications protocol that is used by web browser programs (such as Microsoft Internet Explorer and Netscape Navigator) to communicate with web server applications (such as Microsoft Internet Information Server and Netscape Server). Thus, by executing a web browser, a client computer 111-113 can exchange data with a server 131-133 that is executing a web server application.
[0005] When a web server receives a HTTP data request from a browser, a web server application, such as a Common Gateway Interface (CGI) script, may be used to query databases, customize responses, and/or perform other processing used to generate a response. The web server application may need data about the client computer, the browser, its user, and/or other data in order to complete its processing of the data request. For example, a web server application may provide customized weather information based on a user's home address. The web application may obtain the user's address information by sending a data input form to the browser and receiving a user's response that contains the needed information. A web server application also may obtain needed data from web server environmental variables that are populated by data in HTTP header fields, by a web server, and/or by a web server sub-component. For example, a CGI script's response to a data request may depend on the type of browser originating the request. The CGI script may access a HTTP environment variable (“HTTP_USER_AGENT”) populated by the web server using data from a “User-Agent” field in a HTTP header. The value of the HTTP_USER_AGENT variable identifies the type of browser originating a request so that the CGI script can customize its response to that browser.
[0006] A web server and a browser also may exchange web cookies that contain data. A web cookie is data file that can be automatically exchanged between browsers and servers along with the request and responses exchanged between the browsers and servers. When a web cookie is received by a browser, it can be stored at the client computer. During future transactions with the web server, the web cookie (and any data that it contains) can be sent back to the web server. By using data stored in web cookies, a web server's need to request data from a user may be reduced. However, since web cookies are typically stored on a client computer, they may be deleted and their data lost. Furthermore, if a user moves to another computer, web cookie information stored on the user's original computer will be unavailable to that user. These factors may reduce the utility of web cookies.
[0007] The present inventors recognize that information service systems, such as web servers, should provide convenient, secure, reliable, and simple means of interacting with users. The present inventors further recognize when a server must query a user for data or use web cookies for data storage and input, convenience, security, reliability, and simplicity may suffer. Consequently, the invention disclosed herein provides additional means of providing information to a web server application that may provide additional flexibility in implementing information systems.
Summary
[0008] In general, in one aspect, the invention features a data transfer method performed at a proxy server. The method includes intercepting a data request from a client computer that is directed to a target server, encrypting profile information, augmenting the data request by adding the encrypted profile information to the data request, and sending the augmented data request to the target server. In another aspect, the invention features a data transfer method performed at an information server. The method includes receiving a data request from a proxy server, extracting profile information added to the data request by the proxy server, using the extracted profile information to generate a response, and sending the response to the proxy server.
[0009] In general, in another aspect, the invention features a computer program residing on a computer-readable medium. The program includes instructions for causing a computer to intercept a data request from a client computer that is directed to a target server, encrypt profile information, augment the data request by adding the encrypted profile information to the data request, and send the augmented data request to the target server. In another aspect, the invention features a computer program residing on a computer-readable medium that includes instructions for causing a computer to receive a data request comprising encrypted profile information that was added to the data request by a proxy server, extract the profile information added by the proxy server, use the extracted profile information to generate a response, and send the response to the proxy server.
[0010] In general, in another aspect, the invention features a proxy server that includes a database, a network interface, a processor, and a memory. The database includes records storing user profile information. The network interface operatively couples the proxy server to a network to exchange data with a client computer and with a target server. The processor is operatively coupled to the network interface, the database, and a memory. The memory includes executable instructions for causing the processor to intercept a data request that is directed to a target server, retrieve a record from the database, encrypt profile information in the record, augment the data request by adding the encrypted profile information, and send the augmented data request to the target server
[0011] In general, in another aspect, the invention features an information server that includes a network interface, a processor, and a memory. The network interface operatively couples the information server to a proxy server. The processor is operatively coupled to the network interface and to the memory. The memory includes executable instructions for causing the processor to receive a data request from the proxy server, decrypt user profile the information added to the data request by the proxy server; and use the decrypted user profile information to generate a response to the data request.
[0012] Implementations may include one or more of the following features. A reference token may be exchanged between servers and used to refer to previously exchanged profile information. The reference token may be placed in subsequent data request sent by the proxy server to the target in place of full profile information. The profile information that is encrypted by the proxy server can be stored in proxy server database records. The particular user profile information encrypted and included in a data request can be selected based on an identity of a client computer user or a browser user. The identity may be determined using the Internet Engineering Task Force IDENT protocol or by using another method.
[0013] Implementations also may include one or more of the following features. Profile information may be encrypted at the proxy server using a session key as an encryption key, and may be decrypted at the target server using the same session key. The session key may be determined by the proxy server and sent to the target server using a public key cryptography algorithm and a public key associated with the target server. A data request may use the hypertext transfer protocol. Profile information extracted from the data request at the target/information server can be provided to a web application, such as a CGI script, that is used to generate a response.
[0014] The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Implementations may provide advantages including reduction of redundant data entry, reduction of user data entry errors, secure storage of user data, and automated user profile determination and dissemination. Different encryption keys can be used for different information servers, and each information server may establish characteristics associated with its encryption key. A web site may dynamically generate, maintain, and change its unique encryption key. This may help to minimize risk of replay attacks, message forgery, and message tampering. In addition, implementations may support multiple levels of security.
[0015] Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.
Description of Drawings
[0016] FIG. 1 is a computer network diagram.
[0017] FIG. 2 is a computer network diagram.
[0018] FIGS. 3A and 3B show exemplary HTTP headers.
[0019] FIGS. 4A and 4B are flowcharts.
[0020] FIG. 5 is a message flow diagram.
Detailed Description
[0021] Processing of an information request at a information server, such as a web server, can be facilitated by a data transfer mechanism in which data needed to process the request is stored at a proxy server and automatically transferred to the information servers. Such a data transfer mechanism can be used, for example, by an information service provider (ISP) or on-line service provider (OSP) to automatically transfer information about a user (a “user profile”) to affiliated web sites. Referring to FIG. 2 , to automatically transfer a user profile to a web server 203, the user profile information is first stored at a proxy server 202 in a database 220. When a HTTP data request 211 is received by the proxy server 202 from a web browser 201, the user profile information from database 220 is encapsulated in a request 212 that is forwarded by the proxy server to web server 203. The proxy server 202 encapsulates the user profile information in the request 212 by adding HTTP headers containing the user profile information to the headers received in the request 211.
[0022] FIGS. 3A and 3B shows fields in HTTP requests. The fields 300 may be fields in a request 211 from a client computer 201, and the fields 350 may be fields in a request 212 forwarded by proxy server 202 to a web site 203. Referring to FIGS. 3A and 3B , each field 301-303 includes a HTTP field name and a value associated with the field. HTTP field names identify the associated field value. For example, the “User-Agent” field name in field 302 indicates that request 300 originated at a “Mozilla/3.0 compatible” browser; and the “Cookie:” field name in field 303 includes the value “been_here_before” is a web cookie. When a HTTP request 211 having fields 300 is received at proxy 202, the proxy server 202 can add user profile information to the request 211 by adding additional HTTP fields 304-305 containing the profile information, thereby generating a new request 212 with the user profile information encapsulated in fields 304-305.
[0023] Database 220 may be a local or remote database that can store multiple user profiles. For example, the database 220 may be a database storing user profiles on a hard disk directly connected to the proxy server 202, or the database may be a SQL database at a remote system and accessed over a TCP/IP connection. Still other database 220 implementations may be used. Each user profile may be associated with a particular user or group of users. A user profile may be selected from the database 220 based on the identifying information associated with a particular computer or user of that computer. To determine the user's identity, a proxy server may use a table or database that associates user identity information with network connection information. For example, referring to FIGS. 2 , 4A, and 4B, when a client computer 201 connects to a network 230, the client computer's user may submit name and password information to a POP or to a login server. The POP or login server may then send the user name and network connection information unique to that user (such as a unique combination of TCP/IP address and port number) to the proxy server 202 where it is stored in a database 220 (step 400). When the proxy server 202 receives a subsequent HTTP request 211 (step 401), the proxy server can identify the user associated with the request by querying the database of stored name and network connection associations. A proxy server also may identify a user using the IDENT protocol. The IDENT protocol is an Internet protocol that allows a computer to ask another computer for the name of the user. The IDENT protocol is further described in Internet Engineering Task Force (ETF) document RFC1413.
[0024] When the proxy server 202 has identified the user (step 402), the proxy server can retrieve a user profile associated with that user from its database 220. The proxy server may then add HTTP fields containing user profile information to fields in the original HTTP request 211 (step 403). For example, header fields 304-305 may be added to the original header fields 301-303 from request 211. Field 304 may include unencrypted user profile data (“UserName=John_Doe, ZipCode=60609, ParentalControl=YoungTeen), while field 305 may include encrypted user profile data. Encryption of data in the field 305 may use the SecureData protocol (explained later). The proxy server thereby forms the modified HTTP request 212 containing the user profile data. The modified request 212 may then be forwarded by the proxy server for receipt at a web site (steps 404 and 421).
[0025] Particular web servers may or may not be configured to recognize the user profile data fields 304-305. A web server that is not configured to recognize the user profile fields 304-305 may ignore the fields. A web server that is configured to recognize the user profile fields 304-305 can extract the profile data from the field 304-305 (steps 422 and 424). Extraction of user profile data in the field 305 may include decryption of the user profile data in encrypted field 305. The extracted user profile data can be used, for example, to generate or customize data sent in response 213 to the proxy server for forwarding as a response 214 to a user or client computer (step 425). For example, a tourist information web server may customize a page based user profile data specifying a browser user's age, and interest. If a web server looks for a user profile field 304-305 in the request 212, and the user profile field is not present, the server may use “traditional” data input mechanisms (such as forms and web cookies) to obtain needed data from a user (step 422-423). After the necessary data is obtained, the web server 203 can generate a response (step 425).
[0026] Exchange of user profile data between a proxy server 202 and a web server 203 may implemented using custom filtering software (“proxy data exchange filter” software) that can be added to commercially available proxy and web site server software. For example, Microsoft Internet Information Server (US) provides an application programming interface known as the information server application programming interface (ISAPI) that allows custom filtering software to be added to an IIS web site. A Netscape web site server provides an application programming interface known as the Netscape server application programming interface (NSAPI) that may also be used to develop custom filtering software. When a request 212 from the proxy server 203 is received at an IIS or Netscape server web site, the request 212 is passed to the proxy data exchange filter by the US or Netscape server software and the user profile data is extracted from the headers 304-305. The extracted profile data may then be made available as HTTP environment variables, database entries, or other data exchange structures that can be used by web applications. The remaining header information in request 212 (e.g., the original information from request 211), may then be processed by the web server to obtain response 213 information.
[0027] A proxy server 202 and web server 203 may implement the SecureData protocol (described below) to encrypt user profile data. Encrypted user profile data may be indicated by a special HTTP header. For example, the field name “User-Profile-SecureData” in field 305 indicates that the field value segment of field 305 contains encrypted profile data.
[0028] The SecureData protocol uses multiple cryptography algorithms to provide secure user profile data transfers between a proxy server 202 and a web server 203. For example, the SecureData protocol may use the Rivest, Shamir, Adelman (RSA) public key encryption algorithm or the pretty-good-privacy (PGP) public key cryptography algorithm along with the RSA RC4 symmetric encryption algorithm. Additional information on the RC4 algorithm can be found, for example, in Applied Cryptography, 2nd edition, By Bruce Schneier, John Wiley & Sons, 1996.
[0029] User profile information may be encrypted at proxy server 202 using a symmetric encryption algorithm. A symmetric encryption algorithm, such as the RSA RC4 algorithm, uses the same encryption key (referred to herein as a “session” key) to encrypt and decrypt data. The proxy server 202 may encrypt user profile data and place it in a HTTP field in request message 212. The proxy server 202 can also separately encrypt the session key using a public key cryptography algorithm and the public key of the web server 203. The public key encrypted session key may also be placed in the request message 212, or may be sent separately to the web server 203. When the web server 203 has received the encrypted session key and user profile data, the web server 203 can decrypt its session key by using the public key cryptography algorithm and the web server's private key. The web server 203 may then decrypt the user profile information using the decrypted session key. FIG. 5 shows further details of an implementation in which a request message may include both the encrypted session key and the encrypted user profile data.
[0030] Referring to FIG. 5 , when a request 511 is received at the proxy server 502, the proxy server determines whether it should add encrypted user profile data to the request. To do so, the proxy server may extract a destination web site address from URL information in the request 511, and query a database to determine whether the destination web site is to receive user profile information and whether the information is to be encrypted. If the destination web site is to receive encrypted user profile information, the proxy server 502 may then query its database to determine whether it has a valid public key for the web server 503. If the proxy server 502 has a valid public key, the proxy server can use the public key to encrypt session key information that can be provided to a symmetric encryption algorithm to encrypt user profile data. The encrypted session key and user profile data may then be forwarded in requests 514 to the web server 503.
[0031] If the proxy server 502 does not have a valid public key for web server 503, the proxy server will obtain the public key from the web server 503 using a HTTP request 512. The request 512 includes a URL that identifies a public key file (“pub_key_file”) stored on the server 503. The public key file may include additional information used by the proxy server 502. For example, the public key file may include the length of the public key, a SecureData protocol version number, a list of supported encryption algorithms, and shortcut configuration information (“shortcut” information is further explained, below).
[0032] An exemplary public key may have the format shown below (chevrons ‘<’ and ‘>’ delineate fields in the public key file and brackets ‘[’ and ‘]’ delineate optional information):
[0033]
| Exemplary Public Key File | |
|---|---|
| <public key = length-of-key key> | |
| [<Version = SecureData protocol version number>] | |
| [<crypto = <encryption method>] | |
| [<shortcut =[none|low|med|high|max]>] | |
[0034] The web server's public key file is returned to the proxy server 502 in a HTTP response 513. The web server 503 may provide additional SecureData protocol information in HTTP fields of response 513 and/or in the public key file returned by the response message 513. For example, HTTP fields in response 513 may specify a time to live (TTL) for the key. The TTL value can be used to indicate the period during which the public key is valid.
[0035] A proxy server 502 or web server 503 may check a SecureData protocol version number returned in the public key file, in request 512 and/or in response 513 to ensure that the protocol is functioning properly and to recover from or to avoid errors. For example, if a proxy server 502 detects that protocol versions numbers in a retrieved public key file and those in a header of a response 513 do not match, the proxy server may re-submit the request 512 to the server 503. When the request 512 is re-submitted, the proxy server 502 can include the HTTP “no-cache” pragma to instruct caching systems between the proxy 502 and the web server 503 not to use cached data. This may help avoid errors introduced by using stale cached data. When the proxy server 502 has received the web server's public key, it may cache the public key subject to a time-to-live (TTL) value specified by the web server 503 and/or the proxy server's own TTL policies.
[0036] If the proxy server 502 is unable to retrieve a web server's public key information or the public key information is otherwise unusable, the proxy server can add a problem report information to fields in a HTTP request 514 to indicate why the public key information is unusable. For example, the proxy server may indicate that the key information has been corrupted or a protocol version number or encryption level specified in the public key file is not supported. If the a web server's public key information is unusable and, consequently, the SecureData encryption protocol cannot be used, a proxy server may continue to forward the HTTP requests from browser clients to the web server without adding additional SecureData proxy headers. Alternatively the proxy server may block or otherwise filter request to the web server. The specific behavior may be defined on a per-web server basis using configuration information stored at the proxy server 502.
[0037] Once the proxy server 502 has the public key of web server 503, the proxy server can use the public key to encrypt session key data. The encrypted session key data may then be added to HTTP fields in the request from a browser or client computer 511 to form a modified request 514 that includes the public-key-encrypted session key information. The proxy server also can encrypt the user profile data using the session key information and a symmetric encryption algorithm and place the encrypted user profile data in HTTP fields in the modified request 514. For example, referring to FIG. 3B , the field 305 includes session key data “session=a3f792b210dafad” that may be public-key encrypted, and user profile data “Profile=A3S9C2ZA845MRAS02VMA39v1Z93AYC39AC3ABCEG78BB” that may be encrypted using a symmetric algorithm.
[0038] Different web server's or groups of web servers can have different session keys. A web server's session key may be formed by combining a “master” session key that is the same for a group of web servers with a key mask that can be used to create a unique session key for a web server or a group of web servers. For example, a 64-bit master session key may be combined with a 64-bit key mask using an exclusive-or (‘XOR’) operation, to yield a unique 64-bit session key. In some implementations, the master session key may be the proxy server's public key. Other methods of generating unique keys can be used. The session key data can in field 305 (e.g., “session=a3f792b210dafad”) can include numerous sub-fields. For example, the session key data can include a master key, a key mask, a timestamp, a URL hash, a Proxy IP field, and an encoding scheme field. These fields can contain the following data:
[0039] Master key: The master key is a value that is generated by the SecureData proxy server that can be combined with a key mask to generate a unique session key. The proxy server may periodically generate a new master session key. For example, a new master session key may be generated every n minutes. The Master key may be the proxy server's public key.
Key mask: The key mask is a value generated by a SecureData proxy server that is unique to a particular web site and which can be combined with a master key to generate a unique session key for that web site. A master key and a key mask can be combined using an exclusive-or (‘XOR’) operation, by appending the keys together, or by another key combination algorithm. A new key mask may be periodically generated. For example, a new key mask may be generated every n minutes.
Timestamp: A timestamp value may be added to the public-key encrypted data to make replay attacks more difficult. The timestamp value can be checked by the receiving web server and compared to the current time. If the difference between the timestamp value and current time exceeds a threshold value, the request may be denied or other error recovery or security procedures may be employed.
URL hash: A hash value derived from a requested URL may be added to the public-key encrypted data to make forging or tampering more difficult.
Proxy IP: The IP address of the proxy server be inserted in the session key data. When a request 514 is received at a web server 503, the web server may compare the IP address in the proxy IP field to help confirm that the request came from a particular proxy server 502. If the addresses differ, the request 514 may be rejected or other error recovery or security procedures may be employed.
Encoding scheme: Encoding scheme data may be sent from the SecureData proxy server to a SecureData web server to identify how user profile data is encoded. For example, the encoding scheme value may indicate that profile data is in a binary (bin) form, or in name-value pair (nvp) form (which may be expressed using the Abstract Syntax Notation 1 (ASN.1) or other name-value coding scheme), or in another form.
Key mask: The key mask is a value generated by a SecureData proxy server that is unique to a particular web site and which can be combined with a master key to generate a unique session key for that web site. A master key and a key mask can be combined using an exclusive-or (‘XOR’) operation, by appending the keys together, or by another key combination algorithm. A new key mask may be periodically generated. For example, a new key mask may be generated every n minutes.
Timestamp: A timestamp value may be added to the public-key encrypted data to make replay attacks more difficult. The timestamp value can be checked by the receiving web server and compared to the current time. If the difference between the timestamp value and current time exceeds a threshold value, the request may be denied or other error recovery or security procedures may be employed.
URL hash: A hash value derived from a requested URL may be added to the public-key encrypted data to make forging or tampering more difficult.
Proxy IP: The IP address of the proxy server be inserted in the session key data. When a request 514 is received at a web server 503, the web server may compare the IP address in the proxy IP field to help confirm that the request came from a particular proxy server 502. If the addresses differ, the request 514 may be rejected or other error recovery or security procedures may be employed.
Encoding scheme: Encoding scheme data may be sent from the SecureData proxy server to a SecureData web server to identify how user profile data is encoded. For example, the encoding scheme value may indicate that profile data is in a binary (bin) form, or in name-value pair (nvp) form (which may be expressed using the Abstract Syntax Notation 1 (ASN.1) or other name-value coding scheme), or in another form.
[0040] The proxy server 502 can use a web server's unique session key to encrypt user profile data that is add it to the field 305. In some implementations, the user profile data may be placed in one or more additional fields. The request 514, now containing the public-key encrypted session data and the symmetric encrypted user profile data, is then sent to web server 503.
[0041] When request 514 is received by the web server 503, the request can be passed to proxy data exchange filter software that can extract the added fields 304-305 from the request 514, decrypt the session key and the user profile information contained in the fields 304-305 and make the user profile information available to web server applications. The user profile information may be made available to web server applications by setting HTTP environment variables, by storing it in a database, by placing it in shared memory, and/or using other data exchange techniques. The proxy data exchange filter software may then pass the request 514 back to the web server for further processing and for generation of a response 515.
[0042] The web server 503 can store received profile data in a local database for future request processing purposes. The web server 503 may return a shortcut token to the proxy server 502. The proxy server 502 may add the shortcut token to a subsequent request 518 in place of the ‘full’ user profile data sent in the request 514. This can be used to reduce the amount of data that needs be transferred in subsequent request 518. A shortcut token can be an index value, database query information, file name, other pointer data, or an arbitrary value generated by the web site 503 and used to reference the stored user profile data.
[0043] A web server's public key file may be sent to the proxy server 502 using a security level specified by the site 503. For example, a web site's public key file include data indicating that the web site will use a specified one of the following shortcut key security levels:
-
- [0044] none: If “none” is specified, the shortcut token is sent to the proxy server as a clear (e.g., unencrypted value).
- [0045] low: If “low” is specified, the shortcut token is sent to the proxy server as a clear value and is accompanied by a hash of a previously requested URL.
- [0046] medium: If “medium” is specified, the “low” security level information is further accompanied by a timestamp value.
- [0047] high: If “high” is specified, the “medium” security information is further accompanied by the proxy server's IP address.
- [0048] max: If “max” is specified, the “high” security information is further accompanied by a sequence counter value. The sequence counter value may be based on a initial URL hash, the key mask, or other value, and is incremented in subsequent transactions.
[0049] At low, medium, high, and max security levels, the shortcut token and related security data can be sent in encrypted form using, for example, the proxy server's public key (which may be the master key value). Shortcut token security levels may also be indicated using HTTP fields in a response 513 or 515, or may be specified using data stored in a configuration database at the proxy server 513 using a data entry terminal.
[0050] A proxy server 502 or web server 503 may include other HTTP fields in a request 512, 514, 518 or in a response 513, 515, 519 to control user profile data transfers and/or the operation of the SecureData protocol. For example, HTTP fields in requests and/or responses may specify the following directives:
- [0051] Flush=<shortcut value|ALL>: The ‘Flush’ directive can be sent to the proxy server 502 to discard a specified shortcut token or to discard all shortcut tokens from a particular web server. The ‘Flush’ directive may also be sent to a web server to cause the web server to discard stored user profile data associated with a particular shortcut token or to discard all stored user profile data associated with the sending proxy server. This directive may be used by a web server 503 or proxy server 502 that is performing a reset operation.
- [0052] WrongKey: The WrongKey directive indicate that improper security protocol information was received. A proxy server that receives the WrongKey directive may re-send a request using a HTTP “no-cache” pragma. The “no-cache” pragma indicates that cached data should not be used to satisfy the request.
- [0053] SendFull: A web server can issue a SendFull directive to indicate that a proxy server should send “full” user profile data (rather than a shortcut token) in a subsequent HTTP request.
- [0054] TTL=<n>: The TTL (time to live) directive specifies a period (n, in seconds) during which a shortcut token is valid. Similar directives may be included in requests or response to indicate time-to-live values for other data, such as session keys and public keys.
[0055] The invention may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Apparatus of the invention may be implemented in a computer program product tangibly embodied in a machine-readable storage device for execution by a programmable processor; and method steps of the invention may be performed by a programmable processor executing a program of instructions to perform functions of the invention by operating on input data and generating output. The invention may advantageously be implemented in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device. Each computer program may be implemented in a high-level procedural or object-oriented programming language, or in assembly or machine language if desired; and in any case, the language may be a compiled or interpreted language. Suitable processors include, by way of example, both general and special purpose microprocessors. Generally, a processor will receive instructions and data from a read-only memory and/or a random access memory. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM disks. Any of the foregoing may be supplemented by, or incorporated in, specially-designed ASICs (application-specific integrated circuits).
[0056] A number of embodiments of the present invention have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention. For example, server, proxy, and client protocols need not use the HTTP protocol. Alternate protocols and data formats may be used such as file transfer protocol (FTP) or network news transfer protocol (NNTP). Accordingly, other embodiments are within the scope of the following claims.
Claims
What is claimed is:
1. A data transfer method, the method comprising:
receiving a request from a client application that is directed to a server;
retrieving an identifier based on an identity of a user of the client application;
modifying the request to include the retrieved identifier; and
sending the modified request to the server such that the server extracts the retrieved identifier, accesses a storage associated with the server in which user profile information for the user was stored prior to the server receiving the request, retrieves the user profile information from the storage associated with the server based on the extracted identifier, generates a response to the request based on the retrieved user profile information, and sends the response to the client application.
2. The method of claim 1 further comprising:
receiving an initial request from the client application that is directed to the server;
determining the identity of the user of the client application in response to receiving the initial request;
retrieving the user profile information based on the identity of the user;
encrypting the user profile information;
appending the encrypted profile information to the initial request to generate a modified initial request;
sending the modified initial request to the server such that the server parses the modified initial request to extract the encrypted user profile information, decrypts the encrypted user profile information extracted from the modified initial request, stores the decrypted user profile information in the storage associated with the server, generates an initial response to the initial request based on the decrypted user profile information, generates the identifier, and sends the initial response and the identifier;
receiving the identifier from the server;
storing the identifier in a storage;
receiving the initial response from the server; and
forwarding the initial response to the client application.
3. The method of claim 2 wherein encrypting the user profile information comprises determining a session key and using the session key to encrypt the user profile information.
4. The method of claim 3 further comprising:
encrypting the session key; and
appending the encrypted session key to the initial request to create the modified initial request.
5. The method of claim 4 wherein:
using the session key to encrypt the user profile information comprises using the session key and a symmetric encryption algorithm to encrypt the user profile information, and
encrypting the session key comprises encrypting the session key using a public key encryption algorithm and a public key associated with the server.
6. The method of claim 2 wherein determining the identity of the user comprises:
determining an IP address of the client computer; and
querying a database to determine an identity associated with the IP address in the database.
7. The method of claim 1 wherein receiving the request from the client application includes receiving the request at a proxy server.
8. A data processing method performed by a server, the method comprising:
receiving a modified request, wherein the modified request was created by inserting an identifier corresponding to a user of a client application into a request sent by the client application;
accessing a storage associated with the server, wherein profile information for the user of the client application was stored in the storage prior to the server receiving the modified request;
extracting the identifier from the modified request;
retrieving the user profile information from the storage associated with the server based on the extracted identifier;
generating a response to the request based on the retrieved user profile information; and
sending the response to the client application.
9. The method of claim 8 further comprising:
receiving an initial modified request, wherein the initial modified request includes encrypted user profile information inserted into an initial request;
extracting the encrypted user profile information;
decrypting the encrypted user profile information extracted from the initial modified request;
storing the decrypted user profile information in the storage associated with the server;
generating the identifier; and
sending the identifier.
10. The method of claim 9 wherein
the initial modified request includes a session key, and
decrypting the encrypted user profile information comprises decrypting the encrypted user profile information extracted from the initial modified request using the session key.
11. The method of claim 10 further comprising decrypting the session key.
12. The method of claim 11 wherein:
decrypting the session key comprises decrypting the session key using a public key algorithm and a private key of the server, and
decrypting the encrypted user profile information using the session key comprises decrypting the encrypted user profile information using a symmetric decryption algorithm and the session key.
13. The method of claim 8 further comprising:
receiving a flush directive; and
in response to receiving the flush directive, discarding the user profile information stored in the local storage.
14. The method of claim 8 wherein receiving the modified request includes receiving the modified request from a proxy server.
15. A machine-readable storage device having a computer program embodied thereon, the computer program comprising instructions for causing a processing device to:
receive a request from a client application that is directed to a server;
retrieve an identifier based on an identity of a user of the client application;
modify the request to include the retrieved identifier; and
send the modified request to the server such that the server extracts the retrieved identifier, accesses a storage associated with the server in which user profile information for the user was stored prior to the server receiving the request, retrieves the user profile information from the storage associated with the server based on the extracted identifier, generates a response to the request based on the retrieved user profile information, and sends the response to the client application.
16. The machine-readable storage device of claim 15 wherein the computer program further comprises instructions for causing the processing device to:
receive an initial request from the client application that is directed to the server;
determine the identity of a user of the client computer in response to receiving the initial request;
retrieve the user profile information based on the identity of the user;
encrypt the user profile information;
append the encrypted profile information to the initial request to generate a modified initial request;
send the modified initial request to the server such that the server parses the modified initial request to extract the encrypted user profile information, decrypts the encrypted user profile information extracted from the modified initial request, stores the decrypted user profile information in the storage associated with the server, generates an initial response to the initial request based on the decrypted user profile information, generates the identifier, and sends the initial response and the identifier;
receive the identifier from the server;
store the identifier in a storage;
receive the initial response from the server; and
forward the initial response to the client application.
17. The machine-readable storage device of claim 16 wherein, to encrypt the user profile information, the computer program further comprises instructions for causing the processing device to determine a session key and using the session key to encrypt the user profile information.
18. The machine-readable storage device of claim 17 wherein the computer program further comprises instructions for causing the processing device to:
encrypt the session key; and
append the encrypted session key to the initial request to create the modified initial request.
19. The machine-readable storage device of claim 18 wherein:
to use the session key to encrypt the profile information, the computer program further comprises instructions for causing the processing device to use the session key and a symmetric encryption algorithm to encrypt the user profile information, and
to encrypt the session key, the computer program further comprises instructions for causing the processing device to encrypt the session key using a public key encryption algorithm and a public key associated with the server.
20. The machine-readable storage device of claim 15 wherein the computer program further comprises instructions for causing processing device to send a flush directive to the server such that the server discards the user profile information stored in the storage associated with the server.
21. The machine-readable storage device of claim 15 wherein the request from the client application is received at a proxy server.
22. A machine-readable storage device having a computer program embodied thereon, the computer program comprising instructions for causing a server to:
receive a modified request, wherein the modified request was created by inserting an identifier corresponding to a user of a client application into a request sent by the client application;
access a storage associated with the server, wherein profile information for the user of the client application was stored in the storage prior to the server receiving the modified request;
extract the identifier from the modified request;
retrieve the user profile information from the storage associated with the server based on the extracted identifier;
generate a response to the request based on the retrieved user profile information; and
send the response to the client application.
23. The machine-readable storage device of claim 22 wherein the computer program further comprises instructions for causing the server to:
receive an initial modified request, wherein the initial modified request includes encrypted user profile information inserted into an initial request;
extract the encrypted user profile information;
decrypt the encrypted user profile information extracted from the initial modified request;
store the decrypted user profile information in the storage associated with the server;
generate the identifier; and
send the identifier.
24. The machine-readable storage device of claim 23 wherein
the initial modified request includes a session key, and
to decrypt the encrypted user profile information, the computer program further comprises instructions for causing the server to decrypt the encrypted user profile information extracted from the initial modified request using the session key.
25. The machine-readable storage device of claim 24 wherein the computer program further comprises instructions for causing the server to decrypt the session key.
26. The machine-readable storage device of claim 25 wherein:
to decrypt the session key, the computer program further comprises instructions for causing the server to decrypt the session key using a public key algorithm and a private key of the server, and
to decrypt the encrypted user profile information using the session key, the computer program further comprises instructions for causing the server to decrypt the encrypted user profile information using a symmetric decryption algorithm and the session key.
27. The machine-readable storage device of claim 22 wherein the computer program further comprises instructions for causing the proxy server to:
receive a flush directive from the proxy server; and
discard the user profile information stored in the local storage.
28. The machine-readable storage device of claim 22 wherein the modified request is received from a proxy server.
29. A data transfer method, the method comprising:
receiving a request from a client application that is directed to a server;
retrieving an identifier based on an identity of a user of the client application;
modifying the request to include the retrieved identifier; and
sending the modified request to the server such that the server extracts the retrieved identifier, retrieves user profile information from a location other than the modified request based on the extracted identifier, generates a response to the request based on the retrieved user profile information, and sends the response to the proxy server.
30. A data processing method performed by a server, the method comprising:
receiving a modified request, wherein the modified request was created by inserting an identifier corresponding to a user of a client application into a request sent by the client application;
extracting the identifier from the modified request;
retrieving user profile information from a location other than the received, modified request based on the extracted identifier;
generating a response to the request based on the retrieved user profile information; and
sending the response to the client application.
Patent Citations (64)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5245656(A) | 1993-09-01 | Loeb et al. | Applicant |
| US5586260(A) | 1996-12-01 | Hu | Applicant |
| US5671279(A) | 1997-09-01 | Elgamal | Applicant |
| US5673322(A) | 1997-09-01 | Pepe et al. | Applicant |
| US5678041(A) | 1997-10-01 | Baker et al. | Applicant |
| US5708780(A) | 1998-01-01 | Levergood et al. | Applicant |
| US5740252(A) | 1998-04-01 | Minor et al. | Applicant |
| US5740361(A) | 1998-04-01 | Brown | Applicant |
| US5754938(A) | 1998-05-01 | Herz et al. | Applicant |
| US5764890(A) | 1998-06-01 | Glasser et al. | Applicant |
| US5802320(A) | 1998-09-01 | Baehr et al. | Applicant |
| US5805803(A) | 1998-09-01 | Birrell et al. | Applicant |
| US5825890(A) | 1998-10-01 | Elgamal et al. | Applicant |
| US5826025(A) | 1998-10-01 | Gramlich | Applicant |
| US5826242(A) | 1998-10-01 | Montulli | Applicant |
| US5889956(A) | 1999-03-01 | Hauser et al. | Applicant |
| US5892761(A) | 1999-04-01 | Stracke, Jr. | Applicant |
| US5905872(A) | 1999-05-01 | DeSimone et al. | Applicant |
| US5933827(A) | 1999-08-01 | Cole et al. | Applicant |
| US5961593(A) | 1999-10-01 | Gabber et al. | Examiner |
| US5978799(A) | 1999-11-01 | Hirsch | Applicant |
| US5987454(A) | 1999-11-01 | Hobbs | Applicant |
| US5991795(A) | 1999-11-01 | Howard et al. | Applicant |
| US5991810(A) | 1999-11-01 | Shapiro et al. | Applicant |
| US6029175(A) | 2000-02-01 | Chow et al. | Applicant |
| US6049821(A) | 2000-04-01 | Theriault et al. | Applicant |
| US6049877(A) | 2000-04-01 | White | Applicant |
| US6052785(A) | 2000-04-01 | Lin et al. | Applicant |
| US6081900(A) | 2000-06-01 | Subramaniam et al. | Examiner |
| US6105027(A) | 2000-08-01 | Schneider et al. | Applicant |
| US6128627(A) | 2000-10-01 | Mattis et al. | Applicant |
| US6131095(A) | 2000-10-01 | Low et al. | Applicant |
| US6144996(A) | 2000-11-01 | Starnes et al. | Applicant |
| US6161145(A) | 2000-12-01 | Bainbridge et al. | Examiner |
| US6182141(B1) | 2001-01-01 | Blum et al. | Applicant |
| US6212640(B1) | 2001-04-01 | Abdelnur et al. | Examiner |
| US6253326(B1) | 2001-06-01 | Lincke et al. | Applicant |
| US6272492(B1) | 2001-08-01 | Kay | Applicant |
| US6298380(B1) | 2001-10-01 | Coile et al. | Applicant |
| US6308216(B1) | 2001-10-01 | Goldszmidt et al. | Examiner |
| US6330561(B1) | 2001-12-01 | Cohen et al. | Applicant |
| US6373950(B1) | 2002-04-01 | Rowney | Examiner |
| US6389460(B1) | 2002-05-01 | Stewart et al. | Applicant |
| US6421781(B1) | 2002-07-01 | Fox et al. | Examiner |
| US6487538(B1) | 2002-11-01 | Gupta et al. | Applicant |
| US6606708(B1) | 2003-08-01 | Devine et al. | Examiner |
| US2001/0039587(A1) | 2001-11-01 | Uhler et al. | Applicant |
| US2001/0047484(A1) | 2001-11-01 | Medvinsky et al. | Examiner |
| EP848338 | 1998-06-01 | Applicant | |
| EP855659 | 1998-07-01 | Applicant | |
| EP893920 | 1999-01-01 | Applicant | |
| JP9-114783 | 1989-05-01 | Applicant | |
| JP11-31126 | 1997-05-01 | Applicant | |
| WO97/15885 | 1997-05-01 | Applicant | |
| WO98/31155 | 1998-07-01 | Applicant | |
| WO98/33130 | 1998-07-01 | Applicant | |
| WO98/36522 | 1998-08-01 | Applicant | |
| WO98/43150 | 1998-10-01 | Applicant | |
| WO98/45793 | 1998-10-01 | Applicant | |
| WO98/58334 | 1998-12-01 | Applicant | |
| WO99/00958 | 1999-01-01 | Applicant | |
| WO99/00960 | 1999-01-01 | Applicant | |
| WO99/03243 | 1999-01-01 | Applicant | |
| WO/79432 | 2000-12-01 | Applicant |
Non-Patent Literature (17)
- Gabber et al., “How to Make Personalized Web Browsing Simple, Secure, and Anonymous,” Financial Cryptography, International Conference, Feb. 24, 1997 (XP002059819), pp. 17-31.Applicant
- Petitcolas et al., “WebGroup: a secure group access control tool for the World-Wide Web,” Proceedings—The Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises, US, IEEE Computer Society Press, Los Alamitos, CA, 1998 (XP002142486), pp. 301-305.Applicant
- U.S. Appl. No. 09/258,242, filed Feb. 26, 1999.Applicant
- Office Action dated Apr. 1, 2003 in U.S. Appl. No. 09/258,242.Applicant
- Claims Rejected in Office Action dated Apr. 1, 2003 for U.S. Appl. No. 09/258,242.Applicant
- Wu et al., Virtual Proxy Servers for WWW and Intelligent Agents on the Internet, 1997 IEEEΩ.Applicant
- “Sixth International World Wide Web Conference” Conference Proceedings, http://decweb.ethz.ch/WWW6/.Applicant
- “Extranet Security: What's Right for the Business?”, Steve Trulan, p. 47, Information Systems Security, vol. 7 No. 1, Spring 1998.Applicant
- “Exploiting User Behavior in Prefetching WWW Documents”, El-Saddik et al., pp. 302-311, Interactive Distributed Multimedia Systems and Telecommunications Services 5th International Workshop 1998.Applicant
- Network News (UK Edition), pp. 29-30, Nov. 18, 1998, Issue 156.Applicant
- “Intercessory Objects within Channels” Barry Kitson, Telecom Research Laboratories, 1995.Applicant
- Webgroup: a secure group access control tool for the World-Wide Web, Petitcolas and Zhang pp. 301-205, Proceedings of Seventh IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, 1988.Applicant
- “Notice of Reasons for Rejection,” Japanese Patent Application No. 2000-601562, Jul. 8, 2004.Applicant
- “Statement of Grounds of Opposition,” Australian Patent Application No. 200035010 (769163), Jul. 15, 2004.Applicant
- Japanese Office Action issued on Nov. 29, 2005 for JP2001-500930, 3 pages. Translation of the Japanese Office Action 2 pages.Applicant
- Kamiba et al., “User Profile Management Agent”, Information Processing Institute Study Report (97-HI-70), vol. 97, No. 2, Jan. 16, 1997, p. 1-8. Partial translation of publication, 3 pages.Applicant
- “Recent Application Server Situations”, ASCII NT, vol. 4, No. 3, Mar. 1, 1999, pp. 225-229. Partial translation of publication, 2 pages.Applicant