Methods for optimizing HTTP header based authentication and devices thereof

Description

FIELD

This technology generally relates to methods and devices for authentication and, more particularly, to methods for optimizing HTTP header based authentication and devices thereof.

BACKGROUND

In the context of a transaction using HTTP, authentication is a method for a program or a web browser at a client computing device to provide user credentials which may include a user name and a password each time while making a request. A HTTP header based authentication requires a server to send back HTTP 401/407 challenge to browser for collecting user's authentication credentials or token. The general process which is followed is the web server sending a HTTP 401/407 challenge for each new TCP connection and web-browser replying with user's credentials or token as response to the challenge.

However, each 401/407 challenge attempt adds latency by creating one or more than one extra round trip time between the client and the server. It also adds to the processing overhead on server side as server needs to verify the received credential or token for each request.

SUMMARY

A method for optimizing authentication includes receiving at an application management computing device a request from a client computing device which requires authentication. A determination is made by the application management computing device whether user network identification information currently is stored for the requesting client computing device. On determining the presence of stored user network identification information for the authentication, the application management computing device obtains the stored user network identification information for the authentication. The authentication is completed by the application management computing device with the obtained user network identification information.

A non-transitory computer readable medium having stored thereon instructions for optimizing authentication comprising machine executable code which when executed by at least one processor, causes the processor to perform steps including receiving a request from a client computing device which requires authentication. A determination is made whether user network identification information currently is stored for the requesting client computing device. The stored user network identification information for the authentication is obtained when the user network identification information is determined to be currently stored for the requesting client computing device. The authentication is completed with the obtained user network identification information.

An application management computing device to optimize authentication includes at least one of configurable hardware logic configured to be capable of implementing and a processor coupled to a memory and configured to execute programmed instructions stored in the memory including receiving a request from a client computing device which requires authentication. A determination is made whether user network identification information currently is stored for the requesting client computing device. The stored user network identification information for the authentication is obtained when the user network identification information is determined to be currently stored for the requesting client computing device. The authentication is completed with the obtained user network identification information.

This technology provides a number of advantages including optimizing HTTP header based authentication. With this technology, the typical number of 401/407 challenges can be substantially reduced by utilizing a stored cookie comprising current authentication information at the client computing device. Accordingly, with this technology application management computing device utilization is optimized as the latency and the round trip time is reduced between the client computing device and the application management computing device. It also reduces the processing overhead on the application management computing device side as the application management computing device needs to verify the received credentials/token for reduced number of times.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an exemplary network environment with an application management computing device for optimizing HTTP header based authentication; and

FIG. 2 is a flowchart of an exemplary method for optimizing authentication.

DETAILED DESCRIPTION

An exemplary network environment 10 with an application management computing device 14 for optimizing HTTP header based authentication is illustrated in FIG. 1. The exemplary environment 10 includes client computing devices 12, the application management computing device 14, and servers 16 which are coupled together by local area networks (LANs) 28 and wide area network (WAN) 30, although the environment can include other types and numbers of devices, components, elements and communication networks in other topologies and deployments. While not shown, the exemplary environment 10 may include additional network components, such as routers, switches and other devices, which are well known to those of ordinary skill in the art and thus will not be described here. This technology provides a number of advantages including optimizing HTTP header based authentication.

Referring more specifically to FIG. 1, the application management computing device 14 is coupled to client computing devices 12 through one of the LANs 28, although the client computing devices 12 and application management computing device 14 may be coupled together via other topologies. Additionally, the application management computing device 14 is coupled to the servers 16 through the WAN 30 and another one of the LANs 28, although the servers 16 and the application management computing device 14 may be coupled together via other topologies.

The application management computing device 14 assists with optimizing authentication as illustrated and described with the examples herein, although application management computing device 14 may perform other types and numbers of functions. Application management computing device 14 includes at least one processor 18, memory 20, optional configurable hardware logic 21, I/O interface 22, and interface device 24 which are coupled together by bus 26, although application management computing device 14 may comprise other types and numbers of elements in other configurations.

