Methods for SSL protected NTLM re-authentication and devices thereof

Description

This application claims the benefit of U.S. Provisional Patent Application Ser. No. 62/140,986, filed Mar. 31, 2015, which is hereby incorporated by reference in its entirety.

FIELD

This technology generally relates to methods and devices for network traffic management and, more particularly, to methods for SSL protected NTLM re-authentication and devices thereof.

BACKGROUND

NTLM is a connection-oriented authentication protocol which uses challenge-response messages to authenticate a client connection. When a client sends a HTTP request to a backend resource that's NTLM protected, the request is allowed if the associated connection is NTLM authenticated. If the connection is not authenticated, then the server responds with an HTTP 401 message to the client to start NTLM handshake.

NTLM handshake involves Negotiate (Type 1), Challenge (Type 2) and Authenticate (Type 3) messages. First, the client starts the handshake by sending the Negotiate (Type 1) message advertising its capabilities. Next, the server responds with a challenge in the Challenge (Type 2) message. Finally, the client generates a response to the challenge and sends it in the Authenticate (Type 3) message. The server authenticates the Authenticate message by sending the challenge (generated by the server as part of the Challenge message) and the response to the challenge (generated by the client) to the Active Directory server. Once the Authenticate message is successfully validated, the client connection is authenticated and the original HTTP request is allowed to access the protected web application.

With prior technologies, when a client computing device receives a connection reset from the server due to any internal or backend server error, then some client computing devices create a new connection and reuse the previously used Authenticate handshake message to authenticate the new connection. However, NTLM is a connection oriented protocol and therefore the servers expect client computing devices to perform full NTLM handshake instead of reusing the previously used Authenticate message so they force client computing devices to restart NTLM negotiation by sending HTTP 401 message. Unfortunately, with prior technologies client computing devices treat these messages like an authenticate failure message resulting in a bad end-user experience.

SUMMARY

A method for SSL protected NTLM re-authentication includes receiving by a network traffic management apparatus a connection reset message from a web application server. The received connection reset message is forwarded by the network traffic management apparatus to the client computing device. A recent request including connection data to access a web application is received by the network traffic management apparatus on a new connection as a response to the forwarded connection reset message from the client computing device. Next, it is determined by the network traffic management apparatus whether the received recent request to access the web application including the connection data is identical to a stored connection data. The client computing device is re-authenticated and granted access by the network traffic management apparatus to the requested web application to when the connection data is determined to be identical to the stored connection data.

A non-transitory computer readable medium having stored thereon instructions for SSL protected NTLM re-authentication comprising machine executable code which when executed by at least one processor, causes the processor to perform steps includes receiving a connection reset message from a web application server. The received connection reset message is forwarded to the client computing device. A recent request including connection data to access a web application is received on a new connection as a response to the forwarded connection reset message from the client computing device. Next, it is determined whether the received recent request to access the web application including the connection data is identical to a stored connection data. The client computing device is re-authenticated and granted access to the requested web application to when the connection data is determined to be identical to the stored connection data.

A network traffic management apparatus including at least one of configurable hardware logic configured to be capable of implementing or a processor coupled to a memory and configured to execute programmed instructions stored in the memory to receiving a connection reset message from a web application server. The received connection reset message is forwarded to the client computing device. A recent request including connection data to access a web application is received on a new connection as a response to the forwarded connection reset message from the client computing device. Next, it is determined whether the received recent request to access the web application including the connection data is identical to a stored connection data. The client computing device is re-authenticated and granted access to the requested web application to when the connection data is determined to be identical to the stored connection data.

This technology provides a number of advantages including providing a method, non-transitory computer readable medium and apparatus that effectively assists with SSL protected NTLM re-authentication. The technology disclosed herein provides advantages of avoiding the requirement of full NTLM authentication when a connection reset message is received from a web application server thereby resulting in better user experience.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example of a block diagram of an environment including a network traffic management apparatus for SSL protected NTLM re-authentication;

FIG. 2 is an example of a block diagram of a network traffic management apparatus;

FIG. 3 is an exemplary flowchart of a method for SSL protected NTLM re-authentication; and

