1. Technical Field
The invention relates generally to Internet based authentication technology. More particularly, the invention relates to a method and system for monitoring Web browsing activity across an Internet based network of affiliated sites and for enabling said sites to detect and to force re-authentication upon a user who has had a period of network-wide inactivity longer than a site-specific maximum allowable inactivity period.
2. Description of the Prior Art
To request a service or conduct other electronic transaction in an Internet based network, a user is usually required to go through an authentication process. In other words, the user must provide the seller or service provider with some information such as his personal identification, contact information, or even financial information. The authentication process may take from several seconds to several minutes. Because each seller or service provider usually maintains its own authentication server and database, millions of sellers and service providers might share thousands or millions of consumers or users. Some of the consumers or users might be required to go through the same or substantially similar authentication process again and again if they have transactions with many sellers or service providers. This repetitive authentication not only wastes consumers' precious time, but also burdens the sellers or service providers because they have to expand their databases to keep detailed authentication information for a growing number of users. This situation brings forth a technical need to create a universal, unified, single-logon infrastructure wherein a specific user may be authenticated once for all and the authentication result is widely recognized by a large number of sellers or service providers.
In responding to that need, several approaches have been developed. For example, Microsoft Corporation has introduced a “.NET Passport” single sign-in system. With “.NET Passport”, a user does not need to register a member name and password at each new site he visits. The user may simply use his e-mail address and password that registered as his “.NET Passport” to sign in to any participating site. The information the user registers with “.NET Passport” is stored online, securely, in the “.NET Passport” database as the user's “.NET Passport profile.” When the user signs on to a “.NET Passport” participating site by typing his e-mail address and password in the “.NET Passport” sign-in box, “.NET Passport” confirms that (1) the e-mail address he typed is registered with “.NET Passport”, and (2) the password he typed is correct. “.NET Passport” then notifies the site that the user has provided valid “sign-in credentials,” and he is given access to the participating site. Once the user signs in to one “.NET Passport” participating site during an Internet session, he can sign in to other sites simply by clicking the “.NET Passport” sign-in button available at each site.
Another example is America Online Incorporated (AOL)'s “Screen Name Service” system, which provides free service allowing anyone with a “Screen Name” to easily and securely register at a variety of Web sites. As with to Microsoft's “.NET Passport” system, the “Screen Name Service” eliminates a user's need to remember multiple names and passwords for all the places he visits on the Web. With the “Screen Name Service” system, each user has a “My Profile”, which stores the user's personal information used to make registration at sites across the Web simple and secure. When the user registers at a participating site using the service, he has the opportunity to choose which fields of information stored by AOL, if any, he would like to share with that site. No information is shared with any site without the user's explicit permission. When the user agrees to share certain information with a participating site, that information is conveyed to the site at which he is registering. Another feature is that the user is provided with a “My Site List”, which is an effective way to manage personal information because it shows the user with which sites he has registered using the service. The user can view the privacy policy of a site to see how it uses information it knows about the user. The user can also decide if he would like to be signed into the site without being prompted and if the site should be updated with information when “My Profile” changes.
The common characteristic of these approaches is that they implement a centralized solution for authentication and authentication information management. Undoubtedly, the centralized solution may overcome the repetitive authentication and repetitive storage problems that exist in the scattered, disorganized situation.
In these networks, a user's inactivity is typically tracked only upon individual sites versus at the network level, and thus the user who is active in a network but inactive on a particular site gets inadvertently timed out on that site. For example, if the user had not completed and sent his message in Site A before he switched to Site B, after a predefined duration of a single, continuous session is over, his workflow in Site A will interrupted and the data he created in the session will be lost. Because of this, time has been wasted, efficiency lost, resources wasted, and distraction, annoyance and stress increased.
What is desired is a mechanism to monitor Web browsing activity across an Internet based network of affiliated Web sites so that a Web site does not time-out a session for a user who has been inactive in the Web site for period of time longer than a predefined maximum allowable inactivity period Pmax but his network-wide inactivity duration has not been longer than Pmax, so that the Web site forces the user to re-authenticate if his network-wide inactivity duration has been longer than Pmax.
This invention provides a method and system for monitoring Web browsing activity across a network of affiliated Web sites and for enabling the Web sites to detect and to force re-authentication upon users who have had a period of network-wide inactivity greater than a site-specific maximum allowable inactivity period, wherein the network comprises at least one network authentication server (NAS). The steps of this method, for example, include: (1) the NAS updates the user's NATr parameters in the NATr cookie upon performance of each activity indicating event by the user in the network; (2) The NAS updates the user's NATr parameters in the NATr cookie upon performance of each activity indicating event by the user in the network; (3) the NAS determines upon request the maximum period of network-wide inactivity experienced by the user since his last network authentication; and (4) The NAS re-authenticates the user if the maximum period of network-wide inactivity exceeds the predefined threshold (Pmax).
In the first preferred embodiment, each of the sites in the network maintains a site-specific activity tracking (SATr) cookie which comprises a set of SATr parameters for each registered user.
In the second preferred embodiment, only the NATr cookies are used, and the SATr cookies are not used at all.
In the third preferred embodiment, neither SATr cookies nor Javascript are used.
A typical communications network according to this invention includes a plurality of affiliated sites or service providers, a plurality of clients, and at least one network authentication server (NAS), all coupled to the Internet. NAS maintains a network-wide activity tracking (NATr) cookie which comprises a set of network-wide activity tracking (NATr) parameters for each registered user.
In the first preferred embodiment, each of the affiliated sites maintains a site-specific activity tracking (SATr) cookie which comprises a set of site-specific activity tracking (SATr) parameters for each registered user.
Referring to
The NATr tracking element is included via a Javascript (JS) code snippet that itself is included via a <SCRIPT LANGUAGE=“Javascript” SRC=“ . . . ” >tag. For a given user on a given site S, the JS snippet writes an IMG tag (with tracking element URL as described below) into an S page only once every n minutes. The JS code snippet accomplishes this by looking for the existence of a local cookie, say NAT_WAIT. If NAT_WAIT is not present, then writes the IMG tag with tracking element URL into page, and writes a NAT_WAIT cookie with expiration time n minutes in the future. Otherwise, if the local cookie NAT_WAIT cookie is present, then does not insert tracking element (just waits for the cookie to expire).
The URL of the tracking element is a specified NAS URL, for example, an actTrackUrl, which takes the following query arguments:
The actions performed by the NAS tracking URL include (1) updating the tracking parameters in the NATr cookie as illustrated in
Note that S sometimes, but not always, inserts the NATr element in the requested page.
The following sample code further illustrates the above steps:
The method described above has the following properties: (1) constrains clock skew issues/management to within specific site server farms (i.e., NAS timestamps are compared to NAS timestamps, site S1 timestamps to site S1 timestamps, etc.); (2) centralizes overall activity tracking at the network authentication servers (NAS); (3) allows the tradeoff between tracking granularity and scalability to be adjusted via configuration parameters; and (4) delegates site-specific activity tracking and detecting/handling excessive inactivity to sites.
In the second preferred embodiment, the SATr cookies are not used at all. In place of the snippet of Javascript that uses the NAT_WAIT that causes the NAS tracking image to be periodically inserted into the site's pages, sites instead includes in their pages an HTML SCRIPT tag that causes the browser to request a Javascript activity-tracking source file from the Web server.
Note that Step 8f may include the same exemplary sub-steps as illustrated in
In the third preferred embodiment, neither SATr cookies nor Javascript are used.
Note that Step 9d may include the same exemplary sub-steps as illustrated in
Abbreviations and Definitions:
Although the invention is described herein with reference to the preferred embodiment, one skilled in the art will readily appreciate that other applications may be substituted for those set forth herein without departing from the spirit and scope of the present invention.
Accordingly, the invention should only be limited by the Claims included below.
Number | Name | Date | Kind |
---|---|---|---|
5966705 | Koneru et al. | Oct 1999 | A |
5974549 | Golan | Oct 1999 | A |
6035332 | Ingrassia, Jr. et al. | Mar 2000 | A |
6052730 | Felciano et al. | Apr 2000 | A |
6073241 | Rosenberg et al. | Jun 2000 | A |
6115742 | Franklin et al. | Sep 2000 | A |
6138157 | Welter et al. | Oct 2000 | A |
6148333 | Guedalia et al. | Nov 2000 | A |
6256739 | Skopp et al. | Jul 2001 | B1 |
6281790 | Kimmel et al. | Aug 2001 | B1 |
6286046 | Bryant | Sep 2001 | B1 |
6313855 | Shuping et al. | Nov 2001 | B1 |
6330566 | Durham | Dec 2001 | B1 |
6341310 | Leshem et al. | Jan 2002 | B1 |
6366298 | Haitsuka et al. | Apr 2002 | B1 |
6393479 | Glommen et al. | May 2002 | B1 |
6405252 | Gupta et al. | Jun 2002 | B1 |
6446119 | Olah et al. | Sep 2002 | B1 |
6516416 | Gregg et al. | Feb 2003 | B2 |
6678731 | Howard et al. | Jan 2004 | B1 |
6718328 | Norris | Apr 2004 | B1 |
6859834 | Arora et al. | Feb 2005 | B1 |
6877095 | Allen | Apr 2005 | B1 |
20020028706 | Barnard et al. | Mar 2002 | A1 |
20020029269 | McCarty et al. | Mar 2002 | A1 |
20020095222 | Lignoul | Jul 2002 | A1 |
20020133697 | Royer et al. | Sep 2002 | A1 |
20020146129 | Kaplan | Oct 2002 | A1 |
20020178186 | Parry | Nov 2002 | A1 |
Number | Date | Country |
---|---|---|
1 041 768 | Oct 2000 | EP |
2002-7261 | Jan 2000 | JP |
WO 0036812 | Jun 2000 | WO |
Number | Date | Country | |
---|---|---|---|
20040073660 A1 | Apr 2004 | US |