System and method for delegating a user authentication process for a networked application to an authentication agent

Abstract

A system and method for delegating a user authentication process for a networked application to an authentication proxy. A networked application may request a user to provide authentication information in order to access the application. Upon receiving this authentication information from the user, the client side of the networked application sends the information to the server side of the networked application. The server side of the application may then determine an appropriate authentication agent associated with the user to delegate the authentication process to. For example, for each application user, the server side of the application may maintain information associated with the user, such as the user's employer. The application may then match this employer information to an authentication agent running in the employer's network domain, and the authentication process may then be delegated to this authentication agent.

Description

FIELD OF THE INVENTION

[0002] The present invention relates to the field of networked applications, and more particularly to user authentication for networked applications.

DESCRIPTION OF THE RELATED ART

[0003] In the field of computer security, the term “authentication” refers to the process of verifying the identity of a user attempting to gain access to a computing resource or system. Authentication methods generally require the user to provide some type of information. For example, a user may be required to provide a password, provide biometric data such as a retinal scan, provide personal data such as a handwriting sample, provide a number computed based on a synchronized clock in the user's possession, etc. What then occurs with the provided information varies for different authentication protocols. For example, the user's password may be sent to the system in encrypted form, the user's password may be used as a variable in a mathematical function to compute a value which is then sent to the system, etc.

[0004] The issue of authentication may be considered at different levels. For example, authentication may be considered at a system level, such as when a system such as a Windows NT or Unix system verifies that a user attempting to logon has a valid user account and has provided a valid password. Authentication may also be considered at the application level. For example, when a user attempts to launch or access a particular application, the application may present a login screen asking the user to provide a username and password.

[0005] One of the great advantages of the proliferation of common networking technologies, such as Internet browsers, is that users may access networked applications from virtually anywhere. Of course, this also means that the networked applications are highly exposed to unauthorized users. Thus, it is very common today for networked applications, such as Internet-based applications, to include authentication processes for users attempting to access the applications.

[0006] Currently, most networked applications with authentication processes implement the authentication processes independently of other systems or applications. In other words, authentication information for each user is persistently stored on the server side of the networked application, e.g., by maintaining a server-side database including user authentication information. Upon receiving a user request to launch or access the application, this server-side authentication information may be checked against information dynamically provided by the user, e.g., a password, and authorization may be granted or denied based on the results of this check.

[0007] However, there are several problems associated with this approach for performing application-level user authentication. For example, since each application generally maintains its own set of user authentication information, users may have to remember and provide different login information, e.g., different usernames or passwords, for different applications. For example, many networked applications assign login information on a first-come-first-serve basis, e.g., by providing an online registration form in which users choose their own usernames. In this example, a user may desire to use a common username for different applications, but may be forced to choose another username because the desired one is already taken. Also, the user may be forced to choose an unfamiliar password to access an application, e.g., because the password he normally uses does not satisfy the application's rules for password construction. Thus, it would be desirable to provide a system and method for enabling networked applications to avoid storing their own independent set of user authentication information.

[0008] Another problem associated with the approach described above is that user authentication information may be stored in many different places by many different applications using many different methods, which results in a significant security risk. For example, as described above, users may attempt to reuse common information, such as usernames and passwords, to access several different systems or applications. If the security of any one of these systems or applications is compromised then the stored user authentication information could be improperly used not only to access personal user information in the compromised system or application, but also to access personal user information in many other systems or applications. Thus, it would be desirable to provide a system and method that minimizes the storage points of sensitive user authentication information.

[0009] Another drawback associated with the approach described above is that the application developers may have to implement the authentication processes themselves for their applications. This may represent a significant development effort, depending on the size of the user base, the desired level of security, the underlying computing platform the application runs on, etc. The result may be an increase in development costs, a delay in bringing an application to market, security flaws due to developers who are unfamiliar with computer security issues, etc. Thus, it would be desirable to provide a system and method for delegating user authentication procedures to a separate authentication agent.

SUMMARY OF THE INVENTION