Processor(s) 18 may execute one or more computer-executable instructions stored in the memory 20 for the methods illustrated and described with reference to the examples herein, although the processor(s) can execute other types and numbers of instructions and perform other types and numbers of operations. The processor(s) 18 may comprise one or more central processing units (“CPUs”) or general purpose processors with one or more processing cores, such as AMD® processor(s), although other types of processor(s) could be used (e.g., Intel®).

Memory 20 may comprise one or more tangible storage media, such as RAM, ROM, flash memory, CD-ROM, floppy disk, hard disk drive(s), solid state memory, DVD, or any other memory storage types or devices, including combinations thereof, which are known to those of ordinary skill in the art. Memory 20 may store one or more non-transitory computer-readable instructions of this technology as illustrated and described with reference to the examples herein that may be executed by the one or more processor(s) 18. The flow chart shown in FIG. 2 is representative of example steps or actions of this technology that may be embodied or expressed as one or more non-transitory computer or machine readable instructions stored in memory 20 that may be executed by the processor(s) 18 and/or may be implemented by configured logic in the optional configurable hardware logic 21.

The configurable hardware logic 21 may comprise specialized hardware configured to implement one or more steps of this technology as illustrated and described with reference to the examples herein. By way of example only, the optional configurable hardware logic 21 may comprise one or more of field programmable gate arrays (“FPGAs”), field programmable logic devices (“FPLDs”), application specific integrated circuits (ASICs”) and/or programmable logic units (“PLUs”).

Input and display devices 22 enable a user, such as an administrator, to interact with the application management computing device 14, such as to input and/or view data and/or to configure, program and/or operate it by way of example only. Input devices may include a keyboard and/or a computer mouse and display devices may include a computer monitor, although other types and numbers of input devices and display devices could be used.

The interface device 24 in the application management computing device 14 is used to operatively couple and communicate between the application management computing device 14 and the client computing devices 12 and the servers 16 which are all coupled together by one or more of the local area networks (LAN) 28 and the wide area network (WAN) 30, although other types and numbers of communication networks or systems with other types and numbers of connections and configurations to other devices and elements. By way of example only, the local area networks (LAN) 28 and the wide area network (WAN) 30 can use TCP/IP over Ethernet and industry-standard protocols, including HTTP although other types and numbers of communication networks, can be used. In this example, the bus 26 is a hyper-transport bus in this example, although other bus types and links may be used, such as PCI.

Each of the client computing devices 12 and the servers 16 include a central processing unit (CPU) or processor, a memory, an interface device, and an I/O system, which are coupled together by a bus or other link, although other numbers and types of network devices could be used. The client computing devices 12, in this example, may run interface applications, such as Web browsers, that may provide an interface to make requests for and send content and/or data to different server based applications at servers 16 via the LANs 28 and/or WANs 30. Additionally, in order for the client computing devices 12 to requests for content to one or more of the servers 16, each client computing device 12 may have to provide user network identification information for authentication.

Generally, servers 16 process requests received from requesting client computing devices 12 via LANs 28 and/or WAN 30 according to the HTTP-based application protocol in this example, but the principles discussed herein are not limited to this example and can include other application protocols. A series of applications may run on the servers 16 that allow the transmission of data, such as a data file or metadata, requested by the client computing devices 12. The servers 16 may provide data or receive data in response to requests directed toward the respective applications on the servers 16 from the client computing devices 12. It is to be understood that the servers 16 may be hardware or software or may represent a system with multiple servers 16, which may include internal or external networks. In this example the servers 16 may be any version of Microsoft® IIS servers or Apache® servers, although other types of servers may be used. Further, additional servers may be coupled to the LAN 28 and many different types of applications may be available on servers coupled to the LAN 28.

Although an exemplary network environment 10 with the client computing devices 12, the application management computing device 14, the servers 16, the LANs 28 and the WAN 30 are described and illustrated herein, other types and numbers of systems, devices, blades, components, and elements in other topologies can be used. It is to be understood that the systems of the examples described herein are for exemplary purposes, as many variations of the specific hardware and software used to implement the examples are possible, as will be appreciated by those skilled in the relevant art(s).

Furthermore, each of the systems of the examples may be conveniently implemented using one or more general purpose computer systems, microprocessors, digital signal processors, and micro-controllers, programmed according to the teachings of the examples, as described and illustrated herein, and as will be appreciated by those of ordinary skill in the art.