FIG. 4 is an exemplary sequence diagram for SSL protected NTLM re-authentication.

DETAILED DESCRIPTION

An example of a network environment 10 for SSL protected NTLM re-authentication with a network traffic management apparatus 14 is illustrated in FIGS. 1 and 2. The exemplary environment 10 includes a plurality of client computing devices 12(1)-12(n), an active directory server 13, network traffic management apparatus 14, and a plurality of servers 16(1)-16(n) which are coupled together by communication networks 30, although the environment can include other types and numbers of systems, devices, components, and/or elements and 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 providing SSL protected NTLM re-authentication.

Referring more specifically to FIGS. 1 and 2, network traffic management apparatus 14 is coupled to the plurality of client computing devices 12(1)-12(n) and the active directory server 13 through the communication network 30, although the plurality of client computing devices 12(1)-12(n), the active directory server 13, and network traffic management apparatus 14 may be coupled together via other topologies. Additionally, network traffic management apparatus 14 is coupled to the plurality of servers 16(1)-16(n) through the communication network 30, although the plurality of servers 16(1)-16(n) and network traffic management apparatus 14 may be coupled together via other topologies.

The network traffic management apparatus 14 assists with providing SSL protected NTLM re-authentication as illustrated and described by way of the examples herein, although network traffic management apparatus 14 may perform other types and/or numbers of functions. As illustrated in FIG. 2, the network traffic management apparatus 14 may include a processor or central processing unit (CPU) 18, a memory 20, optional configurable hardware logic 21, and a communication system 24 which are coupled together by a bus 26, although the network traffic management apparatus 14 may comprise other types and numbers of elements in other configurations. In this example, the bus 26 is a PCI Express bus in this example, although other bus types and links may be used.

The processor 18 within the network traffic management apparatus 14 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 can execute other types and numbers of instructions and perform other types and numbers of operations. The processor 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 within the network traffic management apparatus 14 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. The 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 processor 18. The exemplary flowchart shown in FIG. 3 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 18 and/or may be implemented by configured logic in the optional configurable logic 21.

Accordingly, the memory of the network traffic management apparatus 14 can store one or more applications that can include computer executable instructions that, when executed by the network traffic management apparatus 14, causes the network traffic management apparatus 14 to perform actions, such as to transmit, receive, or otherwise process messages, for example, and to perform other actions described and illustrated below with reference to FIG. 3. The application(s) can be implemented as module or components of another application. Further, the application(s) can be implemented as operating system extensions, module, plugins, or the like. The application(s) can be implemented as module or components of another application. Further, the application(s) can be implemented as operating system extensions, module, plugins, or the like. Even further, the application(s) may be operative in a cloud-based computing environment. The application(s) can be executed within virtual machine(s) or virtual server(s) that may be managed in a cloud-based computing environment. Also, the application(s), including the network traffic management apparatus 14 itself, may be located in virtual server(s) running in a cloud-based computing environment rather than being tied to one or more specific physical network computing devices. Also, the application(s) may be running in one or more virtual machines (VMs) executing on the network traffic management apparatus 14. Additionally, in at least one of the various embodiments, virtual machine(s) running on the mobile application manager apparatus may be managed or supervised by a hypervisor.

The optional configurable hardware logic 21 in the network traffic management apparatus 14 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 logic hardware device 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”).

The communication system 24 in the network traffic management apparatus 14 is used to operatively couple and communicate between the network traffic management apparatus 14, the plurality of client computing devices 12(1)-12(n), the active directory server 13, and the plurality of servers 16(1)-16(n) which are all coupled together by communication network 30 such as one or more local area networks (LAN) and/or the wide area network (WAN), 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 communication network such as local area networks (LAN) and the wide area network (WAN) can use TCP/IP over Ethernet and industry-standard protocols, including NFS, CIFS, SOAP, XML, LDAP, and SNMP, although other types and numbers of communication networks, can be used. In this example, the bus 26 is a PCI Express bus in this example, although other bus types and links may be used.

