Browse Prior Art Database

Password management using authentication ID (AID) Disclosure Number: IPCOM000183801D
Original Publication Date: 2009-Jun-01
Included in the Prior Art Database: 2009-Jun-01
Document File: 1 page(s) / 22K

Publishing Venue



This article talks about a method by which a web browser can learn that a single backend server is authenticating access to multiple URLs and provide a method to the user to access those pages with ease.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 74% of the total text.

Page 1 of 1

Password management using authentication ID (AID)

Internet browsers can remember passwords of the user. Browsers may have a master password to protect the passwords and generally
associate login-id/password with the URL of the authentication web page.

If the user happened to have a different web page authenticating with the same back-end server, then the user will need to type the password for each such different page once. Typical example is an IBM* intranet password that is used by multiple services. This requires the user to remember and type intranet password for each such service because the password manager of the browser doesn't know that they all share the same user name and

If the browser knew that the backend authentication server is the same, then the user do not have to type in for each of the front end application.

The login page should have an ID that is readable by the browser. All the webpages that use same authentication method/server should present the same
authentication ID (AID). This AID can be used by the browser to understand that all login pages that have the same AID share the same user name and password.

The browser reads the authentication AID presented in the login page and uses it to map passwords. Essentially it stores "AID, username/password" instead of "URL, username/password". In effect all the web pages that use the same authentication server will have same AID in...