WO2008031219A1 - Gestionnaire d'identités pour internet - Google Patents

Gestionnaire d'identités pour internet Download PDF

Info

Publication number
WO2008031219A1
WO2008031219A1 PCT/CA2007/001623 CA2007001623W WO2008031219A1 WO 2008031219 A1 WO2008031219 A1 WO 2008031219A1 CA 2007001623 W CA2007001623 W CA 2007001623W WO 2008031219 A1 WO2008031219 A1 WO 2008031219A1
Authority
WO
WIPO (PCT)
Prior art keywords
identity
user
agent
mapping
information
Prior art date
Application number
PCT/CA2007/001623
Other languages
English (en)
Inventor
Dick C. Hardt
Keith W. Grennan
Original Assignee
Sxip Identity Corp.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sxip Identity Corp. filed Critical Sxip Identity Corp.
Publication of WO2008031219A1 publication Critical patent/WO2008031219A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/41—User authentication where a single sign-on provides access to a plurality of computers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting
    • G06F40/174—Form filling; Merging
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2119—Authenticating web pages, e.g. with suspicious links

Definitions

  • This invention relates generally to identity managers for use in online environments.
  • a user is often required to provide identity information to subscribe or register for a service.
  • the information required by one site may be different from the information required by another site.
  • the information that a user wishes to provide to a first site may differ from the information the user wants to release to the second site.
  • form-filling applications have been developed. These applications allow a user to click a button to fill in a form.
  • a form is usually generated using HTML.
  • Each field in the form is provided a unique identifier in the HTML.
  • the form filling application either guesses the content that should go into the form fields based on the field identifier embedded in the HTML, or determines the content for each field based on a known mapping of the form. Where mappings for forms exist and are used, they are centrally stored and are designed by the providers of the form filling applications.
  • mapping based - filling applications are limited in how quickly a form mapping can be provided by the ability of the developers of the tool to find forms and generate mappings for them. Best- guess based form-filling applications provide immediate access to a form, but the mapping is often incorrect or incomplete. When a form is designed using field identifiers that are obscure or have names that are not logically linked to the requested content, guess-based form filling provides an unsatisfactory mapping.
  • a user may wish to provide one set of information to a site dedicated to online gaming, while wanting to provide a second set of information to online merchants, and a third set of information to another group of sites.
  • the different information sets may include different addresses, email addresses, and phone numbers. Each of these sets of information defines a persona, and an individual often presents differing personas at different times
  • an identity agent for use in electronic communications.
  • the identity agent comprises a browser interface, an identity store interface, a mapping table interface and an analysis engine.
  • the browser interface is used for communication with a web browser.
  • the identity store interface is used for access to an identity store containing user identity information.
  • the mapping table interface is for communicating to at least one of a plurality of mapping tables.
  • the mapping table interface is used to request mappings from a mapping table for any form received by the browser, and to transmit to a mapping table any mapping generated by the identity agent that associates a field in a form to an element of an identity schema.
  • the analysis engine is used to determine if a page received by the browser contains a form, to request mappings from the mapping table for any form received by the browser, for filling in forms with user identity information that is determined in accordance with received mappings, and for generating mappings for forms not in the mapping table.
  • one of the plurality of mapping tables can be stored locally.
  • the analysis engine can include a mapping generator.
  • the mapping generator can generate mappings between the fields of an obtained form and elements of the identity schema.
  • the mapping can be based on an analysis of the information input by a user into form fields.
  • the mapping can also be based on the obtained form and a name associated a field in the form.
  • the identity information can be organized as a series of personas, each persona having a unique set of identity information.
  • the analysis engine can include a persona selector to allow the user to select one of the series of personas and provide the information associated with the selected persona to the form.
  • the persona selector can include an identity management system persona selector for accessing identity information associated with a identity management system, and for presenting the accessed identity information to the user as a persona within the identity agent.
  • the identity management system can be any of a number of systems including OpenID and InfoCard.
  • the analysis engine can include a user interface engine for indicating recognition of a form to the user through the browser.
  • the user interface can include a translucent overlay over the form indicating the availability of a form mapping.
  • the color of the overlay can be varied in accordance with the form mapping, so that, for example, a form that has been flagged as a potential phishing attempt can have a red overlay to alert the user.
  • the translucent overlay can provide a quick pick list of personas, and can provide one-click functionality for small forms, with the possible entries provided in a list superimposed on the form field.
  • the analysis engine includes a password generation engine for generating a site-specific password for filling in password requests on forms.
  • the password generation engine ca n include means to obtain a password from a user, associate the password obtained from the user with a password hint and provide the user the ability to select the password obtained from the user by displaying the associated password hint.
  • the generated passwords can be stored by the password generation engine along with login information associated with the generated password.
  • the mapping table can include a reputation based engine for evaluating maps received by the analysis engine.
  • the analysis engine can also include means for displaying reputation information associated with a user who submitted a received mapping.
  • the identity agent can include a pseudonymous identity information generator interface. This interface alls the identity agent to receive pseudonymous identity information from a pseudonymous identity information generator and allows for the association of the received pseudonymous identity information with stored identity information.
  • the pseudonymous identity information can be selected from a list including a pseudonymous email address, a pseudonymous credit card number, a pseudonymous postal address and a pseudonymous telephone number.
  • the pseudonymous identity information can also be uniquely associated to the form.
  • the identity information stored in the identity store is obtained from a source selected from a list including a form completed by the user, electronic address books, data submitted to already mapped forms, and a browser auto-fill history.
  • the obtained mapping can be a generic map that is not specific to the page received by the browser. In such a case, the generic map, or template, is applicable to a plurality of different pages.
  • Figure 1 is a block diagram illustrating the interaction of the present invention with Internet elements; and Figure 2 is a block diagram illustrating an embodiment of the present invention as functional elements.
  • the present invention is directed to identity agents for use in online environments such as the Internet.
  • a user may have a work persona based around an office email address, and office address and an office phone number in addition to an at-home persona using a personal email address, a residential mail address and a phone number.
  • the user's biographic information (such as name, gender, date of birth, etc.) can be consistent across personas.
  • a preferred alias can be stored in each profile so that a user can create accounts at different sites with different aliases as usernames depending on the persona used to create the account.
  • the present invention allows a user to fill-in forms with information based on the preferred set of identity information that the user wishes to release.
  • a number of sources can be consulted.
  • Many web browsers have an auto-fill history that is used to fill in already stored information. This history can be used to gather user identity information, as can information that the user provides to already mapped forms. Entries in an electronic address book identified by the user can form another source of data, as could a virtual business card, such as a vCard. Users can also be prompted to populate the schema using a form during the setup of an identity agent.
  • An identity agent stores user identity information and manages the release of the information.
  • the release of the information is preferably done upon receipt of user approval for the release.
  • the identity information associated with the selected information can be provided to the user for approval, and then provided to the requesting form.
  • the identity agent obtains a mapping between the requested information and elements in a schema.
  • the schema defines the structure used to store an overall listing of the information known about the user.
  • Each schema element such as name, postal or zip code, phone number and email address can be differentiated from each other by the element type.
  • a personal can be created as a grouping of schema elements. Thus two different phone numbers can be associated with the same name in two different personas.
  • Forms are typically presented to a user on the Internet using HTML.
  • An HTML based form makes use of a defined form field.
  • the form field is associated with an identifier, which is unique on a per- form basis. This allows the form data to be submitted to the requesting site in a non-ambiguous manner.
  • the form field can have one of a number of types.
  • the field can be a free-form text entry field, it can be a drop down menu, or it can be a selection based menu.
  • the field identifiers are not standardized, and are left to the determination of the designer.
  • a form may request a first name in a given form and identify the field as 'fname', while a second form may identify the same field as 'firstname', and a third form may identify the field as '001'. From this example, one can readily see why best-guess techniques cannot be relied upon to determine a mapping.
  • the identity agent examines a mapping.
  • the mapping indicates a relationship between a form field and an element in the identity schema.
  • the mapping can be stored locally (either independently or as a local cache), embedded in the form itself, or on a central server. For the purposes of the following discussion, the central server scenario will be discussed.
  • the identity agent requests a mapping from a central server using a data connection.
  • the identity agent provides the user with the ability to select personas. Mappings can either be associated to a specific form, or they can be template based for use on common forms, such as blog comment fields.
  • mappings can undergo a validation process to determine their accuracy before they are presented to other users. As a user creates more a more mappings, a reputation can be established.
  • mappings of users with excellent reputations can be provided a simpler validation process than the one used for mappings generated by users without reputation information. Distributing the creation of maps, and building a cooperative community allows for the creation of large numbers of mappings in a short period of time. The users community can also be provided the ability to edit existing mappings if an error is detected. Detected errors can adversely change a user's reputation. The reputation of users can be used as a gauge of whether or not an edit to a mapping should be immediately offered or if the edit should be held in reserve until validated by a central authority.
  • An identity agent 100 is functionally paired to a website browser 102.
  • the browser is controlled by a user, who can direct the browser to connect to different servers, .
  • identity agent 100 detects that a server has provided a form to browser 102, a determination of whether a mapping between form fields and elements of an identity schema has been embedded in the form is made. If no mapping has been embedded, identity agent 100 connects to mapping table 108. Mapping table 108 is typically remotely accessed, although a local cache of the data of mapping table 108 can be accessed locally in some implementations. If a mapping for the form provided by a server is found in mapping table 108 or embedded in the form, the mapping is read by identity agent 100. Identity agent 100 presents an interface to the user allowing the user to make use of the mapping and select a set of data associated with an persona stored in identity store 110.
  • Identity store 110 can be local or remote to the user, though to address privacy concerns, identity store 110 is typically a local identity repository. The data in identity store 110 may be backed up to an identity store backup 112 that is remote to the user. Identity data can be stored in an encrypted state. Identity store 110 is used to hold the identity information of a user according to a defined schema. Identity information is preferably organized as a number of sets, each defining a persona. The Identity Agent 100 accesses the identity store 110 to obtain the information associated with a selected persona that is required for filling in a form.
  • Identity information is organized according to a defined schema.
  • Maps provide a pairing between form fields and elements in the identity schema.
  • the relationship between a form field and a schema element must be unique to avoid ambiguity (e.g. a name field on a form should uniquely point to one of a first name, a last name or a full name, but not to more than one.)
  • identity agent 100 submits the information to the site through browser 102.
  • the experience is seamless.
  • the user is provided with an interface to the identity agent 100.
  • the identity agent 100 provides an interface to the user allowing the user either to directly enter the information required bypassing identity agent 100, or to create a mapping for the form.
  • the user creates a mapping, the user is presented the name of the fields in the form (preferably in the order that they appear on the page). The user is then prompted to associate a schema element with each field where possible. Users can be provided with the ability to indicate that a field cannot be mapped, or that a new schema element is required.
  • the identity agent can make use of best-guess algorithms to map schema elements to form fields, and then provide the user with the ability to confirm or refine the selections. This reduces the time that the user has to spend creating mappings, and provides a human check of the mapping.
  • mapping After a user has defined a mapping, the identity agent 100 submits the data to the server through browser 102. User approval for the submission of the mapping can be sought prior to release of the mapping. The mapping is then added to the mapping table 108. New mappings may be held in a queue for a period of time to allow them to be vetted by an administrator. Alternatively, the mappings can be immediately made available and users can be provided with the ability to edit other user's mappings to correct errors in user-generated mappings.
  • the identity agent can be enabled to statistically analyze the data provided to a form. This analysis, in conjunction with the analysis performed by other identity agents on the same form, can be used as the basis for a mapping.
  • the interface provided to the user to indicate the availability of a mapping can, in some embodiments, be a translucent overlay on, or near the form.
  • the coloration of the overlay can be used to provide information to the user about the site. In one example, the coloration of the overlay can be changed to indicate the suspicion that a site is a phishing site that is seeking user information for illicit uses.
  • the translucent overlay can be placed a form, and can provide the user the ability to invoke identity agent 100.
  • the overlay can be used to indicate whether a form mapping is available or if an opportunity to create a mapping is available.
  • mapping When used to indicate that a mapping is available, it can be used to either invoke an identity agent interface that provides a persona selector, and allows the user to selectively approve the release of each element of identity information, or it can be used to provide a persona selector that allows rapid selection of a persona.
  • identity agent interface that provides a persona selector, and allows the user to selectively approve the release of each element of identity information, or it can be used to provide a persona selector that allows rapid selection of a persona.
  • the interface provided to the user can be a small icon placed in the form field.
  • a persona selector can be provided.
  • the persona selector can be provided as a series of translucent overlays, or can be provided in a separate window. When provided as a series of translucent overlays, the persona selector can function as a quick-pick selector.
  • the information associated with the persona can be inserted into the form fields. The user can either delete the information that should not be submitted, or by clicking on the icon placed into each of the form fields, can select different information to be submitted for each field individually.
  • Forms mapped in the mapping tables 108 are preferably grouped by a form type. Where some forms are designed to obtain profile information (such as information required during an online purchase), other forms are used for registration at a site.
  • profile information such as information required during an online purchase
  • other forms are used for registration at a site.
  • One of the key differences between these form types is that a username and password pairing is generated during registrations.
  • the type of form can be provided by the user during the mapping process, can be determined by best- guessing or a combination thereof.
  • the identity agent 100 can provide a randomly generated password, or can allow the user to enter her own password on a registration form. When the user enters a password, it is possible to associate that password with a password hint, so that in the future, the user can be provided with the chance to reuse the password with only the hint showing instead of the full password.
  • the icon can be altered to indicate which password has been submitted. Random passwords can be created to offer a degree of security that is difficult for most users to match. Providing different random passwords to different sites also ensures that the compromise of a password at one site will not necessarily lead to the compromise of a password at another site.
  • the mapping When a username and password pairing are generated, it is preferable for the mapping to store the URL of the page that will request the username and password as a login. This information can then be stored by the identity agent 100 so that the user will immediately be able to login to the site. With the login page URL known, the user can use a randomly generated password at registration and not need to have a copy of the password to create a login mapping. This enables full password management, and allows a user to have different passwords at different sites, each password being difficult to guess due to its random nature. It is difficult for users to provide this degree of password security for themselves. Many passwords are easy to attack using social attacks, and it is rare for users to use different passwords at different sites, especially if the passwords are difficult to guess.
  • the identity agent 100 of the present invention can be an identity management system aware identity agent. This allows identity agent 100 to determine if a login page makes use of an identity management system. If such a system is detected, a persona dedicated to the identity management system can be employed.
  • the identity agent can be OpenID-aware. When an OpenID compliant site is visited, the identity agent 100 need not request a mapping from mapping table 108, and instead can provide the credentials required for an OpenID login. The interface provided to the user by identity agent 100 can be altered to indicate that an identity management system login is requested.
  • a client based identity agent in conjunction with a distributed identity system, such as OpenID, prevents a number of identity attacks that rely upon deceptively attempting to obtain user passwords and OpenID URIs.
  • a local identity agent can be used to release the password only to a known OpenID provider, which will prevent the release of the information at a site that looks deceptively similar.
  • Certain forms require only a single data element, or a small set of data. These forms often request an email address, a postal code, or another simple release of data. If the form mapping identifies the form as such, identity agent 100 can automatically submit the information through browser 102, after the user selects the data for release from a quick pick menu, instead of allowing the user to view the filled form. This one-click experience allows small data sets, not used for registration, to be quickly submitted.
  • the identity agent can communicate with pseudonymous email address generators, such as those disclosed in issued Canadian Patent No. 2,447,121, (the contents of which are incorporated herein by reference) to obtain pseudonymous email addresses for use on forms requesting email addresses.
  • the identity agent can make use of an email address confirmation system to ensure that the user is associated with the email address that the pseudonymous email address redirects to. This allows users to sign up for services and provide email addresses to requesting sites, and maintain the ability to delete an email account if it is abused without detrimentally impacting on other logins.
  • a pseudonymous identity information generator in place of a pseudonymous email address generator, can be used.
  • a pseudonymous identity information generator creates mappings between generated identity information, such as phone numbers, addresses, and credit card numbers and identity information stored in the identity store.
  • the generation of the pseudonymous address information typically requires storing the identity information with the pseudonymous identity information generator, and allowing a mapping that when processed by external processing servers (e.g. credit card processing systems) resolves the pseudonymous information to the stored information.
  • FIG 2 illustrates an embodiment of the present invention instantiated as functional elements.
  • the Identity Agent 100 is shown in Figure 1 as connected to browser 102.
  • the connection between these elements is provided by browser interface 114.
  • Browser interface 114 may take advantage of publicly accessible application programming interfaces specific to a browser. If so desired, Identity agent 100 can be instantiated as a plugin or extension to an existing browser, or can be provided as a set of functions fully integrated into the browser.
  • the connection to mapping table 108 is provided by mapping table interface 116 which can make use of existing communication protocols.
  • the mapping table interface can communicate with the mapping table through the browser, in which case the functionality of the mapping table interface 116 can be integrated into the browser interface 114.
  • Mapping table interface handles the requests for mappings, the responses thereto as well as the transmission of new mappings to the mapping table.
  • Analysis engine 118 communicates to the browser 102 through the browser interface 114 and examines pages received by browser 102 from sites such as sitel 104 and site2 106. When the examination of pages results in the determination that a form has been received, analysis engine 118 transmits a request for a mapping to mapping table 108 through mapping table interface 116. The selection of the persona and obtaining user consent for the release of data is a function of the analysis engine.
  • User identity information is stored in Identity Store 110, which is shown here as discrete from the identity agent, but can be implemented as a contained element. The identity store houses the identity information, and is accessed by the analysis engine 118.
  • the identity store can be local and stored on the same device or machine as the browser, it can be stored on a secured and portable device, or it can be remotely accessible to the identity agent 100.
  • elements of the identity store are provided by the browser, which has a username and password storage facility.
  • the user directs the browser 102 to sitel 104 and retrieves a page having a form.
  • Analysis engine 118 in identity agent 100 detects the form and issues a request to mapping table 108 through mapping table interface 116.
  • the request contains the information required to identify the form, which may include the URL of the form, a form identification code, a list of the form fields, the destination to which the form data is sent, or any combination of the above.
  • the mapping table 108 identifies the form as a known form, and transmits a mapping to identity agent 100.
  • Analysis engine 118 receives the mapping, and presents the user with a persona selector allowing the user to select the set of data that will be provided to the form. When the users selects a persona, the analysis engine 118 obtains the information from identity store 110, and provides it to the browser 102 through browser interface 114. The data is then submitted to sitel 104.
  • mapping table 108 reports that the form is unkown.
  • Analysis engine 118 then prompts the user to create a mapping of the form. If the user agrees to create the mapping, the user is prompted to identify the identity schema element that should be provided for each of the fields on the form. Some fo the fields may not be mappable, and the user can indicate this where applicable.
  • the completed mapping is then transmitted to mapping table 108 through mapping table interface 116, and is used by analysis engine 118 to allow the user to submit the information associated with a persona. The process then continues as above.
  • mapping engine 118 the user is prompted to fill in the form instead of creating mapping.
  • the data entered into the form is then analyzed by analysis engine 118 and compared to data stored in identity store 110.
  • the analysis and comparison is used to generate a mapping that is submitted to mapping table 108 as outlined above.
  • analysis engine 118 determines that a form is present in a retrieved page it can analyze the form to determine whether a mapping is embedded in the form. If a mapping has been embedded, the mapping can be used without reference to mapping table 108. Additionally, analysis engine 118 can determine that the form is an identity management system form, such as an OpenED login form. In such a case, the identity management system information, such as an OpenID login credential, can be provided.
  • Embodiments of the invention may be represented as a software product stored in a machine-readable medium (also referred to as a computer-readable medium, a processor- readable medium, or a computer usable medium having a computer readable program code embodied therein).
  • the machine-readable medium may be any suitable tangible medium including a magnetic, optical, or electrical storage medium including a diskette, compact disk read only memory (CD-ROM), digital versatile disc read only memory (DVD-ROM) memory device (volatile or non-volatile), or similar storage mechanism.
  • the machine- readable medium may contain various sets of instructions, code sequences, configuration information, or other data, which, when executed, cause a processor to perform steps in a method according to an embodiment of the invention.
  • Those of ordinary skill in the art will appreciate that other instructions and operations necessary to implement the described invention may also be stored on the machine-readable medium.
  • Software running from the machine-readable medium may interface with circuitry to perform the described tasks.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Computational Linguistics (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Artificial Intelligence (AREA)
  • Software Systems (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Storage Device Security (AREA)

Abstract

Selon l'invention, un agent d'identification stocke des informations d'identité liées à un utilisateur, et exerce une fonction de remplissage de formulaires en ligne, à l'aide d'un système de mise en correspondance généré par l'utilisateur qui permet d'établir une correspondance entre les informations demandées et les informations stockées. Les tables de correspondance servant à associer les informations stockées aux informations demandées sont générées par les utilisateurs de l'agent d'identification, et sont partagées dans le cadre d'un effort collectif visant à réaliser une mise en correspondance répartie. Les informations d'identité peuvent être stockées sous la forme d'une persona, ce qui permet à un utilisateur d'utiliser une pluralité de personas.
PCT/CA2007/001623 2006-09-14 2007-09-14 Gestionnaire d'identités pour internet WO2008031219A1 (fr)

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
US82564306P 2006-09-14 2006-09-14
US60/825,643 2006-09-14
US82883906P 2006-10-10 2006-10-10
US60/828,839 2006-10-10
US82901706P 2006-10-11 2006-10-11
US60/829,017 2006-10-11
US86841006P 2006-12-04 2006-12-04
US60/868,410 2006-12-04
US88619407P 2007-01-23 2007-01-23
US60/886,194 2007-01-23

Publications (1)

Publication Number Publication Date
WO2008031219A1 true WO2008031219A1 (fr) 2008-03-20

Family

ID=39091968

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CA2007/001623 WO2008031219A1 (fr) 2006-09-14 2007-09-14 Gestionnaire d'identités pour internet

Country Status (2)

Country Link
CA (1) CA2600564C (fr)
WO (1) WO2008031219A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2463800A1 (fr) * 2010-12-08 2012-06-13 Disney Enterprises, Inc. Système et procédé d'association d'une identification d'utilisateur universel et identification d'utilisateur spécifique d'un domaine

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020156846A1 (en) * 2000-04-28 2002-10-24 Jai Rawat Intelligent client-side form filler
US6697839B2 (en) * 2001-11-19 2004-02-24 Oracle International Corporation End-to-end mobile commerce modules

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020156846A1 (en) * 2000-04-28 2002-10-24 Jai Rawat Intelligent client-side form filler
US6697839B2 (en) * 2001-11-19 2004-02-24 Oracle International Corporation End-to-end mobile commerce modules

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2463800A1 (fr) * 2010-12-08 2012-06-13 Disney Enterprises, Inc. Système et procédé d'association d'une identification d'utilisateur universel et identification d'utilisateur spécifique d'un domaine
US8769646B2 (en) 2010-12-08 2014-07-01 Disney Enterprises, Inc. System and method for associating a universal user identification and a domain specific user identification

Also Published As

Publication number Publication date
CA2600564A1 (fr) 2008-02-13
CA2600564C (fr) 2009-08-04

Similar Documents

Publication Publication Date Title
US20080071808A1 (en) Internet Identity Manager
US11025616B2 (en) Limited user authentication by self-recognition
US10560454B2 (en) Authentication system and method
US7496751B2 (en) Privacy and identification in a data communications network
US7275260B2 (en) Enhanced privacy protection in identification in a data communications network
US7085840B2 (en) Enhanced quality of identification in a data communications network
US7103912B2 (en) User authorization management system using a meta-password and method for same
CA2871049C (fr) Mots de passe uniques, aleatoires et abstraits destines a l'authentification de transaction
US7921456B2 (en) E-mail based user authentication
US8341710B2 (en) Ubiquitous webtoken
US20030084302A1 (en) Portability and privacy with data communications network browsing
US20030084171A1 (en) User access control to distributed resources on a data communications network
CN105791259B (zh) 一种个人信息保护的方法
JP4758175B2 (ja) 利用者認証方法及び利用者認証プログラム
CA2600564C (fr) Gestionnaire d'identite sur l'internet
JP4633458B2 (ja) ネットワーク上のｉｄ管理システム
JP2004102760A (ja) ウェブページアクセス制御システム
KR20180016447A (ko) 인터넷 포털시스템과 그 사용방법
CN113196263B (zh) 用户认证系统、用户认证服务器及用户认证方法
KR20180020977A (ko) 메시지 제공 및 평가 시스템
WO2007029849A1 (fr) Procede et systeme de gestion de mots de passe personnels, appareil et programme d'assistance a l'association de mots de passe personnels et serveur d'authentification
KR20050112943A (ko) 특화된 검색키워드를 이용한 개인화된 정보 제공 시스템및 방법
JP7013504B2 (ja) Ｉｄ連携システム
JP2007102351A (ja) ワークフロー管理システム、ワークフロー管理方法、及びワークフロー管理プログラム
KR20020007778A (ko) 복수 아이디를 활용한 온라인상의 폐쇄 소그룹과 개인공간의 결합 서비스방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07815817

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS EPO FORM 1205A DATED 29.06.2009.

122 Ep: pct application non-entry in european phase

Ref document number: 07815817

Country of ref document: EP

Kind code of ref document: A1