Each of the plurality of client computing devices 12(1)-12(n), include a central processing unit (CPU) or processor, a memory, input/display device interface, configurable logic device and an input/output system or I/O system, which are coupled together by a bus or other link. The plurality of client computing devices 12(1)-12(n), in this example, may run interface applications, such as Web browsers, that may provide an interface to make requests for and send and/or receive data to and/or from the plurality of servers 16(1)-16(n) via the network traffic management apparatus 14. Additionally, the plurality of client computing devices 12(1)-12(n) can include any type of computing device that can receive, render, and facilitate user interaction, such as client computers, network computer, mobile computers, virtual machines (including cloud-based computer), or the like. Each of the plurality of client computing devices 12(1)-12(n) utilizes the network traffic management apparatus 14 to conduct one or more operations with the plurality of servers 16(1)-16(n), such as to obtain data from one of the plurality of servers 16(1)-16(n), by way of example only, although other numbers and/or types of systems could be utilizing these resources and other types and numbers of functions utilizing other types of protocols could be performed.

In this example the active directory server 13 include a central processing unit (CPU) or processor, a memory, and a communication system, which are coupled together by a bus or other link, although other numbers and/or types of network devices could be used. In this example, the active directory server 13 assists the network traffic management apparatus 14 with SSL protected NTLM re-authentication, although the active directory server 13 can perform other types or amounts of functions.

Each of the plurality of servers 16(1)-16(n) include a central processing unit (CPU) or processor, a memory, and a communication system, which are coupled together by a bus or other link, although other numbers and/or types of network devices could be used. Generally, the plurality of servers 16(1)-16(n) process requests for providing access to one or more enterprise web applications received from the plurality of client computing devices 12(1)-12(n), network traffic management apparatus 14, or the network traffic management apparatus 14 via the communication network 30 according to the HTTP-based application RFC protocol or the CIFS or NFS 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 plurality servers 16(1)-16(n) that allows the transmission of applications requested by the plurality of client computing devices 12(1)-12(n), or the network traffic management apparatus 14. The plurality of servers 16(1)-16(n) may provide data or receive data in response to requests directed toward the respective applications on the plurality of servers 16(1)-16(n) from the plurality of client computing devices 12(1)-12(n) or the network traffic management apparatus 14. It is to be understood that the plurality of servers 16(1)-16(n) may be hardware or software or may represent a system with multiple external resource servers, which may include internal or external networks. In this example the plurality of servers 16(1)-16(n) may be any version of Microsoft® IIS servers or Apache® servers, although other types of servers may be used.

Although the plurality of servers 16(1)-16(n) are illustrated as single web application servers, one or more actions of each of the servers 16(1)-16(n) may be distributed across one or more distinct network computing devices. Moreover, the servers 16(1)-16(n) are not limited to a particular configuration. Thus, the plurality servers 16(1)-16(n) may contain a plurality of network computing devices that operate using a master/slave approach, whereby one of the network computing devices of the servers 16(1)-16(n) operate to manage and/or otherwise coordinate operations of the other network computing devices. The plurality of servers 16(1)-16(n) may operate as a plurality of network computing devices within cluster architecture, a peer-to peer architecture, virtual machines, or within a cloud architecture.

Thus, the technology disclosed herein is not to be construed as being limited to a single environment and other configurations and architectures are also envisaged. For example, one or more of the servers 16(1)-16(n) depicted in FIG. 1 can operate within network traffic management apparatus 14 rather than as a stand-alone server communicating with network traffic management apparatus 14 via the communication network(s) 30. In this example the servers 16(1)-16(n) operate within the memory of the mobile application manager apparatus.

While network traffic management apparatus 14 is illustrated in this example as including a single device, network traffic management apparatus 14 in other examples can include a plurality of devices or blades each with one or more processors each processor with one or more processing cores that implement one or more steps of this technology. In these examples, one or more of the devices can have a dedicated communication interface or memory. Alternatively, one or more of the devices can utilize the memory, communication interface, or other hardware or software components of one or more other communicably coupled of the devices. Additionally, one or more of the devices that together comprise network traffic management apparatus 14 in other examples can be standalone devices or integrated with one or more other devices or applications, such as one of the plurality of servers 16(1)-16(n) or, active directory server 13, or a network traffic management apparatus 14, or applications coupled to the communication network(s), for example. Moreover, one or more of the devices of network traffic management apparatus 14 in these examples can be in a same or a different communication network 30 including one or more public, private, or cloud networks, for example.