[0010] The problems outlined above may in large part be solved by providing systems and methods relating to user authentication for networked applications, such as described herein. A networked application may request a user to provide authentication information in order to access the application. For example, the application may request the user to type in a username and password, the application may request some type of biometric information from the user, such as a fingerprint scan, or the application may request the user to provide another type of authentication information. Upon receiving this authentication information from the user, the client side of the networked application sends the information to the server side of the networked application, possibly in an encrypted form, using any of various methods or protocols. For example, the client side of the application may coordinate with the server side of the application in order to send the information using cleartext methods, hashed password methods, challenge-response methods, etc.

[0011] Upon receiving the authentication information that the user provided to the client side of the networked application, the server side of the networked application may proceed in various ways in order to authenticate the user. In one embodiment, the server side of the application determines an appropriate authentication agent associated with the user to delegate the authentication process to. For example, for each application user, the server side of the application may maintain information associated with the user, such as the user's employer. The application may then match this employer information to an authentication agent running in the employer's network domain, and the authentication process may then be delegated to this authentication agent. The user authentication information that the user provided to the application may be passed to the authentication agent, and the authentication agent may use the information in attempting to authenticate the user. In one example, the user may provide to the application the same username and password that he uses to log in to his employer's system. The application may then pass on the username and password to an authentication agent running in the user's employer's domain. The authentication agent running in the user's employer's domain may then use the username and password in order to attempt to authenticate the user, e.g. by communicating with the employer's system or the system's authentication services in order to authenticate the user. The authentication agent may then communicate the results of its authentication attempt to the server side of the application, which may then act accordingly, e.g. by authorizing the user to use the application or by displaying an error message.

[0012] In one embodiment, the server side of the application communicates with one central, trusted authentication agent for each user. For example, a global authentication service may store user authentication credentials for users of various systems and applications and may accept client requests to verify received authentication information against the stored authentication credentials.

[0013] In one embodiment, the server side of the application may store its own authentication credentials for certain users. The server side of the application may first check to see if it stores authentication credentials for the user in question. If so, the application may use its own stored information to attempt to authenticate the user. If not, the application may delegate the authentication process to an authentication agent, as described above. Of course, the embodiments described above may be combined in various ways. For example, the server side of the application may store its own authentication information for certain users, may store information mapping users to a specific authentication agent for certain other users, and may rely on a default central authentication agent to authenticate the remaining users. Administration tools may be included for mapping users to authentication agents.

BRIEF DESCRIPTION OF THE DRAWINGS

[0014] A better understanding of the present invention can be obtained when the following detailed description of the preferred embodiment is considered in conjunction with the following drawings, in which:

[0015] FIG. 1 illustrates exemplary networked applications; and

[0016] FIG. 2 is a flowchart diagram illustrating one embodiment of a user authentication process involving an authentication agent.

[0017] While the invention is susceptible to various modifications and alternative forms specific embodiments are shown by way of example in the drawings and are herein described in detail. It should be understood however, that drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary the invention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the present invention as defined by the appended claims.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] Incorporation by Reference

[0019] The following reference is hereby incorporated by reference in its entirety as though fully and completely set forth herein:

[0020] U.S. patent application Ser. No. _____ titled “System and Method for Integrating Internet-Based Healthcare Applications” filed Jul. 26, 2000, whose inventors were Fel Bautista, Marco Framba, Venkateshwar Talla, Rajeev Chawla, Rajdeep Gupta, Jeff Nelson, and Steven Lemon.

[0021] FIG. 1—Exemplary Networked Application

[0022] FIG. 1A illustrates an exemplary networked application. It is noted that FIG. 1A represents one embodiment of a networked application, and various other embodiments are possible.

[0023] In FIG. 1A; the networked application is illustrated as a client/server application comprising a client side and a server side. Each client process 100 communicates with a server process 104 via a network 120. The client processes 100 and the server process 104 may be associated with any type of application program or computing service. For example, a client process may communicate with a server process to perform a high-level operation such as an electronic commerce transaction, or the client and server processes may work together to perform a lower-level operation, such as printing a document, etc. The server process 104 typically interacts with some type of server-side resource 106 on behalf of a client process. For example, the server process 104 may retrieve information from or store information to a server-side database 106.

