Imported: 17 Feb '17 | Published: 10 Jan '12
USPTO - Utility Patents
A method, system, and computer readable medium for facilitating user authentication for accessing an application hosted on an external web site by users in an enterprise network. A request is received from a user a request is received from a user to access the application on the external web site. The user is redirected to a secure web page on an enterprise server to log in to the enterprise server. Authentication information for the user is formatted in compliance with a login specification for the application hosted on the external web site. The authentication information is encrypted in compliance with the login specification for the application hosted on the external web site. The user is then directed to the application hosted on the external web site, wherein the user can access the application without having to reenter login information.
Embodiments of the invention relate generally to sign-on procedures for software applications on a computer network and, more particularly, to methods and systems for user authentication for web-based applications in a corporate wide area network.
Authentication and authorization are two basic computer security concepts. In general, authentication refers to verifying the identity of a user attempting to gain access to a computing resource or system, and authorization refers to granting an authenticated user permission to access the resource or system, at least to a degree. There are many methods and protocols for performing authentication, each with various advantages and disadvantages. For example, authentication may be performed using cleartext password methods, hashed password methods, challenge-response methods, or any of many other types of methods.
One common denominator of authentication methods is that they require the user to provide some type of information or perform some action. For example, a user may be required to provide a password, provide biological 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. Of course, 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.
One major problem which users face is that as they attempt to interact with multiple systems or multiple resources within a system, they are often required to provide authentication information multiple times. This imposes practical problems to users, such as having to remember or store multiple passwords, having to have a synchronized clock currently in their possession, etc., as well as the frustrating workflow problems of being interrupted to type in a password, etc. A concept known as “single sign-on” aims to address these types of problems. The idea behind single sign-on is that a user is authenticated once, in response to providing information or performing an action as described above, and then further authentication procedures are performed transparently to the user as he attempts to access other systems or resources.
The issue of authentication may, of course, be considered at many 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 a system resource level. For example, an application which a user attempts to launch may authenticate the user, or an application may authenticate the user when he attempts to open a particular file, etc. In the case of application-level authentication, the application may utilize a protocol or method of its own, and/or authentication data of its own, to perform the authentication process, or the application may rely on system-level authentication services or protocols for authenticating the user.
Most efforts to enable single sign-on have approached the problem by attempting to incorporate system-level authentication services or protocols into the computing environments in question. Kerberos is one well-known example of this type of approach. In the Kerberos approach, a user provides authentication information to a Kerberos server. In response, the Kerberos server grants the user a ticket-granting ticket. The user may then present this ticket-granting ticket to a ticket-granting server in order to get a server ticket. This server ticket may then be used to access resources such as applications. Other attempts to enable single sign-on by building it into the system level include IBM Corporation's KryptoKnight and Axent Technologies Inc.'s Enterprise Resource Manager.
Such approaches to single sign-on generally aim to provide a comprehensive, very secure authentication infrastructure able to provide system-wide authentication services for applications and other resources. While this may seem ideal, there are several disadvantages involved. For example, in order to introduce this type of single sign-on capability to an existing system, the system may have to be modified significantly. For example, the Kerberos approach may require the Kerberos server, the ticket-granting server, etc. to be set up. Additionally, user machines may need to be modified with special client-side software for the system's authentication protocol. Once the necessary modifications have been made to a system, there is the problem of how to define the authentication logic for the system. For example, many systems comprise multiple servers in different locations. System administrators must decide which of these servers the single sign-on policy applies to, which users the policy applies to, etc.
Assuming that the system's single sign-on policy can be adequately defined and supported by the authentication infrastructure; and that any necessary modifications can be made to applications and other resources in order to take advantage of the authentication services, the problem of system interoperability remains. For example, if a user of the system attempts to access an application on a separate system, the user may need to be authenticated again, even if the separate system has single sign-on capabilities of its own.
Focusing now on networked applications, such as web-based applications or other Internet or Intranet applications, the problems described above are magnified. Many networked applications require users to be authenticated, e.g. by entering a username and password on a login screen. As networked applications become increasingly interconnected, it becomes more desirable to enable single sign-on capabilities for them. For example, it may be desirable to enable a user of a web-based application to launch a second application, e.g., by clicking on a hypertext link, and have the second application launch immediately, bypassing an interactive authentication process that the user may normally have to perform when launching the second application.
Single sign-on approaches such as the ones described above may be unsuitable for integrating networked application authentication processes. For example, a developer of a networked application may wish to enable single sign-on to a large number of other networked applications, each of which may run on different systems. It may be impossible or infeasible to make the types of modifications described above to each system. Assuming this obstacle can be surmounted, other obstacles may remain, such as installing any necessary client software on each user's machine, defining the access rights of users who connect to a system via a network connection, etc. If a networked application were ported to a new system or a new server within a system, various steps in this process may have to be repeated.
Embodiments of the invention are directed to a common secure web authentication for web applications. The web authentication tool provides a common secure login process for all internal and external web applications. Embodiments of the invention provide one login to access all of a large enterprise's web applications. Embodiments of the invention also provide a way to determine if a user accessing enterprise web applications is logged in and secure. If the user is not, then the user will be redirected to a common login screen that will provide a link to register the user if the user has not done so previously.
In an exemplary embodiment, a method, system, and computer readable medium are provided for facilitating user authentication for accessing an application hosted on an external web site by users in an enterprise network. In the method, a request is received from a user to access the application on the external web site. The user is redirected to a secure web page on an enterprise server to log in to the enterprise server. Authentication information for the user is formatted in compliance with a login specification for the application hosted on the external web site. The authentication information is encrypted in compliance with the login specification for the application hosted on the external web site. The user is then directed to the application hosted on the external web site, wherein the user can access the application without having to reenter login information.
The system includes a plurality of components that perform the steps of the method when operated on a computer system. The computer readable medium has computer instructions embedded therein, the computer readable medium implementing the method when operated on the computer system.
The following description is provided as an enabling teaching of embodiments of the invention. Those skilled in the relevant art will recognize that many changes can be made to the embodiments described, while still obtaining the beneficial results. It will also be apparent that some of the desired benefits of the embodiments described can be obtained by selecting some of the features of the embodiments without utilizing other features. Accordingly, those who work in the art will recognize that many modifications and adaptations to the embodiments described are possible and may even be desirable in certain circumstances, and are a part of the invention. Thus, the following description is provided as illustrative of the principles of the embodiments of the invention and not in limitation thereof, since the scope of the invention is defined by the claims.
In addition to a common secure login, the embodiments disclosed provide a number of capabilities including, but not limited to: (1) a single web authentication token which uniquely identifies a user; (2) a web site to be used by administrators in the various support centers to centrally manage identities; (3) various components for calling applications to retrieve information about a logged-in user; (4) a web site for existing customers to login, new customers to register, and a method for existing users to change their password; and (5) a terms of service page that must be accepted by all first-time users.
Users can include internal employees and external customers who use the enterprise web applications remotely through the Internet. The web authentication tool features include the following: (1) provide a common, secure, web login; (2) provide a highly available web login; (3) provide a secure means to register a new user; (4) provide a user with a single login identity for all web applications; and (5) provide a common security model across all web applications.
The Web Authentication tool was written to be a “Single Sign-On” solution (SSO) for a complete Enterprise Authentication solution. There is one common login site that every application uses for login. The site is on the enterprise's external web farms and can be leveraged by internal and external applications.
Once authenticated, a security token representing the user's identity is stored in the browser session. The security token identifies the user as a valid user during his visit to the website. The encryption and expiration of that token is centrally managed by the Web Authentication tool which knows how to check the values. All applications use this common form of identity. The token itself can contain an Active Directory or any qualifying system identity and is not limited to any specific type. The security token will be set to expire after a fixed period, e.g., 8 hours. After this period, an attempt to reuse the token will cause the user to be redirected to the login page. The login site could have a security certificate set to only allow 128-bit encrypted communication with the site.
FIG. 1 illustrates a web authentication architecture diagram in accordance with an exemplary embodiment. The diagram depicts internal web authentication users 100 connecting directly to a web server farm 120, and external web authentication users 170 connecting to the web server farm 120 through a firewall 110. The web server farm 120 is operationally connected to a communication server farm 130 which in turn, is connected operationally to application servers 140, 150, 160.
The login site is platform-independent and uses basic HTTP GET and POST functions for integration into calling applications. The login screen is customizable to the calling application's look and feel. The application also can specify user requirements for login (e.g., “Employees Only”). Each registering user must comply with the terms of service upon registering.
The databases have failover in order to meet high availability requirements. The sites run on a web server farm and are monitored through a script on each site that performs unit tests frequently. This script is called from an external system to ensure approximately 99.99% uptime. The web site uses components that talk to the database (the web site cannot directly communicate with the database, but only through highly-secured components). All websites using the Web Authentication tool must run under Secure Sockets Layer (SSL). The Web Authentication tool supports multiple password strength levels.
In an exemplary embodiment, the password must satisfy one or more of the following requirements, depending on the strength level needed: (1) expire on a periodic basis, (2) contain at least “n” characters, (3) contain both alphabetic and numeric characters, (4) contain both upper and lower case letters, (5) not be a dictionary word, (6) not have been used in the past, (7) not contain more than “n” contiguous repeating characters, (contain at least one non-printable characters, such as the “tab” character. FIG. 3 illustrates a reset password user interface in accordance with an exemplary embodiment in a scenario in which all of the preceding requirements must be satisfied to satisfy the strength levels requirements for a new password.
FIG. 4 illustrates another reset password user interface that the user could receive after clicking the submit button in FIG. 3 if any of the listed conditions occurred when attempting to reset the user's password. Only one of the conditions would actually display on the user interface. The user interface would display “password is required” if the user clicked the submit button without entering a password. The user interface would display “password confirmation is required” if the user did not enter the password in the confirm password field. The user interface would display “the passwords do not match” if the password and confirm password entries did not match. The user interface would display if there was an error in saving the password.
There is a transfer page mechanism that can translate the enterprise's secure identity into a format required by external authentication systems. This transfer page mechanism is referred to herein as Hosted Redirect and supports various encryption algorithms, hashes, formats, certificates, etc. that an external site would need to accept a login externally without presenting a login page. FIG. 2 illustrates processing logic for a transfer page mechanism that translates an enterprise's secure identity into a format required by an external authentication system in an exemplary embodiment.
Hosted Redirect is a web page mechanism that facilitates user authentication for externally hosted applications. Users can login using Web Authentication and their familiar username and password. This login mechanism requires that the hosted application implement some custom code to receive a custom token and then log the user in through the normal authentication process.
As illustrated in FIG. 2, user 200 logs in using Web Authentication with username and password and wants to go to an externally hosted application on web site 236. The user is taken to the Hosted Redirect page 204 that is hosted on the enterprise secure web site (e.g., https://WebAuthentication.Enterprise.com). As indicated in block 208, the user must login if not yet logged into another application. The user's authentication information is formatted based on the specification for the external application, as indicated in block 212. The user's authentication is then encrypted based on the external application's specifications as indicated in block 216.
The user is directed to the externally hosted application as indicated in block 220. This is followed in block 224 with the external site decrypting user authentication information. The external site then authenticates the user based on its internal authentication mechanisms, as indicated in block 228. Once the user is authenticated, the external application functions as it would normally function, as indicated in block 232. This completes the process for the user 200 accessing the externally hosted web site 236.
As an example of the use of Hosted Redirect, consider an electronic commerce procurement (e-procurement) site that is hosted off-site (i.e., not on the enterprise's website) on which the enterprise's internal employees would like to utilize their normal usernames and passwords to login. One such e-procurement site used for procurement in the energy industry is that provided by Pantellos Corporation. Pantellos Corporation was launched in 2000 to operate and manage an open, independent marketplace for the purchase of goods and services between the energy industry and its suppliers. In this example implementation, Pantellos can partner with the enterprise to utilize the Hosted Redirect page to meet this requirement. Pantellos could build a page on its site to receive parameters from the enterprise. A user could then click on an e-procurement icon on an enterprise web page. After clicking on the icon, the user is actually taken to https://WebAuthentication.Enterprise.com/HostedRedirect.aspx?app=buy where “buy” is the application name in the Hosted Redirect database. This web page is also referred to herein as the Hosted Redirect page. The user would then login using Web Authentication. If the user has already logged into Web Authentication in the same browser window, the user is not shown the login page again since the user has already been authenticated.
Hosted Redirect then looks up “buy” in the database, creates a custom token according to the configuration for “buy” in the database, and redirects user to the Pantellos site at https://test.pantellos.com/extauth/auth.aspx?co=enterprise&id=<EncryptedCustomToken>&app=buy.
In this example, the Pantellos application would decrypt the ID querystring argument (using the same format and encryption configuration that the enterprise used to encrypt it) and log the user into the e-procurement application.
Redirect Uniform Resource Locator (URL) Parameters
When redirected to the externally hosted application, the following format is used:
Query strings are the part of a URL that contains data to be passed to web applications.
The following is a list of query string arguments that could be used in exemplary embodiments:
co—identifies the enterprise as the source of the custom token. This allows the hosted application to reuse the custom login page for other companies.
id—the custom token; formatted and encrypted according to the hosted application's specifications
<original querystring arguments>—the contents of the user's original request to the Hosted Redirect page. This allows for the hosted application to accept additional parameters.
FIG. 5 illustrates an exemplary top level database configuration table related to the client web application. The top level information includes the return URL and the return type. The web page address in the “Return_URL” field is also referred to as the Hosted Redirect page. All parameters for the custom token format and encryption are fully customizable on a per application basis. FIGS. 6A-6C illustrate a database configuration table for storing the encryption data used by Hosted Redirect to create the custom token for the requesting web application. This database configuration table defines the token contents, encryption algorithm, and encryption keys that should be used to build the custom token. Hosted Redirect provides a unique token to each application requiring a custom token. The benefits of having a unique token for each application are increased security and flexibility.
The hosted application can specify the Uniform Resource Locator (URL) and format for the custom token as discussed in the following paragraphs.
URL—the URL of the page on the externally hosted application's site that knows how to handle custom token arguments. This page on the externally hosted application's site must be running with Secure Sockets Layer (SSL).
Custom Token Format—the format of the custom token. For example, the custom token format might be “SID|Expiration” to return the user's Security Identifier (SID) and the time that the user's token expires. The following fields are supported in the custom token in an exemplary embodiment:
SID—user's SID (80 characters). This is the only guaranteed unique identifier.
ShortSID—hashed version of the user's SID (32 characters). This is not guaranteed to be a unique identifier.
SCID—user's enterprise ID (e.g., employee number).
Expiration—UTC timestamp of when the token expires. The use of a UTC timestamp for token expiration is strongly recommended. The hosted site must verify that the custom token has not expired.
Username—user login ID. This is not recommended as a primary key since it is not a unique value; instead, SID or ShortSID should be used.
FirstName—user's first name
LastName—user's last name
Email—user's e-mail address
The hosted application can also specify the following parameters for encryption:
Cipher—the encryption algorithm to be used. In an exemplary embodiment, available ciphers could include: RC2, DES, TripleDES, Rajindael.
Cipher Format—format of the cipher text. In an exemplary embodiment, available formats could include: Base64Encoded, HexString, Binary.
Hash—the algorithm that produces a one-way digest from a given key. In an exemplary embodiment, available hashes could include: MD5, SHA1, None.
Mode—the cipher block mode to use for encryption. In an exemplary embodiment, available modes could include: CBC, CFB, ECB.
Padding—the type of padding to apply when the message data block is shorter than the full number of bytes needed for a cryptographic operation. In an exemplary embodiment, available padding modes could include: None, PKCS7, Zeroes. As is well known, PKCS7 is a public key cryptographic message syntax standard developed by RSA Laboratories that describes general syntax for data that may have cryptography applied to it, such as digital signatures.
Date Format—format of dates returned in the custom token. All dates are in Universal Coordinated Time. In an exemplary embodiment, the data format might be “MM-dd-yyyy HH:mm:ss”.
Encryption Key—the key to be used to encrypt and decrypt the custom token.
Initialization Vector—used to initialize blocks of encrypted text. The initialization vector is typically zero-filled. If specified, it must conform to a fixed size defined by the cipher.
The Encryption Key and Initialization Vector parameters are considered “secrets” and must be protected. Because of this, both are encrypted within the database used for Hosted Redirect.
The hosted application cannot specify the character encoding to use. In exemplary embodiments, ASCII encoding can be used.
The system and method embodiments have been described as computer-implemented processes. It is important to note, however, that those skilled in the art will appreciate that the mechanisms of the disclosed embodiments are capable of being distributed as a computer readable medium in a variety of forms, regardless of the particular type of physical signal bearing media utilized to carry out the distribution. Examples of physical signal bearing media include, without limitation, recordable-type media such as flash drives, portable hard drives, diskettes, and CD ROMs.
The corresponding structures, materials, acts, and equivalents of all means plus function elements in any claims below are intended to include any structure, material, or acts for performing the function in combination with other claim elements as specifically claimed. Those skilled in the art will appreciate that many modifications to the exemplary embodiment are possible without departing from the scope of the invention.
In addition, it is possible to use some of the features of the embodiments described without the corresponding use of the other features. Accordingly, the foregoing description of the exemplary embodiments is provided for the purpose of illustrating the principles of the invention, and not in limitation thereof, since the scope of the invention is defined solely by the appended claims.