US 7,305,470 B2Grant
Method for displaying web user's authentication status in a distributed single login network
Issue Date:2007-12-04
•16 Claims
•7 Drawing Sheets
Abstract
The invention provides a system and method for automatically displaying a user's logged-in status across an Internet based network of affiliated Web sites via a visual indicator such as a toolbar to help the user to be certain about his logged-in status when he stays with one or switches from one to another affiliated Web site.
Metadata
Assignee
- AOL LLC
Inventors
- Allen Lee Tom
- Mohan Kumar S. Bethur
- Hyun Jong Shin
- Jun-Shong Huang
Application Information
Application Number:US 10/365,979
Filing Date:2003-02-12
Priority Date:2003-02-12
Art Unit:2145
Classifications
IPC:
G06F15/16G06F7/04G06F3/00H04K1/00H04L9/32G06F15/173G06F17/30G06F3/048H04L9/00G06Q99/00
Patent Drawings (7 sheets)
Description
Background of the Invention
[0001] 1. Technical Field
[0002] This invention relates generally to cross domain authentication technology. More particularly, the invention relates to a method and system for automatically displaying a Web user's authentication status across an Internet based network of participating Web sites.
[0003] 2. Description of the Prior Art
[0004] To request a service or conduct other electronic transactions in an Internet based network, a user is usually required to go through an authentication process. In other words, the user is required to provide the seller or service provider with some credential 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 the consumers' 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-login 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.
[0005] 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 affiliated 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 of the network. 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 in 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 entered is registered with “.NET Passport”, and (2) the password he entered is correct. “.NET Passport” then notifies the site that the user has provided valid “sign-in credentials,”and thus 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 any other site simply by clicking the “.NET Passport” sign-in button available at the site.
[0006] Another example is America Online Incorporated (AOL)'s “Screen Name Service” system, which provides a free service allowing anyone with a “Screen Name” to register easily and securely at a variety of Web sites. 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 credentials 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.
[0007] In these distributed single login networks, cross domain status toolbars or indicators are static and do not display a personalized greeting across multiple domains. For example, when the user with a screen name “ljewpt9” logs in the MSN e-mail service, his full e-mail address [email protected] is displayed in the upper-left corner of every mail service pages such as the “inbox,” “sent,” “trash,” etc. When the user switches to other pages hosted by MSN, such as “search,” “music,” “sports,” neither the user's e-mail address, nor his screen name, nor his first name or last name associated with his account is displayed. There is only a small bar “sign Out.net” embedding in the pages. Without a close look, the user is not certain whether he is still logged-in or who is currently logged-in on the page. Similarly, when the user switches from an MSN page to any other affiliated website with “.NET Passport”, the user's logged-in status or personalized greeting is not expressly displayed in the targeted pages.
[0008] Websites, such as yahoo.com and amazon.com, display personalized greetings on their sites, but only on pages under the same domain from which they originally authenticated. For example, a user, with a screen name “ljewpt9”, who is authenticated to yahoo.com can only be identified on Web pages hosted on yahoo.com. When the user logs in the yahoo e-mail service, his full e-mail address [email protected] is displayed in the upper-right corner of every mail service pages such as the pages for “inbox”, “draft”, “sent”, “trash”, and “bulk”, etc. When the user switches to “Yahoo! Travel” or “Weather”, a greeting like “Welcome, Ljewpt9” is displayed on the page. However, the user's login status cannot be displayed on any other Web pages which are not hosted by yahoo.com.
[0009] What is desired is a mechanism to automatically display a user's logged-in status across an Internet based network of affiliated Web sites so that the user is certain about his logged-in status when he stays with one or switches from one to another affiliated Web site.
Summary of the Invention
[0010] The invention provides a system and method for automatically displaying a user's logged-in status across an Internet based network of affiliated Web sites via a visual indicator such as a toolbar to help the user to be certain about his logged-in status when he stays with one or switches from one to another affiliated Web site. The visual indicator has two modes: logged-in and logged-out. In the logged-in mode, the indicator displays the user's login name, such as a screen name or a personalized greeting, and a virtual button, by clicking which the user signs out. In the logged-out mode, the indicator displays a virtual button for signing in. When the user has signed in one participating site of the network, the user is automatically recognized at all other sites which use the visual indicator.
[0011] The visual indicator is hosted on a single Web site. Once the user has been authenticated to the indicator Web site, the user is recognized at all affiliated Web sites that embed the indicator. A Web site embeds the indicator by instructing the user's Web browser to load additional JavaScript from the indicator Web site. The additional JavaScript writes the indicator HTML onto the Web page that the user visits.
[0012] The invention allows a participating Web site to recognize a user who has never visited the site before and customize its content based on the user. The invention can also be used to track users across multiple Web sites to determine their interests and to display customized content and promotions targeted to the user.
Brief Description of the Drawings
[0013] FIG. 1 is a schematic block diagram illustrating a distributed, single login network according to the invention;
[0014] FIG. 2 is a schematic flow diagram illustrating a method for automatically displaying a Web user's authentication status in a distributed single login network according to the invention;
[0015] FIG. 3 a is an exemplary page where an authentication status indicator is in its logged-out mode;
[0016] FIG. 3 b is a schematic diagram showing a typical graphical arrangement of the status indicator in logged-out mode;
[0017] FIG. 4 is an exemplary “sign in” page where the user enters his login name and his password for authentication;
[0018] FIG. 5 a is an exemplary page where the status indicator is in logged-in mode showing the user is validly logged in;
[0019] FIG. 5 b is a schematic diagram showing a typical graphical arrangement of the status indicator in its logged-in mode;
[0020] FIG. 6 a is an exemplary page of a participating site where the user's logged-in status is automatically displayed in the status indicator when the user switches to this site;
[0021] FIG. 6 b is an exemplary schematic diagram of the status indicator in logged-in mode with a slightly different appearance; and
[0022] FIG. 7 is a flow diagram illustrating a method for automatically displaying a Web user's authentication status in a distributed single login network using an authentication status cookie according to the invention.
Detailed Description of the Invention
[0023] FIG. 1 is schematic block diagram illustrating a distributed, single login network 100 which comprises at least one client 101 with a Web browser 102, an authentication status indication server (ASIS) 104, a plurality of participating websites such as NETSCAPE.COM 105 and CNN.COM 106, communicatively coupled to the Internet 103. The ASIS 104 centrally hosts the authentication status indicator in all affiliated sites. The authentication status indicator, which displays the user's authentication status information, may be incorporated in a dashboard or a toolbar or any other visual cue on the Web pages. The status information may include the user's login name, such as his screen name or his e-mail address or even his full name, and/or a short welcome message or other information. The content of the visual indicator,i.e. the user's status information is centrally served, managed, and tracked.
[0024] The participating sites embedding the status indicator do not need to run any additional software or Web server plug-ins to display the indicator. However, they must include a few lines of HTML and a small piece of JavaScript code, called bootstrapping code, in their page headers. The function of the bootstrapping code is to instruct the user's Web browser 102 to load additional JavaScript 107 from the ASIS 104 to render each participating website's status indicator in logged-in mode or logged-out mode.
[0025] All content updates are managed from one single site, i.e. the ASIS 104. The participating sites which deploy the bootstrapping code automatically get future revisions on the dashboard without any additional work.
[0026] An exemplary of the bootstrapping code is given below:
[0027]
| <table border=“O” cellpadding=“O” cellspacing=“O” width=“WWW”> |
| <tr><td> |
| <script Language=“Javascript” SRC= “http://tool |
| bar.aol.com/dashboard.twhat?dom=XXX”> |
| </script> |
| </td></tr> |
| </table> |
[0028] Here, WWW should be the desired width in pixels of the Dashboard and XXX should be the site's three digit partner code.
[0029] The user's authentication status information is stored in an authentication status cookie 108 which is sent to the ASIS 104 when the user is logged into the network 100. The ASIS 104 checks the validity of the received cookie and returns JavaScript 107 to render the toolbar in logged-in mode if the cookie is valid, or logged-out mode if the cookie is missing or invalid.
[0030] Because the authentication status cookie 108 is stored on one central server (ASIS 104), the cookie 108 can be shared across multiple participating sites if each site embeds the bootstrapping code on their Web pages. The cookie is bound to the ASIS 104, not to the top level domains such as .NETSCAPE.COM or .AOL.COM. Since the cookie 108 should only be read by the ASIS 104, it should be acceptable to keep the cookie in clear text. This eliminates the computational overhead of decrypting the cookie for each page view. Alternatively, the ASIS 104 may use other authentication methods without using a local status cookie.
[0031] To prevent unauthorized sites from reading the user's sensitive personal data, the ASIS 104 never returns the user's screen name in the indicator JavaScript or in text form. Instead, an image containing the screen name is used and the browser 102 is instructed to display the image. This mechanism prevents unauthorized sites from reading or extracting the screen name or other personal information from users who visit them.
[0032] Alternatively, each website could maintain their own authentication scheme, using cookies or some other method. A website would have no way of determining if the user has logged into any other participating website. A system could be devised where a participating website would redirect the user's browser to a third party site which would then somehow pass the authentication credentials back to the originating site, if the user is logged in. However, the originating site would have to redirect all users to this third party site, without knowing ahead of time if the user is logged in. Redirecting the user to another site to check the authentication status is very complicated (special software and protocols must be installed and agreed upon between the originating site and the third party site) and also adds a great deal of time needed to display the content on the originating site.
[0033] Note that the authentication status indication server (ASIS) 104 is built on top of a single login service (cross sites authentication) such as AOL's Screen Name Service (SNS). Without ASIS 104, the participating sites of the single login service such as SNS would not be able to automatically recognize users who are signed into a different domain via SNS. To recognize a user who is already signed into a first site via SNS, a second site would require the user to click on a login button. There was no way to recognize the user automatically without the user's intervention. However, this invention allows users to be recognized and authenticated across multiple domains. Once a user has been authenticated to one participating site that embeds the status indicator, the toolbar for example, the user is recognized at all other participating sites that embed the indicator.
[0034] FIG. 2 is a schematic flow diagram illustrating a method for automatically displaying a Web user's authentication status in a distributed single login network according to the invention. The method comprises the steps of:
[0035] Step 201: Displaying the user's logged-in status on the page of a participating website from which the user logged in the network 100; and
[0036] Step 202: When the user switches from one participating website to another participating website with a different domain, automatically displaying the user's logged-in status in said another participating website without requiring any browser redirects or any additional Web application. No client software such as browser plug-in or special client application is required to be installed on the user's computer, nor is any special Web application or server software required to be installed on the participating site's servers.
[0037] FIG. 3 a is an exemplary page of NETSCAPE.COM where an authentication status toolbar 301 is in its logged-out mode. The toolbar may be in any color or any shape, and may be placed anywhere in the page.
[0038] FIG. 3 b illustrates a typical graphical arrangement of the toolbar 301 in logged-out mode. By clicking the “Join” button 302, a user is prompted to a registration page for joining as a member. Similarly, by clicking the “Sign in” button 303, the user will be prompted to a “sign in” page for authentication.
[0039] FIG. 4 is an exemplary “sign in” page 401 of NETSCAPE.COM where the user enters his screen name “Ljewpt9” and his password “★★★★” for authentication.
[0040] FIG. 5 a is an exemplary page of NETSCAPE.COM where the authentication status toolbar is in logged-in mode 501. The toolbar may be in any color or any shape, and may be placed anywhere in the page.
[0041] FIG. 5 b illustrates a typical graphical arrangement of the status toolbar in its logged-in mode 501 which comprises the user's screen name, a “My Account” button 502, which links to an account information page, and a “Sign out” button 502, by clicking which the user signs out.
[0042] FIG. 6 a is a sample page of CNN.COM, a participating site where the user now visits. The user's logged-in status is automatically displayed in the status toolbar which is also in logged-in mode 601.
[0043] FIG. 6 b illustrates the status toolbar in its logged-in mode 601 which is slightly different in size and font from the status toolbar as illustrated in FIG. 5 b. The status toolbar in logged-in mode comprises the user's screen name, a “My Account” button 602, which links to an account information page, and a “sign out” button 602, by clicking which the user signs out.
[0044] Note that once the user logs in any participating site, the logged-in status is recognized at any other participating site simultaneously without need to redirect the user's logged-in status from a central server back to the user's Web browser.
[0045] FIG. 7 is a flow diagram illustrating a method for automatically displaying a Web user's authentication status in a distributed single login network using a status cookie according to the invention. The method comprises the steps of:
[0046] Step 701: Whenever the user logs in the network 100, the authentication status indication server (ASIS) 104 returns JavaScript to have the user's Web browser load the status toolbar in logged-in mode and at the same time creates a cookie 108 storing the user's logged-in status and sends the status cookie to the user's Web browser 102;
[0047] Step 702: Whenever the user switches from one participating website to any other participating website in a different domain, the user's Web browser 102 sends the cookie 108 to the ASIS 104;
[0048] Step 703: The ASIS 104 compares the received cookie with the stored cookie 108;
[0049] Step 704: If the received cookie is identical with the stored cookie 108, the ASIS 104 returns JavaScript 107 to render said any other participating website's toolbar in logged-in mode (see FIG. 6 a and FIG. 6 b, 601); and
[0050] Step 705: If no cookie is received or the received cookie is not identical with the stored cookie 108, the ASIS 104 returns JavaScript 107 to render said any other participating website's toolbar in logged-out mode.
[0051] The method described above allows a participating Web site to recognize a user who has never visited the site before and customize its content based on the user. It also allows the users to personalize their Uls and look and feel of multiple Web sites. In addition, the method can also be used to track users across multiple Web sites to determine their interests and to display customized content and promotions targeted to the user.
[0052] 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.
[0053] Accordingly, the invention should only be limited by the Claims included below.
Claims
The invention claimed is:
1. A method for automatically displaying a Web user's authentication status in a distributed single login network, comprising the steps of:
displaying said user's logged-in status on a first visual indicator in a participating website from which said user has logged in said network; and
when said user switches from any participating website to any other participating website in a different domain, automatically displaying said user's logged-in status on another visual indicator in said any other participating website without requiring any browser redirects or any additional pre-installed application;
wherein a visual indicator comprises an image which contains said user's Personal identification information, wherein any of said participating websites cannot extract the content of said image.
2. The method of claim 1, wherein said first visual indicator and said another visual indicator are substantially same.
3. The method of claim 1, wherein any of said visual indicators has only two states:
logged-in; and
logged-out.
4. A method for automatically displaying a Web user's authentication status in a distributed single login network, comprising the steps of:
displaying said user's logged-in status on a first toolbar in a participating website from which said user has logged in said network; and
whenever said user switches from any participating website to any other participating website in a different domain, automatically displaying said user's logged-in status on another toolbar in said any other participating website without requiring any browser redirects or any additional pre-installed application;
wherein each participating website of said network embeds a small piece of JavaScript bootstrapping code which instructs said user's Web browser to load additional JavaScript from a central server of said network to render said each participating website's toolbar in logged-in state or logged-out state.
5. The method of claim 4, wherein whenever said user logs in said network, said central server creates a status cookie storing said user's logged-in status and sends said status cookie to said user's Web browser;
wherein whenever said user switches from said any participating website to said any other participating website in a different domain, said user's Web browser sends said status cookie to said central server; and
wherein said central server returns JavaScript to render said any other participating website's toolbar in logged-in state if the cookie received is identical with said status cookie, or in logged-out state if no cookie is received or the cookie received is not identical with said status cookie.
6. The method of claim 4, wherein said first toolbar and said another toolbar are substantially same.
7. In a distributed single login network which comprises at least one client, a plurality of participating websites and a central status indication server supporting a visual indicator embedded in each participating website, a method for automatically displaying a Web user's authentication status, comprising steps of:
said status indication server creating a status cookie storing said user's authentication status information when said user logs in said network;
sending said status cookie to said user's Web browser;
said user's Web browser storing said status cookie loading said visual indicator in logged-in state;
when said user switches to any other participating website, said user's Web browser sending said status cookie to said status indication server;
said status indication server checking whether said status cookie is received and whether the received cookie is valid;
if a valid status cookie is received, returning a first code to said user's Web browser, said first code rendering said visual indicator in said any other participating website in logged-in state; and
if said status cookie is missing or if the received cookie is invalid, returning a second code to said user's Web browser, said second code rendering said visual indicator in said any other participating website in logged-out state;
wherein each participating website embeds a third code which instructs said user's Web browser to load said first code or said second code from said status indication server.
8. The method of claim 7, wherein said steps are performed in said order recited.
9. The method of claim 7, wherein any of said codes is JavaScript.
10. The method of claim 7, wherein said first code instructs said user's Web browser to load an image which contains said user's personal identification information, wherein any of said participating websites cannot extract the content of said image.
11. The method of claim 7, wherein said visual indicator has only two states:
logged-in; and
logged-out.
12. The method of claim 7, wherein said visual indicator may vary in appearance in different participating sites.
13. A distributed single login network comprising:
a plurality of participating websites with different domain names,
a central status indication server which supports a visual indicator in each of said participating websites, the central server hosting the process that displays visual indicators of the user's status from site to site; and
at least one client from which a user logs in said network;
wherein each of said participating websites embeds a first JavaScript which instructs said user's Web browser to load from said status indication server a second JavaScript for rendering said visual indicator in logged-in state or a third JavaScript for rendering said visual indicator in logged-out state.
14. The network of claim 13, wherein when said user logs in said network, said status indication server creates a status cookie which stores said user's authentication status information and sends said status cookie to said user's Web browser;
wherein whenever said user switches from one to another of said participating websites, said user's Web browser sends said status cookie to said status indication server;
wherein if the cookie received is identical with said status cookie, said status indication server returns to said user's Web browser said second JavaScript for rendering said visual indicator in logged-in state; and
wherein if the cookie received is not identical with said status cookie, said status indication server returns to said user's Web browser said third JavaScript for rendering said visual indicator in logged-out state.
15. The network of claim 13, wherein when said visual indicator is in logged-in state, said visual indicator displays:
said user's login name or real name; and
a first virtual button, by clicking which said user logs out said network.
16. The network of claim 13, wherein when said visual indicator is in logged-out state, said visual indicator displays:
a second virtual button, by clicking which said users is prompted to a login page; and
a third virtual button, by clicking which said user is prompt to a registration page.
Patent Citations (51)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5778377(A) | 1998-07-01 | Marlin et al. | Applicant |
| US5963925(A) | 1999-10-01 | Kolling et al. | Applicant |
| US5970477(A) | 1999-10-01 | Roden | Applicant |
| US5974572(A) | 1999-10-01 | Weinberg et al. | Applicant |
| US5978648(A) | 1999-11-01 | George et al. | Applicant |
| US5987611(A) | 1999-11-01 | Freund | Applicant |
| US5999179(A) | 1999-12-01 | Kekic et al. | Applicant |
| US6073119(A) | 2000-06-01 | Bornemisza-Wahr et al. | Applicant |
| US6112190(A) | 2000-08-01 | Fletcher et al. | Applicant |
| US6115040(A) | 2000-09-01 | Bladow et al. | Applicant |
| US6192405(B1) | 2001-02-01 | Bunnell | Applicant |
| US6272537(B1) | 2001-08-01 | Kekic et al. | Applicant |
| US6341316(B1) | 2002-01-01 | Kloba et al. | Applicant |
| US6385494(B1) | 2002-05-01 | Blahnik et al. | Applicant |
| US6385595(B1) | 2002-05-01 | Kolling et al. | Applicant |
| US6385655(B1) | 2002-05-01 | Smith et al. | Applicant |
| US6397378(B1) | 2002-05-01 | Grey et al. | Applicant |
| US6401220(B1) | 2002-06-01 | Grey et al. | Applicant |
| US6421717(B1) | 2002-07-01 | Kloba et al. | Applicant |
| US6434607(B1) | 2002-08-01 | Haverstock et al. | Applicant |
| US6442590(B1) | 2002-08-01 | Inala et al. | Applicant |
| US6460058(B2) | 2002-10-01 | Koppolu et al. | Applicant |
| US6668322(B1) | 2003-12-01 | Wood et al. | Examiner |
| US6701438(B1) | 2004-03-01 | Prabandham et al. | Examiner |
| US6763468(B2) | 2004-07-01 | Gupta et al. | Examiner |
| US6826696(B1) | 2004-11-01 | Chawla et al. | Examiner |
| US6859878(B1) | 2005-02-01 | Kerr et al. | Examiner |
| US6892307(B1) | 2005-05-01 | Wood et al. | Examiner |
| US6941376(B2) | 2005-09-01 | Mitchell et al. | Examiner |
| US6970904(B1) | 2005-11-01 | Rode | Examiner |
| US7010582(B1) | 2006-03-01 | Cheng et al. | Examiner |
| US7016875(B1) | 2006-03-01 | Steele et al. | Examiner |
| US7032241(B1) | 2006-04-01 | Venkatachary et al. | Examiner |
| US7069293(B2) | 2006-06-01 | Cox et al. | Examiner |
| US7093020(B1) | 2006-08-01 | McCarty et al. | Examiner |
| US7150038(B1) | 2006-12-01 | Samar | Examiner |
| US7188360(B2) | 2007-03-01 | Gerdes et al. | Examiner |
| US7191467(B1) | 2007-03-01 | Dujari et al. | Examiner |
| US7225464(B2) | 2007-05-01 | Satyavolu et al. | Examiner |
| US2003/0014519(A1) | 2003-01-01 | Bowers et al. | Examiner |
| US2003/0140120(A1) | 2003-07-01 | Hartman | Examiner |
| US2004/0158746(A1) | 2004-08-01 | Hu et al. | Examiner |
| US2005/0022006(A1) | 2005-01-01 | Bass et al. | Examiner |
| US2005/0144452(A1) | 2005-06-01 | Lynch et al. | Examiner |
| US2006/0107217(A1) | 2006-05-01 | Lu et al. | Examiner |
| EP774725 | 1997-05-01 | Applicant | |
| EP907120 | 1999-04-01 | Applicant | |
| EP1168203 | 2002-01-01 | Applicant | |
| EP1168204 | 2002-01-01 | Applicant | |
| EP1168765 | 2002-01-01 | Applicant | |
| EP1227635 | 2002-07-01 | Applicant |
Non-Patent Literature (16)
- Netegrity Siteminder: Ask The Experts—SearchCIO.com—Ebusiness Security Experts(s): Puneet Mehta, Dec. 4, 2001.Applicant
- 5.8: Single Sign-On: Single Sign-On: WebSphere Application Server—InfoCenter Home>5: Securing applications—special topics > 5.8: Single Sign-On, Feb 10, 2003.Applicant
- Universal Wed Agent Datasheet: Home>Products>Authentication and Access Control>SafeWord™ PremierAccess™>Applications Protected by PremierAccess>Universal Web Agent, Feb. 2002.Applicant
- Not Another ID and Password: A Look at Single Sign-On: M. Bonham II, Feb 10, 2003.Applicant
- Challenge 2: Cross Domain Authentication (Web SSO); OneName Corporation; Home>Products & Solutions>7 digital Identity Challenges>Challenge 2, Feb. 10, 2003.Applicant
- Securant Debuts Single Sign-On Across Multiple Sites: G. Hulme; InformationWeek Online; May 2000.Applicant
- Extended SSO; Integrating Siebel 2000 (6.X) and Siebel 7 Into Your SSO Environment —p. 4; Netegrity Portal Security Software, Feb. 10, 2003.Applicant
- Numerical Relativity in a Distributed Environment; W. Benger I. Foster J. Novotny, E. Seidel, J. Shalf, W. Smith, P. Walker, Apr. 1999.Applicant
- Issues in the Security Architecture of the Computerized Patient Record Enterprise; K. Beznosov; Apr. 1998.Applicant
- Entrust TruePass™; Entrust: Entrust TruePass—Frequently Asked Questions, Feb. 10, 2003.Applicant
- Securing Access to BEA WebLogic® Applications Using SafeWord™ PremierAccess™; Home>Products Authentication and Access Control>SafeWord™ PremierAccess™>Applications Protected by PremierAccess>Application interoperability papers>BEA WebLogic® Feb. 10. 2003.Applicant
- Providing Multi-Layer Security Support for Wireless Communications Across Multiple Trusted Domains; J. Kong, M. Gerla, B.S. Prabhu, R. Gadh; UCLA Computer Science Department Technical Report 020032, Sep. 2002.Applicant
- Authentication in Distributed Systems: Theory and Practice; B. Lampson, M. Abadi, M. Burrows, E. Wobber; Digital Equipment Corporation, Nov. 1992.Applicant
- Preserving State on the World Wide Web Using Dynamic Argument Embedding; A. Iyengar, IBM Research Division; T.J. Watson Research Center, Mar.-Apr. 1997.Applicant
- Using Netscape Directory Server to Manage NT Domains; G. Yost; NT Insights, 1999.Applicant
- Role-Based Security for Distributed Object Systems; N. Yialelis, E. Lupu, M. Sloman; Department of Computing, Imperial College, Jun. 19-21, 1996.Applicant