Although an exemplary environment 10 with the plurality of client computing devices 12(1)-12(n), active directory server 13, the network traffic management apparatus 14, and the plurality of servers 16(1)-16(n), communication networks 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).

Further, 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.

One or more of the components depicted in the network, such as network traffic management apparatus 14, plurality of client computing devices 12(1)-12(n), active directory server 13, or plurality of servers 16(1)-16(n), for example, may be configured to operate as virtual instances on the same physical machine. In other words, one or more of network traffic management apparatus 14, plurality of client computing devices 12(1)-12(n), or plurality of servers 16(1)-16(n) illustrated in FIG. 1 may operate on the same physical device rather than as separate devices communicating through a network as depicted in FIG. 1. There may be more or fewer plurality of client computing devices 12(1)-12(n), active directory server 13, network traffic management apparatus 14, or plurality of servers 16(1)-16(n) than depicted in FIG. 1. The plurality of client computing devices 12(1)-12(n) or the active directory server 13 could be implemented as applications on network traffic management apparatus 14.

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 example of a method for improving web scanner accuracy will now be described with reference to FIGS. 1-4. The exemplary method begins at step 305 with the network traffic management apparatus 14 receiving a HTTP request to access a web application in one of the plurality of web application servers 16(1)-16(n) from one of the plurality of client computing devices 12(1)-12(n), although the network traffic management apparatus 14 can receive other types or amounts of requests from other devices. In this example, the network traffic management apparatus 14 receives the request to access the web application upon establishing a TCP/IP connection with the requesting one of the plurality of client computing devices 12(1)-12(n). Additionally in this example, a secured socket layer (SSL) session is also established with the requesting one of the plurality of client computing devices 12(1)-12(n). Further in this example, the network traffic management apparatus 14 enforces the NTLM authentication on the requesting one of the plurality of client computing devices 12(1)-12(n) to access requested web application, although the network traffic management apparatus 14 may not require the NTLM authentication for other types of web application requests.

Next in step 310, the network traffic management apparatus 14 determines when the requested web application is NTLM protected. In this example, the network traffic management apparatus 14 determines that the requested web application or resource is NTLM protected based on the type of web application or resource being requested, although the network traffic management apparatus 14 can use other techniques to make the determination. Accordingly, when the network traffic management apparatus 14 determines that the requested web application is not NTLM protected, then the No branch is taken to step 375 to allow the requesting one of the plurality of client computing devices 12(1)-12(n) access to the requested web application or resource.

However in step 310, when the network traffic management apparatus 14 determines that the requested resource or web application is NTLM protected, then the Yes branch is taken to step 315.

In step 315, the network traffic management apparatus 14 determines when the connection established with the requesting one of the plurality of client computing devices 12(1)-12(n) is NTLM authenticated. When the network traffic management apparatus 14 determines that the connection between the requesting one of the plurality of client computing devices 12(1)-12(n) is NTLM authenticated, then the Yes branch is taken to step 375 where the network traffic management apparatus 14 allows the requesting one of the plurality of client computing devices 12(1)-12(n) access to the requested web application or resource.

However back in step 315, when the network traffic management apparatus 14 determines that the connection between the requesting one of the plurality of client computing devices 12(1)-12(n) is not NTLM authenticated, then the No branch is taken to step 320.

Next in step 320, the network traffic management apparatus 14 sends a HTTP 401 response back to the requesting one of the plurality of client computing devices 12(1)-12(n) responsive to the requested HTTP request to authenticate the with NTLM, although the network traffic management apparatus 14 can request other types of authentication from the requesting one of the plurality of client computing devices 12(1)-12(n). In this example, the network traffic management apparatus 14 sends a HTTP 401 response back to the requesting one of the plurality of client computing devices 12(1)-12(n) because the requesting one of the plurality of client computing devices 12(1)-12(n) does not use a NTLM-authenticated connection and the requested application requires a NTLM authentication.