In addition, two or more computing systems or devices can be substituted for any one of the systems or devices in any example. Accordingly, principles and advantages of distributed processing, such as redundancy and replication also can be implemented, as desired, to increase the robustness and performance of the devices and systems of the examples. The examples may also be implemented on computer system(s) that extend across any suitable network using any suitable interface mechanisms and traffic technologies, including by way of example only teletraffic in any suitable form (e.g., voice and modem), wireless traffic media, wireless traffic networks, cellular traffic networks, G3 traffic networks, Public Switched Telephone Network (PSTNs), Packet Data Networks (PDNs), the Internet, intranets, and combinations thereof.

The examples may also be embodied as a non-transitory computer readable medium having instructions stored thereon for one or more aspects of the technology as described and illustrated by way of the examples herein, which when executed by a processor (or configurable hardware), cause the processor to carry out the steps necessary to implement the methods of the examples, as described and illustrated herein.

An exemplary method for optimizing authentication will now be described with reference to FIGS. 1-2. In step 305, one of the client computing devices 12 may transmit a request which is received by the application management computing device 14 and requires authentication, although requests can be received from other types of devices and systems.

In step 310, the application management computing device 14 determines whether the user network identification information is currently present in the request received from the client computing device 12. This information is present in the request received from the client computing device 12 if the user network identification information stored in the memory of the client computing device 12, more particularly in the browser of the client computing device 12 in the form of a cookie in this example. By way of example only, the user network identification information stored in the form of a cookie may also be in different forms such as a flash cookie, a browser cookie or a general HTTP cookie, although the user network identification information may be stored in other manners.

If in step 310, the application management computing device 14 determines user network identification information is not currently stored, then the No branch is taken to step 340. In step 340, the application management computing device 14 sends one or more than one challenge message requiring client credentials, such as a HTTP challenge 401/407 requests, to the requesting one of the client computing devices 12, although other types of challenge messages can be sent to the client computing device 12 to obtain client credentials.

In step 345, the application management computing device 14 receives one or more user credential from the requesting one of the client computing devices 12 in response the challenge message. In this example, the received credentials include login credentials, such as username, password or tokens, although other types and numbers of credentials could be received.

Next, in step 350 the application management computing device 14 authenticates the received credentials by verifying with the corresponding one of the one or more servers 16 to which the request is directed, although other manners for authenticating the credentials could be used. If in step 350, the application management computing device 14 determines the received credentials from the requesting one of the client computing devices 12 are not authenticated, then the No branch is taken to step 351. In step 351, the application management computing device 14 transmits a denial of the request to the requesting one of the client computing devices 12 and this exemplary method ends.

If in step 350, the application management computing device 14 determines the received credentials from the requesting one of the client computing devices 12 are authenticated, then the Yes branch is taken to step 352. At step 352, the application management computing device 14 obtains the user network identification information user from the authenticated requesting one of the client computing devices 12. The user network identification information may be a user's internet protocol address, user's user agent string presented by the internet browser of the client computing device 12 and other network related properties of the internet browser of the client computing devices 12, although other types of network identification information could be used. The user network identification information is network identification information of the client computing device 12, which is obtained for the first time when the application management computing device 14 determines that the cookie is not present in the browser of the client computing device 12.

In step 355, the application management computing device 14 may encrypt the user network identification information by using an encryption key. By way of example, the encryption key may be unique to each user or can be common to all users. Optionally, the application management computing device 14 may store the user network identification information in its own memory 20. The application management computing device 14 then can create a unique identifier that enables it to lookup user network identification information in its memory 20 and can encrypt this unique identifier by using the encryption key.

In step 360, the application management computing device 14 transmits the encrypted value as a cookie to the requesting client computing device 12 where it is stored in the browser of the client computing device 12 and then the initial authentication is completed. For all subsequent requests, the application management computing device 14 may use the cookie stored in the browser of the client computing device 12 to authenticate the requests

Referring back to step 305, the one of the client computing devices 12 which previously transmitted a request may transmit another request which is received by the application management computing device 14 and requires authentication, although requests can be received from other types of devices and systems