[0024] Each of the client processes 100 may run in any type of client-side environment. For example, a client process may run in a desktop computer or workstation running any of various operating systems, such as Windows, Mac OS, Unix, etc., or a client process may run in a portable computing device, such as a personal data assistant, smart cellular phone, etc. Any number of clients 100 may communicate with the server 104, depending on the type of application running on the system and the resources available to the server, such as network connection speed, processing power, etc.

[0025] Each of the clients 100 may be connected to the server 104 through any of various types of networks 120, e.g., via a direct connection, LAN, WAN, Intranet, Internet, etc., or any combination of these. Each client may use a network connection as a communication channel to send requests and receive responses over the network 120. Any of various types of network protocols may be used to send messages across the network. As messages are sent across the network, the messages may pass through various gateways, network routers, etc. Each client's network connection may be a connection of any type, such as a PPP or SLIP dialup link, an Ethernet or token ring connection, an ISDN connection, a cable modem connection, any of various types of wireless connections, etc.

[0026] Networked applications may be web-based applications or may include web-browsing functionality. FIG. 1B illustrates one embodiment of a networked application with web-browsing capabilities. There are, of course, many possible variations in webbased application architectures, and FIG. 1B is exemplary only.

[0027] As shown in FIG. 1B, the client-side of the networked application may comprise a web browser 132 and application-specific client code 130. The application-specific client code 130 may comprise code packaged in various forms that operate under control of the browser 132, such as Java applets or ActiveX components. The application-specific client code 130 may also use the web browser 132 as a component. For example, the Internet Explorer web browser from Microsoft Corporation exposes an ActiveX/COM interface enabling applications to use Internet Explorer as an embedded component.

[0028] Web-enabled networked applications often comprise client-side code 130 which takes advantage of the familiar interface and popularity of web browsers, utilizing them to handle the user interface/presentation portions of an application, and often the network communication needs as well. However, it is noted that the client-side of a networked application may also run entirely within a web browser 132. For example, a networked application may utilize web pages comprising browser-supported elements such as HTML, XML, Javascript, etc., without relying on additional client-side code 130. FIG. 1C illustrates one such embodiment of a thin-client, browser-only client side.

[0029] The web browser 132 may communicate across a network 150, such as the Internet or an Intranet, with a web server 136. Depending on the application and the request, the web server 136 may broker client application requests to server-side application code 138 for processing, e.g., through interfaces such as CGI, ISAPI, NSAPI, etc. Server-side application code 138 may execute on one or more separate application servers and may interface with one or more server-side databases 140.

[0030] As described above, many networked applications include authentication processes requiring users to provide authentication information in order to access the application. The authentication information may be requested in any of various ways, as appropriate to the application. For example, an application may present a login screen to the user when the application is launched, or a web-based application may present a login screen to the user when the user attempts to access a web page associated with the application, etc.

[0031] As discussed in more detail below, the application may then pass the authentication information to an authentication agent in order to authenticate the user.

[0032] FIG. 2—Delegating User Authentication to an Authentication Agent

[0033] FIG. 2 is a flowchart diagram illustrating one embodiment of a user authentication process involving an authentication agent.

[0034] In step 200 of FIG. 2, a user attempts to access a networked application. As discussed above with reference to FIG. 1, the networked application may be an application for any purpose, and may have various architectures. Thus, a user may attempt to access the networked application in various ways, as appropriate for a particular system or application. For example, a user may attempt to access a web-based application by accessing a uniform resource locator (URL) associated with the application, e.g., by providing the URL to a web browser. For other types of networked applications, step 200 may differ. For example, the user may attempt to access a networked application by dialing in to the application through a modem, etc.

[0035] In step 202 of FIG. 2, the networked application obtains authentication information from the user. An application may request any of various types of authentication information, such as a username and password, biometric information, information based on some item in the user's possession, such as a synchronized clock, or any other type of authentication information. The application may request the authentication information in any of various ways, as appropriate to the particular application, the type of authentication information being requested, etc. For example, the application may present a form or window for the user to provide text-based information, the application may interface with a hardware device to request biological information, etc.