Next in step 325, the network traffic management apparatus 14 receives a subsequent HTTP GET request to access the web application in the plurality of web application servers 16(1)-16(n) with the Type 1 NTLM negotiate message in the authorization header, although the network traffic management apparatus 14 can receive other types or amounts of information in the subsequent HTTP GET request. By way of example only, Type 1 NTLM negotiate message includes the capabilities of the requesting one of the plurality of client computing devices 12(1)-12(n), although the Type 1 NTLM negotiate message can include other types or amounts of information.

Next in step 330, network traffic management apparatus 14 generates a challenge and sends the generated challenge in a HTTP 401 response back to the requesting one of the plurality of client computing devices 12(1)-12(n). In this example, the network traffic management apparatus 14 includes the TYPE 2 challenge in the header of the HTTP 401 response.

In step 335, the network traffic management apparatus 14 receives another subsequent HTTP GET request to access the web application from the requesting one of the plurality of client computing devices 12(1)-12(n) including a TYPE 3 NTLM authenticate message in the header. By way of example only, the TYPE 3 NTLM authenticate message includes a response to the challenge that was previously sent by the network traffic management apparatus 14, although the TYPE 3 NTLM authenticate message can include other types or amounts of information such as domain name, user name, or server target name.

Next in step 340, the network traffic management apparatus 14 determines when the received response to the challenge is correct by sending the generated challenge and the response received for the challenge from the requesting one of the plurality of client computing devices 12(1)-12(n) to the active directory server 13 and receiving a response back from the active directory server 13. In this example, the active directory server 13 compares the received challenge and the response to the challenge and validates using the user's password stored within the active directory server 13. When the active directory server 13 determines that the received response to the challenge is correct based on the stored information, the active directory sends the network traffic management apparatus 14 a response indicating that the challenge and the response to the challenge is a success. However, if the active directory server 13 determines that the received response to the challenge is incorrect, then the active directory server 13 sends a failure message back to the network traffic management apparatus 14. Alternatively in another example, the network traffic management apparatus 14 can determine when the received response is correct by comparing the received response with a stored response corresponding to the generated challenge in an active directory server 13, although the network traffic management apparatus 14 can use other techniques to determine if the received response is correct.

Accordingly in step 340, when the network traffic management apparatus 14 receives a failure message from the active directory server 13, then network traffic management apparatus 14 determines that the received response is incorrect then the No branch is taken to step 380 where the network traffic management apparatus 14 generates a 401 challenge to re authenticate the requesting one of the plurality of client computing devices 12(1)-12(n) to end the exemplary method.

However in step 340, when the network traffic management apparatus 14 receives a success message from the active directory server 13, then the network traffic management apparatus 14 determines that the response received from the requesting one of the plurality of client computing devices 12(1)-12(n) is correct and then the Yes branch is taken to the next step 345.

In step 345 the network traffic management apparatus 14 allows the requesting one of the plurality of client computing devices 12(1)-12(n) access to the requested web application in one of the plurality of web application servers 16(1)-16(n) as the requesting one of the plurality of client computing devices 12(1)-12(n) has been successfully NTLM authenticated and mark the connection as NTLM authenticated.

Next in step 350, the network traffic management apparatus 14 determines when there is a connection reset message from one of the plurality of web application servers 16(1)-16(n) for which is hosting the web application that is being used by the requesting one of the plurality of client computing devices 12(1)-12(n). In this example, the network traffic management apparatus 14 receives the connection reset message from one of the plurality of web applications when the plurality of web application servers 16(1)-16(n) is operating above a threshold level, unavailable web application in the plurality of web application servers 16(1)-16(n), internal error in the plurality of web application servers 16(1)-16(n), although the network traffic management apparatus 14 can receive the connection reset message for other conditions from the plurality of web application servers 16(1)-16(n). Accordingly, when the network traffic management apparatus 14 determines that there is no connection reset message from the plurality of web application servers 16(1)-16(n), then the No branch is taken back to step 345 where the network traffic management apparatus 14 continues to forward the received response back to the requesting one of the plurality of client computing devices 12(1)-12(n).

