MANAGING DIGITAL IDENTITY INFORMATION
4 Assignments
0 Petitions
Accused Products
Abstract
A basic architecture for managing digital identity information in a network such as the World Wide Web is provided. A user of the architecture can organize his or her information into one or more profiles which reflect the nature of different relationships between the user and other entities, and grant or deny each entity access to a given profile. Various enhancements which may be provided through the architecture are also described, including tools for filtering email, controlling access to user web pages, locating other users and making one'"'"'s own location known, browsing or mailing anonymously, filling in web forms automatically with information already provided once by hand, logging in automatically, securely logging in to multiple sites with a single password and doing so from any machine on the network, and other enhancements.
23 Citations
31 Claims
-
1-17. -17. (canceled)
-
18. In a computing system environment, a method for managing digital identity information, comprising:
-
storing at least one electronic profile comprising identity information of a first user in a first user vault object; storing at least one electronic profile comprising identity information of a second user in a second user vault object that is different from the first user vault object; and on completion of an acceptable contact, automatically federating identity information between the first user vault object and the second user vault object whereby read-only access is granted between the first user'"'"'s and the second user'"'"'s respective at least one electronic profiles. - View Dependent Claims (19, 20, 21, 22, 23, 24, 25, 26)
-
-
27. In a computing system environment, a method for managing digital identity information, comprising:
-
storing at least one electronic profile comprising identity information of a user in a first vault object; storing at least one electronic profile comprising information of another entity in a second vault object that is different from the first vault object; on completion of an acceptable contact between the user and another entity, automatically federating at least a portion of the user identity information and the another entity information across a network. - View Dependent Claims (28, 29, 30, 31)
-
Specification