[0036] In step 204 of FIG. 2, the client side of the networked application contacts the server side of the networked application in order to authenticate the user. The client side of the networked application may pass the authentication information obtained from the user in step 202 to the server side of the networked application. The authentication information may be passed in various forms, e.g., the information may be encrypted, digitally signed, etc. The client side and the server side of the networked application may communicate using any of various communication protocols. For example, the client side and server side may use the Secure Sockets Layer (SSL) standard protocol, other TCP/IP-based protocols, etc., for communication.

[0037] As shown in step 206 of FIG. 2, in one embodiment the server side of the networked application may determine whether the server side of the application stores authentication credentials for the user that can be used for authenticating the user. For example, the networked application may be a healthcare application that enables users to perform healthcare-related operations, such as accessing medical journals, viewing the status of their health insurance claims, etc. In this example, particular groups, such as employers or organizations, may coordinate with the healthcare application administrator in order to enable each group member, such as each employee, to access the application. In this case, the server side of the healthcare application may not store authentication credentials for users who are members of such groups, but may delegate the authentication process to an authentication agent associated with the user's group, as explained in more detail below.

[0038] However, the healthcare application may also allow independent users to access the application, e.g., by purchasing a subscription, etc. In this case, the server side of the application may itself store the user's authentication credentials, and the networked application itself may perform the authentication process for these types of users, rather than delegating the authentication process to an authentication agent. Of course, there are many other scenarios that may make it desirable for a networked application to store authentication credentials for only a portion of its users. Also, it is noted that in one embodiment, the application does not store authentication credentials for any of its users, but always delegates the authentication process to authentication agents.

[0039] The networked application may determine whether authentication credentials for the user are maintained by the application itself in any of various ways. For example, the application may maintain a database comprising user information, wherein information for each user can be accessed using a key that the user provides in step 202, such as a username, etc. In this example, the application may then access the user's records in the database and determine from the records whether or not the authentication credentials, such as the user's password, are stored by the application.

[0040] If the server side of the networked application determines in step 206 that the application does not maintain authentication credentials for the user, then in step 208 of FIG. 2, the server side of the networked application determines an appropriate authentication agent to contact for authenticating the user. For example, as discussed above, a user may be associated with a particular employer, and the employer may have an associated authentication agent running on one of the employer's servers. The appropriate authentication agent may be determined in various ways. For example, as described above, the server side of the networked application may maintain a database of user information that may be accessed based on a key, such as the user's username or another key that the user provides in step 202, and the application may access this database to determine the appropriate authentication agent associated with the user. The information regarding authentication agents may be stored or specified in various ways. For example, network addresses, such as IP addresses or port numbers, may be stored for each authentication agent, parameters associated with each authentication agent may be stored, etc.

[0041] In step 210 of FIG. 2, the server side of the networked application contacts the appropriate authentication agent in order to authenticate the user. In one embodiment, the server side of the application may interface with a separate process or thread referred to as an authentication proxy, which is responsible for communicating with the authentication agent. The authentication proxy may pass the authentication information obtained from the user in step 202 to the authentication agent, and the authentication agent may then use the information in whatever way is appropriate to attempt to authenticate the user.

[0042] In one embodiment, the authentication agent interfaces with a network operating system, such as a Windows NT system, Unix system, etc., and carries out an authentication process with the system. For example, as described above, the authentication agent may be associated with a particular company or organization. The authentication agent may interface with the company or organization's computer system, e.g., in order to verify that a username and password that the user provided in step 202 is a valid username/password combination for the computer system. As is well known in the art, there are various ways in which such an authentication agent may interface with a system to perform an authentication procedure.

[0043] Other embodiments are also contemplated, in which the authentication agent interfaces with various other types of systems or applications. For example, the networked application may be a networked application A that is associated with another networked application B. Networked application B may maintain user authentication credentials for users that are common to both application A and application B, and application A may delegate the authentication process for these common users to an authentication agent associated with application B, whenever such a user attempts to access application A.

