Method and apparatus for trusted federated identity management and data access authorization

• US 8,881,257 B2
• Filed: 01/21/2011
• Issued: 11/04/2014
• Est. Priority Date: 01/22/2010
• Status: Active Grant

• Current Assignee: InterDigital Patent Holdings, Inc. (InterDigital, Inc.)
• Original Assignee: InterDigital Patent Holdings, Inc. (InterDigital, Inc.)
• Inventors: Cha, Inhyok, Schmidt, Andreas, Leicher, Andreas, Shah, Yogendra C.
• Primary Examiner(s): Homayounmehr, Farid
• Assistant Examiner(s): SARKER, SANCHIT K
• Application Number:
  US13/011,558
• Publication Number:
  US 20120023568A1
• Time in Patent Office: 1,383 Days
• Field of Search: 726/1, 726/3, 726/10
• US Class Current: 726/10
• CPC Class Codes: G06F 21/335 for accessing specific resources, e.g. using Kerberos tickets
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: G06F 2221/2115 Third party
• CPC Class Codes: H04L 2463/121 Timestamp
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04W 12/069 using certificates or pre-shared keys

Abstract

Systems, methods, and instrumentalities are disclosed that may provide for integration of trusted OpenID (TOpenID) with OpenID. The authentication may be accomplished, in part, via communications between a trusted ticket server on a UE and a network application function. The UE may retrieve platform validation data (e.g., from a trusted platform module on the UE). The UE may receive a platform verification in response to the platform validation data. The platform verification may indicate that the network application function has verified the platform validation data and the user. The platform verification may indicate that the platform validation data matches a previously generated reference value.

Claims

1. A method performed at a wireless device having a user, the method comprising:

receiving, by the wireless device, an authentication request from a network application function, the authentication request comprising an OpenID identity that corresponds to the user;

when the authentication request is accepted, retrieving, by a trusted ticket server residing on the wireless device, authentication data and platform validation data using a storage root key, wherein the platform validation data includes a measure of trustworthiness of the wireless device and a measure of trustworthiness of the trusted ticket server, and the authentication data is associated with the OpenID identity that corresponds to the user;

sending the platform validation data and the authentication data associated with the OpenID identity that corresponds to the user to the network application function; and

receiving verification data indicating that the network application function has verified the platform validation data and the OpenID identity that corresponds to the user.

2. The method of claim 1, wherein the verification data indicates that a system state indicated by the platform validation data matches a previously generated reference value.

3. The method of claim 1, wherein the platform validation data is signed.

4. The method of claim 1, wherein the platform validation data includes a user identification parameter.

5. The method of claim 1, wherein the platform validation data includes attestation data.

6. The method of claim 5, wherein the attestation data includes an SML and a PCR quote signed with an AIK.

7. The method of claim 1, further comprising receiving a ticket comprising the verification data, wherein the ticket is capable of being reused to perform a subsequent authorization without revalidation of the wireless device.

8. The method of claim 7, wherein the ticket includes a timestamp.

9. The method of claim 7, wherein the ticket includes an origination timestamp.

10. The method of claim 7, wherein the ticket includes a lifetime limit.

11. The method of claim 7, wherein the ticket includes an end date.

12. The method of claim 7, wherein the ticket includes a usage parameter limit.

13. The method of claim 7, further comprising receiving a ticket reference from a network entity.

14. The method of claim 13, wherein the ticket reference is capable of being used to obtain the ticket from the network application function, and wherein the verification data is capable of being reused to perform a subsequent authorization without revalidation of the wireless device.

15. The method of claim 1, further comprising:

establishing a connection to a relying party;

receiving a browser redirection to the network application function; and

sending an authentication request to the network application function.

16. The method of claim 1, wherein the verification data indicates access granted to a relying party.