In step 310, the application management computing device 14 determines whether the user network identification information is currently stored in the request received from the internet browser of the client computing device 12. Accordingly, in this pass through step 310 the application management computing device 14 determines the user network identification information is currently stored in the browser of the requesting one of the client computing devices so the Yes branch is taken to step 315.

In step 315, the application management computing device 14 obtains the cookie from the received request of the client computing devices 12 and determines whether the cookie is valid. If in step 315, the application management computing device 14 determines the obtained cookie is invalid, then the No branch is taken to step 340 as described earlier.

If in step 315, the application management computing device 14 determines the obtained cookie is valid, then the Yes branch is taken to step 320. In step 320, the application management computing device 14 decrypts the obtained cookie to obtain the user network identification information.

In step 325, the application management computing device 14 determines whether a signature of the decrypted cookie is valid. If in step 325, the application management computing device 14 determines the signature in the decrypted cookie is not valid, then the No branch is taken to step 340 as described earlier.

If in step 325, the application management computing device 14 determines the signature in the decrypted user network identification information is verified, then the Yes branch is taken to step 330. In step 330, the application management computing device 14 first obtains the verification user network identification information from the client computing device 12 from which the request was sent and determines whether in the decrypted user network identification information, such as client's ip, unique client id, ssl session id, or other identifiers which is stored in the cookie is same as the verification user network identification information. The verification of the user network identification information is network identification information of the requesting client computing device 12, such as client's identification protocol (client's ip), user session information etc. Since, the cookie is already stored once in the browser of the client computing device 12 based on the previous communication with the application management computing device 14, the application management computing device 14 additionally obtains the network information of the requesting client computing device 12 in the form of verification of the user network identification information to compare with the information contained in the previously stored cookie. If in step 330, the application management computing device 14 determines the decrypted user network identification information stored in the already existing cookie is not the same the verified user network identification which is the user network identification information of the client computing device 12 from which the new request is received, then the No branch is taken to step 340 as described earlier. If in step 330, the application management computing device 14 determines the user network identification information in the cookie is same as the verified user network identification, then the Yes branch is taken to step 360 as described earlier.

In one exemplary method of the present disclosure, the cookie stored in the browser of the client computing device 12 may be valid for or could be used by the application management computing device 14 to service the subsequent requests for a particular user session of the requesting client computing device 12, wherein the client computing devices 12 may be required to obtain a new cookie by following the steps 340 to 355 as described above to authenticate a transaction after termination of the user session.

In another exemplary method of the present disclosure, the cookie stored in the browser of the client computing device 12 may be valid for or could be used by the application management computing device 14 to service the subsequent requests for a particular number of transactions of the requesting client computing device 12, wherein the client computing devices 12 may be required to obtain a new cookie by following steps 340 to 355 as described above to authenticate a transaction after the reaching the maximum number of transactions.

In another exemplary method of the present disclosure, the cookie stored in the browser of the client computing device 12 may be valid for or could be used by the application management computing device 14 to service the subsequent requests for a particular interval of time, wherein the client computing devices 12 may be required to obtain a new cookie by following steps 340 to 355 as described above to authenticate a transaction after the termination of the time interval.

Accordingly, as illustrated and described with the examples herein, this technology provides a number of advantages including optimizing HTTP header based authentication. With this technology, the typical number of 401/407 challenges can be substantially reduced by utilizing a stored cookie comprising current authentication information at the application management computing device. Accordingly, with this technology server utilization is optimized as the latency and the round trip time is reduced between the client computing device and the server. It also reduces the processing overhead on the server side as the server needs to verify the received credentials/token only once

Having thus described the basic concept of the invention, it will be rather apparent to those skilled in the art that the foregoing detailed disclosure is intended to be presented by way of example only, and is not limiting. Various alterations, improvements, and modifications will occur and are intended to those skilled in the art, though not expressly stated herein. These alterations, improvements, and modifications are intended to be suggested hereby, and are within the spirit and scope of the invention. Additionally, the recited order of processing elements or sequences, or the use of numbers, letters, or other designations therefore, is not intended to limit the claimed processes to any order except as may be specified in the claims. Accordingly, the invention is limited only by the following claims and equivalents thereto.