[0044] Also, in one embodiment the networked application may communicate with a central, trusted authentication agent to authenticate a portion of or all of the application users. For example, this authentication agent may be associated with a central, trusted computer security service provider who stores information such as user passwords, user encryption keys, etc., and provides services such as user authentication services to many systems or applications. In this example, the application may first check to see that the claimed user is a valid user of the application, e.g., by checking the user's username or other identifying key against a set of subscribed application users, and the application may then delegate the task of verifying the user's identity to the central authentication agent.

[0045] In step 212 of FIG. 2, the authentication agent returns the results of the authentication process performed in step 210 to the authentication proxy, e.g., whether or not the user was successfully authenticated against his authentication credentials, possibly along with an error or status message, etc. The authentication proxy and the authentication agent preferably exchange information in encrypted form, using a secure protocol. Any of various communication protocols may be used to communicate between the proxy and the agent, such as the standard secure sockets layer (SSL) protocol, other TCP/IP-based protocols, etc. It is noted that different authentication agents may communicate with the server side of the networked application using different communication protocols, message formats, etc. Thus, the server side of the application may be constructed according to a modular architecture that allows multiple authentication proxies to be incorporated into the application. From step 212, the flowchart logic proceeds to step 216 of FIG. 2.

[0046] If the server side of the networked application determines in step 206 that the application does store authentication credentials for the user, then in step 214 of FIG. 2, the server side of the networked application uses the stored authentication credentials to attempt to authenticate the user. The server side of the application may verify the authentication information provided by the user in step 202 against the authentication credentials in any of various ways, depending on the type of credentials, how the credentials are stored, etc. From step 214, the flowchart logic proceeds to step 216 of FIG. 2.

[0047] In step 216 of FIG. 2, the server side of the networked application interprets the results of the authentication process performed in step 210 or step 214. If the authentication was successful, then in step 218 of FIG. 2, the application authorizes the user to access the application. Step 218 may take on various forms depending on the type of application, the level of authorization granted to the user, etc. For example, for a web-based application, step 218 may involve returning an HTTP cookie to the user's web browser, where the cookie is used to enable the user to perform subsequent requests to interact with the application.

[0048] If the authentication process in step 210 or 214 was unsuccessful, then in step 220 of FIG. 2, the application behaves accordingly. For example, the application may display an error message, may ask the user to re-submit his authentication information, etc.

[0049] As noted above, FIG. 2 represents one embodiment of a user authentication process involving an authentication agent. Thus, the flowchart of FIG. 2 is exemplary, and various steps may be combined, omitted, added, or modified as required or desired for different systems or applications. For example, steps 206 and 214 may be omitted if the application does not store its own authentication credentials for any users. As another example, communication steps may be combined in some embodiments. For example, some communication protocols, such as various cryptographic protocols, involve passing information between a sender and a receiver in a stepped, iterative manner.

[0050] Application Integration

[0051] The system and method described herein may be applied for any of various types of applications. The above-incorporated patent application, titled, “System and Method for Integrating Internet-Based Healthcare Applications,” describes a system and method for integrating independent Internet-based applications via an application shell. A user may access a master server environment, providing authentication information, and may receive data for implementing an application shell, e.g., an application shell which runs within the environment of a web browser. The application shell may include a graphical user interface and other means for integrating a set of networked applications. For example, a group of healthcare-related applications, such as an application for accessing online medical journals, an application for filing health insurance claims, an application for ordering laboratory results, etc., may be integrated via the application shell. The integration provided by the application shell may include such capabilities as single sign-on authentication, application context-sharing, etc.

[0052] In various embodiments, the present invention may be utilized in order to delegate the authentication process for accessing the application shell and/or accessing the applications accessible via the application shell to an authentication agent.

[0053] Although the system and method of the present invention has been described in connection with the preferred embodiment, it is not intended to be limited to the specific form set forth herein, but on the contrary, it is intended to cover such alternatives, modifications, and equivalents, as can be reasonably included within the spirit and scope of the invention as defined by the appended claims.

Claims

1. A method for authenticating a user of a networked application, wherein the networked application has a client side and a server side, the method comprising: the server side of the networked application receiving authentication information for the user from the client side of the networked application; the server side of the networked application determining an appropriate authentication agent to contact for authenticating the user; the server side of the networked application passing the authentication information to the authentication agent; the authentication agent using the authentication information to attempt to authenticate the user; the authentication agent communicating the results of the authentication attempt to the server side of the networked application; the server side of the networked application authorizing the user to access the networked application if the authentication attempt was successful.