However if back in step 350, when the network traffic management apparatus 14 determines that it has received a connection reset request from one of the plurality of web application servers 16(1)-16(n), then the Yes branch is taken to step 355.

In step 355, the network traffic management apparatus 14 stores the challenge that was sent to the requesting one of the plurality of client computing devices 12(1)-12(n), response to the challenge that was received in the NTLM Type 3 authenticate request, the request URI and the SSL session ID in the memory of the network traffic management apparatus 14. Alternatively in another example, the network traffic management apparatus 14 can store this information at other memory locations. In this example, the network traffic management apparatus 14 stores the received response along with the SSL session id and the HTTP request URI in the memory 20 so that the network traffic management apparatus 14 can easily identify the received response when it is required to authenticate the requesting one of the plurality of client computing devices 12(1)-12(n) again on the next TCP connection but within the same SSL connection. In this example, the network traffic management apparatus 14 only stores the response along with the SSL session id and the HTTP request URI only when it receives the connection reset message from the plurality of web application servers 16(1)-16(n).

Next in step 360, the network traffic management apparatus 14 forwards the received connection reset from one of the plurality of web application servers 16(1)-16(n) to the requesting one of the plurality of client computing devices 12(1)-12(n).

In step 365, the network traffic management apparatus 14 receives the same HTTP Request with NTLM TYPE 3 message in a new TCP connection to access the web application in one of the plurality of web application servers 16(1)-16(n) from the requesting one of the plurality of client computing devices 12(1)-12(n), although the network traffic management apparatus 14 can receive other types of request from the requesting one of the plurality of client computing devices 12(1)-12(n).

Next in step 370, the network traffic management apparatus 14 determines when the received TYPE 3 HTTP request from the requesting one of the plurality of client computing devices 12(1)-12(n) is through the same SSL session through which all of the above illustrated requests-responses were exchanged and the requesting one of the plurality of client computing devices 12(1)-12(n) is trying to access the same web application using the same URI that was previously sent. In this example, the network traffic management apparatus 14 uses the information stored in the memory 20 to compare the recently received TYPE 3 HTTP GET request to determine if it is through the same SSL session, and trying to access the same web application with the URI and the request contains the same TYPE 3 HTTP request message, although the network traffic management apparatus 14 can make this determination using other techniques. Accordingly, when the network traffic management apparatus 14 determines that the recently received TYPE 3 HTTP GET request is either not in the same SSL session, or not accessing the same web application or using a different URI, then the No branch is taken back to step 320 where the network traffic management apparatus 14 sends a HTTP 401 response as previously illustrated above.

However if back in step 370, when the network traffic management apparatus 14 determines that the received TYPE 3 HTTP GET request from the requesting one of the plurality of client computing devices 12(1)-12(n) is through the same SSL session through which all of the above requests-responses were exchanged and the requesting one of the plurality of client computing devices 12(1)-12(n) is trying to access the same web application and using same URI and the TYPE 3 HTTP request message is the same as previous message, then the Yes branch is taken to step 375.

In step 375, the network traffic management apparatus 14 proceeds to allow the requesting one of the plurality of client computing devices 12(1)-12(n) to access the web application in one of the plurality of web application servers 16(1)-16(n) and marks the new TCP connection as NTLM authenticated. In this example, the network traffic management apparatus 14 uses the stored response to the challenge, SSL session id and same URI, to allow access to the requesting one of the plurality of client computing devices 12(1)-12(n), although the network traffic management apparatus 14 can use other types or amounts of information to allow the requesting one of the plurality of client computing devices 12(1)-12(n) to access the web application.

The exemplary method ends in step 380 when the requesting one of the plurality of client computing devices 12(1)-12(n) completes using the web application and terminates the TCP/IP connection and SSL session where the network traffic management apparatus 14 also deletes the stored information such as SSL session ID, TYPE 3 message and HTTP URI requesting the web application.

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.