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
• • 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/60—Protecting data
  • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
  • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
  • G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
  • G06F21/6263—Protecting personal data, e.g. for financial or medical purposes during internet communication, e.g. revealing personal data from cookies
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F15/00—Digital computers in general; Data processing equipment in general
• • 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/33—User authentication using certificates
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q20/00—Payment architectures, schemes or protocols
  • G06Q20/38—Payment protocols; Details thereof
  • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q30/00—Commerce
  • G06Q30/06—Buying, selling or leasing transactions
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials

Definitions

• Identity is an important component enabling interactions in everyday life. For example, an individual's credit card enables merchants to identify and allow the individual to purchase products and services on credit. The same is true in the digital world as well, where digital identity enables digital interactions. For example, digital identities can be used to authenticate parties to each other in the digital environment. Knowing with whom one is interacting is an important element in deciding whether or not to trust and provide information to a party.
• An entity can use a digital identity to authenticate a party's identity or other personal information about the party.
• a digital identity can be issued by another entity and include information about the party. Examples of such information include the party's name, address, social security number, age, telephone number, etc.
• a party can have multiple digital identities issued by one or more other entities, similar to that of an individual having a driver's license, a credit card, and a frequent flyer card.
• the party can use a digital identity to identity itself to a third party.
• a third party such as an online service
• the party can forward to the third party a digital identity in the form of a security token issued by another entity trusted by the third party.
• the third party can provide access to the goods or services requested by the party.
• the party has little or no ability to control or view the contents of a security token issued by another entity.
• the party can unknowingly share personal information in the security token with the third party that the party does not need to share for authentication.
• the party can unknowingly provide personal information that the party does not want to share with the third party (e.g., social security number, telephone number, etc.).
• One aspect relates to a system for providing a digital identity that includes a claims transformer programmed to generate a security token including a computational token and a display token, the computational token including one or more claims associated with an identity of a principal, and the display token including display information about the claims in the computational token.
• the display information is configured to allow the principal to view the display token.
• Another aspect relates to a method for providing a digital identity, the method including: receiving a security token including a computational token and a display token, the computational token including one or more claims associated with an identity of a principal, and the display token including display information about the claims in the computational token; and displaying the display information in the display token for the principal so that the principal can review the contents of the display token.
• Yet another aspect relates to a computer-readable medium having computer- executable instructions for performing steps including: generating a security token including receiving a security token including a computational token and a display token, the computational token including one or more claims associated with an identity of a principal, and the display token including display information about the claims in the computational token; and displaying the display information in the display token for the principal so that the principal can review the contents of the display token.
• Figure 1 illustrates an example digital identity system
• Figure 2 illustrates an example general purpose computer system
• Figure 3 illustrates a portion of the system of Figure 1
• Figure 4 illustrates another portion of the system of Figure 1;
• Figure 5 illustrates an example security token
• Figure 6 illustrates an example computer system programmed to interpret and display a display token of a security token
• Figure 7 illustrates another portion of the system of Figure 1;
• Figure 8 illustrates an example method for authenticating a principal;
• Figure 9 illustrates an example method for interpreting and displaying a display token of a security token
• Figure 10 illustrates an example user interface for displaying a display token of a security token
• Figure 11 illustrates an example method for generating a security token including a computational token and a display token.
• Example embodiments disclosed herein relate generally to digital identities that can be exchanged between a first party and a second party to authenticate an identity and/or information related to the first party.
• the first party can be an individual, a company, an organization, a computer or other device, a service, or any other type of entity.
• the first party is referred to herein as the principal.
• the second party has goods, services, or other information that the principal desires to access and/or obtain.
• the second party is referred to herein as the relying party.
• an example digital identity system 100 including a principal 110 and a relying party 120.
• Principal 110 and relying party 120 can communicate with each other over one or more networks, as described further below.
• principal 110 can request goods, services, or other information from relying party 120, and relying party 120 can require authentication of the identity of or information about principal 110 before or in conjunction with providing the requested goods, services, or information.
• a claims transformer 130 and a claims authority 140 are one or more entities that can provide one or more claims or assertions about a principal.
• a claim is a statement made about the principal related to the principal's identity or information about the principal such as, for example, name, address, social security number, age, etc.
• claims transformer 130 and claims authority 140 can provide claims to the principal 110 and/or the relying party 120 in the form of a signed security token.
• claims authority 140 is in a trusted relationship with relying party 120 so that relying party 120 trusts the claims in the signed security token from claims authority 140.
• claims transformer 130 and claims authority 140 are shown as separate entities in Figure 1, in alternative embodiments claims transformer 130 and claims authority 140 can be the same entity or different entities.
• claims transformer 130 is illustrated as being in communication with principal 110, in alternative embodiments, relying party 120 can communicate directly with claims transformer 130, as described further below.
• system 100 is implemented as an InfoCard system provided in the WINFX application programming interface developed by Microsoft Corporation of Redmond, Washington.
• the InfoCard system allows principals to manage multiple digital identities from various claims authorities.
• the InfoCard system utilizes a web services platform such as the Windows Communication Foundation in the WINFX application programming interface.
• the InfoCard system is built using the Web Services Security
• WS-Security Specifications propagated at least in part by Microsoft Corporation of Redmond, Washington. These specifications include a message security model WS-Security, an endpoint policy WS-SecurityPolicy, a metadata protocol WS- MetadataExchange, and a trust model WS-Trust.
• WS-Security model describes how to attach security tokens to messages.
• SecurityPolicy model describes end point policy requirements, such as required security tokens and supported encryption algorithms, implemented using a metadata protocol WS-MetadataExchange.
• the WS-Trust model describes a framework for trust models that enable different web services to interoperate. Example embodiments described herein refer to the Web Services Security
• one or more different specifications can be used to facilitate communications between the various elements in system 100.
• principal 110 is an individual that uses a computer system such as an example computer system 200 to communicate with relying party 120 and claims transformer 130.
• Computer system 200 can take a variety of forms such as, for example, a desktop computer, a laptop computer, and a hand-held computer.
• computer system 200 is illustrated, the systems and methods disclosed herein can be implemented in various alternative computer systems as well.
• the system 200 includes a processor unit 202, a system memory 204, and a system bus 206 that couples various system components including the system memory 204 to the processor unit 202.
• the system bus 206 can be any of several types of bus structures including a memory bus, a peripheral bus and a local bus using any of a variety of bus architectures.
• the system memory includes read only memory (ROM) 208 and random access memory (RAM) 210.
• ROM read only memory
• RAM random access memory
• BIOS basic input/output system 212
• BIOS basic routines that help transfer information between elements within the computer system 200, is stored in ROM 208.
• the computer system 200 further includes a hard disk drive 212 for reading from and writing to a hard disk, a magnetic disk drive 214 for reading from or writing to a removable magnetic disk 216, and an optical disk drive 218 for reading from or writing to a removable optical disk 219 such as a CD ROM, DVD, or other optical media.
• the hard disk drive 212, magnetic disk drive 214, and optical disk drive 218 are connected to the system bus 206 by a hard disk drive interface 220, a magnetic disk drive interface 222, and an optical drive interface 224, respectively.
• the drives and their associated computer-readable media provide nonvolatile storage of computer readable instructions, data structures, programs, and other data for the computer system 200.
• the example environment described herein can employ a hard disk 212, a removable magnetic disk 216, and a removable optical disk 219
• other types of computer-readable media capable of storing data can be used in the example system 200.
• Examples of these other types of computer-readable mediums that can be used in the example operating environment include magnetic cassettes, flash memory cards, digital video disks, Bernoulli cartridges, random access memories (RAMs), and read only memories (ROMs).
• a number of program modules can be stored on the hard disk 212, magnetic disk 216, optical disk 219, ROM 208, or RAM 210, including an operating system 226 such as the WINDOWS operating system from Microsoft Corporation, one or more application programs 228, other program modules 230, and program data 232.
• a user may enter commands and information into the computer system 200 through input devices such as, for example, a keyboard 234, mouse 236, or other pointing device.
• input devices such as, for example, a keyboard 234, mouse 236, or other pointing device.
• Other input devices include a toolbar, menu, touch screen, microphone, joystick, game pad, pen, satellite dish, and scanner.
• serial port interface 240 that is coupled to the system bus 206.
• these input devices also may be connected by other interfaces, such as a parallel port, game port, or a universal serial bus (USB).
• An LCD display 242 or other type of display device is also connected to the system bus 206 via an interface, such as a video adapter 244.
• computer systems can typically include other peripheral output devices (not shown), such as speakers and printers.
• the computer system 200 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 246.
• the remote computer 246 may be a computer system, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer system 200.
• the network connections include a local area network (LAN) 248 and a wide area , network (WAN) 250.
• LAN local area network
• WAN wide area , network
• the computer system 200 When used in a LAN networking environment, the computer system 200 is connected to the local network 248 through a network interface or adapter 252. When used in a WAN networking environment, the computer system 200 typically includes a modem 254 or other means for establishing communications over the wide area network 250, such as the Internet.
• the modem 254 which can be internal or external, is connected to the system bus 206 via the serial port interface 240.
• program modules depicted relative to the computer system 200, or portions thereof may be stored in the remote memory storage device. It will be appreciated that the network connections shown are examples and other means of establishing a communications link between the computers may be used.
• the embodiments described herein can be implemented as logical operations in a computing system.
• the logical operations can be implemented (1) as a sequence of computer implemented steps or program modules running on a computer system and (2) as interconnected logic or hardware modules running within the computing system.
• This implementation is a matter of choice dependent on the performance requirements of the specific computing system. Accordingly, the logical operations making up the embodiments described herein are referred to as operations, steps, or modules. It will be recognized by one of ordinary skill in the art that these operations, steps, and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof without deviating from the spirit and scope of the disclosure.
• This software, firmware, or similar sequence of computer instructions may be encoded and stored upon computer readable storage medium and may also be encoded within a carrier-wave signal for transmission between computing devices.
• example principal 110 and relying party 120 are again shown.
• Principal 110 can communicate with relying party 120 using, for example, a computer system 300 (see Figure 6) that is similar to computer system 200 described above.
• principal 110 uses computer 300 to send a request to relying party 120 for goods, services, or other information.
• principal 110 sends a request to relying party 120 for access to information that principal 110 desires.
• the request sent by principal 110 can include a request for the security policy of relying party 120 using, for example, the mechanisms provided in WS- MetadataExchange.
• relying party 120 sends principal 110 requirements for relying party 120 to authenticate the identity or other information about principal 110.
• the requirements of relying party 120 for authentication are referred to herein as a security policy.
• the security policy defines the set of claims that the principal 110 must provide to relying party 120 for relying party 120 to authenticate principal 110.
• relying party 120 specifies its security policy using WS- SecurityPolicy, including both the claim requirements and type of security token required by relying party 120.
• WS-SecurityPolicy A basic form for a security policy in accordance with WS-SecurityPolicy is illustrated in the example below. ⁇ sp:IssuedToken ...>
• Last Name - Type xs:string - surname or family name of a subject
• Email Address - Type xs : string - preferred address for the "To:" field of email to be sent to the subject, usually of the form ⁇ user>@ ⁇ domain>;
• Postal Code - Type xs:string - postal code or zip code component of a subject's address information
• Country - Type xs: string - country of a subject
• the policy can also be used to specify the type of security token required by relying party 120, or a default type can be used as specified by WS-Trust.
• a default type can be used as specified by WS-Trust.
• the above-noted policy specifies a certain type of security token that is required by relying party 120 (i.e., "wstTokenType").
• the security policy can specify a specific claims authority required by the relying party ("sp:Issuer"), as shown below.
• the policy can omit this element, leaving a determination of the appropriate claims authority up to the principal.
• Other elements can be specified in the security policy as well such as, for example, the freshness of the required security token.
• principal 110 can request one or more security tokens from claims authority 140 using the issuance mechanism described in WS-Trust. In one example, principal 110 forwards the claim requirements in the policy of relying party 120 to claim authority 140.
• the identity of relying party 120 can, but need not, be specified in the request sent by principal 110 to the claims authority 140.
• the request can include other requirements as well, such as a request for a display token, as described further below.
• claims authority 140 can have its own security policy as specified in WS-SecurityPolicy and require authentication of principal 110 before claims authority 140 forwards a security token to principal 110.
• Claims authority 140 can provide one or more of the claims required by the policy from relying party 120.
• claims authority 140 is programmed to generate one or more claims required by the policy.
• Claims transformer 130 is programmed to translate the claims of claims authority 140 into one or more claims that can be understood by relying party 120.
• claims transformer 130 generates one or more signed security tokens 150 that include the one or more claims, as described below.
• the security token 150 can then be forwarded to principal 110.
• claims transformer 130 forwards the security token 150 to principal 110 using the response mechanisms described in WS-Trust.
• security token 150 includes a computational token 152 and a display token 154.
• Computational token 152 includes the claims provided by claims authority 130 in an encrypted format.
• claims transformer 130 generates computational token 152 in an encrypted format that can be understood (i.e., decrypted) by relying party 120, as described below.
• Claims transformer 130 also generates display token 154.
• display token 154 includes at least a summary of the claims that are included in computational token 152 of security token 150.
• display token 154 includes a list of all of the claims included in computational token 152.
• Display token 154 can be generated in a format that can be reviewed by principal 110 using, for example, computer system 300, as described below.
• display token 154 is generated in a plain text format or a Hypertext Markup Language ("HTML”) format.
• HTML Hypertext Markup Language
• security token 150 including computational token 152 is issued in accordance with the Security Assertion Markup Language ("SAML") standard promulgated by the Organization for the Advancement of Structured Information Standards (“OASIS").
• SAML Security Assertion Markup Language
• OASIS Organization for the Advancement of Structured Information Standards
• security token 150 can be issued in accordance with SAML 1.1 or SAML 2.0 standards.
• Other standards can also be used such as, for example and without limitation, an X.509 certificate and a Kerberos ticket.
• security token 150 can be cryptographically signed or endorsed by claims transformer 130 using a known algorithm.
• a 2048-bit asymmetric RSA key is used.
• other encryption algorithms can be used such as, for example, a base64 encoded symmetric encryption key.
• a symmetric key is used by default. In this manner, in the example shown, a party such as relying party 120 can cryptographically verify that security token 150 originated from claims transformer 140.
• computational token 152 is cryptographically bound to display token 154 using one or more known algorithms such as, for example and without limitation, using a digital signature over the entire response message from the claims authority containing both the computational token 152 and the display token 154.
• example computer system 300 of principal 110 can include an interpreter 312 and a display 314.
• interpreter 312 can be one or more application programs (see, e.g., programs 228 described above) executable by computer system 300.
• display 314 can be an output device such as a printer or monitor (see, e.g., monitor 242) that can output information to principal 110.
• interpreter 312 is programmed to interpret display token 152 of security token 150.
• interpreter 312 can identify the claims that are summarized in display token 152, and interpreter 312 can display the claims for principal 110 using display 314.
• principal 110 can utilize the summary of the claims included in security token 150 provided on display 314 to make a decision as to whether or not to share security token 150 with relying party 120.
• principal 110 can forward security token 150 to relying party 120 to satisfy all or a part of the security policy of relying party 120.
• principal 110 can forward security token 150 to relying party 120 by binding security token 150 to an to application message using the security binding mechanisms described in WS-Security.
• relying party 120 can cryptographically verify the origin of signed security token 150.
• Relying party 120 can also utilize the claims in computation token 152 of security token 150 to satisfy the security policy of relying party 120 to authenticate principal 110.
• relying party 120 can provide access to the goods, services, or other information requested by principal 110.
• Method 400 for authenticating a principal is shown.
• Method 400 is described with reference to a non-limiting example wherein the principal is Employee A.
• Employee A is an employee of a company referred to as "Company A,” and the relying party is a travel agency referred to as "Travel Agency A.”
• Company A has partnered with Travel Agency A for making travel arrangements for employees of Company A at discounted rates.
• a principal requests information from a relying party.
• Employee A utilizes an application program on Employee A's computer to request travel arrangements from the web site of Travel Agency A.
• Employee A's computer receives the security policy from the web site of Travel Agency A. This policy requires that Employee A submit a security token with a claim establishing that Employee A is an employee of Company A before Employee A can access the discounted travel arrangements on the web site of Travel Agency A.
• Employee A's computer forwards the policy to a claims authority, which in the present example is a security token service or STS operated by Company A.
• Employee A's computer receives a signed security token from the STS of Company A.
• the security token includes a computational token and a display token, with the computational token including the claim establishing that Employee A is an employee of Company A.
• Control is then passed to operation 450, and Employee A's computer presents the summary of the claims from the display token to Employee A for review.
• Employee A can decide whether or not to forward the security token to the web site of Travel Agency A based on the information in the display token presented to Employee A.
• the security token from Company A not only includes a claim establishing that Employee A is an employee of Company A, but also includes a claim with Employee As home telephone number, Employee A may not be comfortable sharing Employee A's home telephone number with Travel Agency A. In this situation, Employee A can review the display information from the display token of the security token, determine that the security token includes Employee A's home telephone number, and decide not to forward the security token to Travel Agency A.
• the display token of the security token is interpreted by the principal.
• an application program such as a web browser plug-in or applet or another application is programmed to interpret the information contained in the display token.
• the application is programmed to display the information to the principal using a graphical user interface such as a web browser interface.
• a graphical user interface such as a web browser interface.
• User interface 550 displays information in a display token of a security token.
• User interface 550 includes a list 555 of the display information from the display token.
• the display information includes employer information (e.g., "Company A”) and home telephone number (e.g., "999-999- 9999").
• User interface 550 also includes a send element 557 and a cancel element 559. The principal can select send element 557 to send the security token to the relying part (e.g., Travel Agency A), or select cancel element 559 to refrain from sending the security token.
• additional information can be provided in user interface 550.
• information about other security tokens that have been sent to a particular relying party can be listed, and/or information about where the particular security token currently being displayed has been sent previously can be listed.
• information about the particular relying party to which the security token is going to be sent can be provided in the user interface, and/or links to obtain additional information about the relying party can be provided. Other configurations are possible.
• method 600 for a claims authority and a claims transformer to generate a security token including a computational token and a display token is shown.
• method 600 is described with reference to the non-limiting example provided above, wherein the principal is Employee A, the relying party is Travel Agency A, and the claims authority and claims transformer are Company A.
• the STS of Company A receives the policy of Travel Agency A forwarded by Employee A.
• Company A generates a computation token including one or more claims required by the policy.
• a display token including display information about the claims in the computational token is generated.
• the display token is logically bound to the computational token to generate the security token.
• the security token including the computational token and the display token are forwarded to Employee A bound together cryptographically in the response message.
• a display token can be provided by default in each security token issued by a claims transformer. In other embodiments, a display token is provided only if the principal requests the display token.
• An example of such a display token request included in a security token request is as follows. ⁇ wst:RequestSecurityToken>
• a security token lacks a display token
• the principal is notified of the lack of a display token, and the principal can decide whether or not to forward the security token to a relying party.
• no display token is provided, no display information is presented to the principal.
• a principal can review the display information from the display token and decide whether or not to forward the security token to a relying party. In other embodiments, the principal can review the display information, but does not have the option to stop the forwarding of the security token to the relying party. In other words, once the security token is requested by the principal, the security token is automatically forwarded to the relying party once the security token is received by the principal.
• only the computational token portion of a security token is forwarded by the principal to the relying party.
• the principal forwards the entire security token including both the computational token and the display token to the relying party.
• example embodiments shown herein illustrate a security token that is forwarded by a claims transformer to a principal and then on to a relying party
• the security token can be forwarded directly from the claims transformer to the relying party.
• one security token including a computational token (and possibly a display token) can be forwarded to the relying party
• another security token including a display token can be forwarded to the principal.
• Other configurations are possible.
• the example embodiments shown herein illustrate a security policy requiring only a single claim and a single security token issued by one claims transformer, in other embodiments a policy can require multiple claims, and one or more claims authorities can issue one or more security tokens with one or more claims to satisfy the policy.
• the principal is an individual, in alternative embodiments, the principal can be a company, an organization, a computer or other device, a service, or any other type of entity.
• the principal is a device that is part of a network.
• the device can request information, such as a software update, from another device on the network functioning as a relying party.
• the relying party can require authentication of the identity of the device before the relying party provides the requested update.
• the device can request one or more claims required by the security policy of the relying party from one or more claims transformers, and the claims transformers can provide one or more security tokens including display tokens to the device.
• the device can be programmed to review the contents of the display tokens and decide whether or not to forward the security token to the relying party based on its contents. If the device forwards the security token to the relying party, the relying party can then complete the authentication process and provide the requested update to the device.
• a security token including both a computation token and a display token with display information that can be reviewed by a principal.
• a principal can efficiently review the contents of a security token using an application program on the client computer system of the principal programmed to interpret and display the contents of the display token.
• the principal's review of the contents of the security token enables the principal to have more control over the information shared with relying parties in the security token.
• such a system including a security token with both a computational token and a display token bound together can provide an auditable trail should disclosure of unauthorized information about the principal occur.

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Computer Security & Cryptography (AREA)
• Computer Hardware Design (AREA)
• General Engineering & Computer Science (AREA)
• Physics & Mathematics (AREA)
• Business, Economics & Management (AREA)
• General Physics & Mathematics (AREA)
• Accounting & Taxation (AREA)
• Finance (AREA)
• Software Systems (AREA)
• Signal Processing (AREA)
• Computer Networks & Wireless Communication (AREA)
• General Health & Medical Sciences (AREA)
• Health & Medical Sciences (AREA)
• Bioethics (AREA)
• Computing Systems (AREA)
• Strategic Management (AREA)
• General Business, Economics & Management (AREA)
• Development Economics (AREA)
• Economics (AREA)
• Marketing (AREA)
• Medical Informatics (AREA)
• Databases & Information Systems (AREA)
• Storage Device Security (AREA)

Priority Applications (5)

Applications Claiming Priority (2)

Publications (1)

Family

ID=38175330

Family Applications (1)

Country Status (8)

Cited By (1)

Families Citing this family (64)

Citations (4)

Family Cites Families (51)

• 2005
  • 2005-12-19 US US11/312,920 patent/US7788499B2/en active Active
• 2006
  • 2006-11-22 KR KR1020087014863A patent/KR101319636B1/ko active IP Right Grant
  • 2006-11-22 EP EP06838382A patent/EP1964043A4/en not_active Ceased
  • 2006-11-22 CN CN2006800475254A patent/CN101331509B/zh not_active Expired - Fee Related
  • 2006-11-22 BR BRPI0620078-8A patent/BRPI0620078A2/pt not_active IP Right Cessation
  • 2006-11-22 JP JP2008545618A patent/JP5010615B2/ja not_active Expired - Fee Related
  • 2006-11-22 RU RU2008124907/08A patent/RU2421789C2/ru not_active IP Right Cessation
  • 2006-11-22 WO PCT/US2006/045386 patent/WO2007075247A1/en active Application Filing

Patent Citations (4)

Also Published As

Similar Documents

Legal Events