2. The method of claim 1, wherein the authentication information passed to the authentication agent comprises account information for the user, wherein said authentication agent using the authentication information to attempt to authenticate the user comprises the authentication agent passing the account information to a network computer system with which the authentication agent is associated; wherein, in response to receiving the account information from the authentication agent, the network computer system uses the account information to verify that the network computer system has a user account matching the account information.

3. The method of claim 2, wherein the account information for the user comprises a username and password.

4. The method of claim 2, wherein the server side of the networked application stores information associated with the user; wherein the server side of the networked application uses the authentication information received from the client side of the networked application to access the information associated with the user, wherein the information associated with the user comprises information regarding a group of which the user is a member; wherein the server side of the networked application stores information regarding an authentication agent associated with the group of which the user is a member; wherein the server side of the networked application passes the authentication information to the authentication agent associated with the group of which the user is a member.

5. The method of claim 4, wherein the group of which the user is a member is the user's employer.

6. The method of claim 2, wherein the network computer system is a network computer system from the group consisting of: a Windows NT system and a Unix system.

7. The method of claim 1, further comprising: the server side of the networked application determining whether the server side of the networked application stores authentication credentials for the user; the server side of the networked application attempting to authenticate the user using the user's stored authentication credentials if authentication credentials for the user are stored by the server side of the networked application; the server side of the networked application passing the authentication information to the authentication agent in order to authenticate the user if authentication credentials for the user are not stored by the server side of the networked application.

8. A system for authenticating a user of a networked application, the system comprising: a first computer system running software associated with a client side of a networked application; a second computer system connected to the first computer system via a network, wherein the second computer system runs software associated with a server side of the detworked application; a third computer system connected to the second computer system via a network, wherein the third computer system runs an authentication agent; wherein the software associated with the server side of the networked application is operable to: receive authentication information for the user from the software, associated with the client side of the networked application; determine that the authentication agent running on the third computer system should be contacted in order to authenticate the user; pass the authentication information to the authentication agent; wherein the authentication agent is operable to: use the authentication information to attempt to authenticate the user; communicate the results of the authentication attempt to the software associated with the server side of the networked application; wherein the software associated with the server side of the networked application is operable to authorize the user to access the networked application if the authentication attempt was successful.

9. The system of claim 8, wherein the authentication information passed to the authentication agent comprises account information for the user; wherein said authentication agent using the authentication information to attempt to authenticate the user comprises the authentication agent passing the account information to a network computer system with which the authentication agent is associated; wherein, in response to receiving the account information from the authentication agent, the network computer system is operable to use the account information to verify that the network computer system has a user account matching the account information.

10. The system of claim 9, wherein the account information for the user comprises a username and password.

11. The system of claim 9, wherein the second computer system includes a memory storing information associated with the user; wherein the software associated with the server side of the networked application is operable to use the authentication information received from the software associated with the client side of the networked application in order to access the information associated with the user; wherein the information associated with the user comprises information regarding a group of which the user is a member, wherein the memory of the second computer system also stores information specifying an authentication agent associated with the group of which the user is a member; wherein the software associated with the server side of the networked application is operable to access the memory to determine the authentication agent associated with the group of which the user is a member and is operable to pass the authentication information to the authentication agent associated with the group of which the user is a member.

12. The system of claim 11, wherein the group of which the user is a member is the user's employer.

13. The system of claim 9, wherein the network computer system is a network computer system from the group consisting of: a Windows NT system and a Unix system.

14. The system of claim 8, wherein the second computer system includes a memory storing authentication credentials for a plurality of users; wherein the software associated with the server side of the networked application is operable to: access the memory in order to determine whether the memory stores authentication credentials for the user; attempt to authenticate the user using the stored authentication credentials for the user if authentication credentials for the user are stored on the memory; pass the authentication information to the authentication agent in order to authenticate the user if authentication credentials for the user are not stored on the memory.