IP Library Granted Patent US 8,112,790
Granted Patent B2
US 8,112,790 · App. 11/171,513 · Granted Feb 7, 2012

Methods and apparatus for authenticating a remote service to another service on behalf of a user

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,112,790
App. No.
11/171,513
Granted
Feb 7, 2012
Kind
B2
Abstract

Methods and apparatus are provided for authenticating a remote service to another service on behalf of a user. A user client authorizes a remote application client to perform one or more actions with a server on behalf of the user client. The user client provides one or more keys to a remote authentication service; receives an identifier of the remote application client, where the remote authentication client is remote from the server; and notifies the remote authentication service that the remote application client is authorized to obtain a response from the remote authentication service regarding a challenge from the server, where the response is based on at least one of the one or more keys stored by the remote authentication service on behalf of the user client. The remote application client provides a challenge that is received from a server that the remote application client is attempting to access for the user client and an identifier of the user client to a remote authentication service and receives a response to the challenge from the remote authentication service, wherein the response is based on one or more keys stored by the remote authentication service on behalf of the user client.

Claims (34)

1. A method performed by a user client to provide authorization to a remote application client that performs one or more actions with a server for said user client, comprising:

providing one or more keys to a remote authentication service;

receiving an identifier of said remote application client, wherein said remote application client is remote from said server; and

notifying said remote authentication service, wherein said notification authorizes said remote authentication service to perform an authentication procedure without participation from said user client, wherein said authentication procedure comprises receiving a challenge from said remote application client without participation from said user client, generating a credential without participation from said user client based on said challenge received from said remote application client, and issuing said credential to said remote application client without participation from said user client, wherein said credential is based on at least one of said one or more keys stored by said remote authentication service on behalf of said user client.

2. The method of claim 1 , further comprising the step of creating an account with said remote authentication service.

3. The method of claim 1 , further comprising the step of establishing an identity of said user client to said remote authentication service.

4. The method of claim 1 , wherein said remote application client can perform said actions on behalf of said user client without obtaining said one or more keys.

5. The method of claim 1 , further comprising the step of notifying said user client when said remote application client obtains said credential.

6. A method performed by a remote application client that performs one or more actions for a user client, comprising:

receiving a challenge from a server that said remote application client is attempting to access for said user client, wherein said remote application client is remote from said server, wherein a notification authorizes a remote authentication service to perform an authentication procedure without participation from said user client, wherein said authentication procedure comprises receiving a challenge from said remote application client without participation from said user client, generating a credential without participation from said user client based on said challenge received from said remote application client, and issuing said credential to said remote application client without participation from said user client;

providing said challenge from said server and an identifier of said user client to said remote authentication service during a remote application transaction;

receiving said credential to said challenge from said remote authentication service, wherein said response is based on one or more keys stored by said remote authentication service on behalf of said user client; and

providing said credential to said server.

7. The method of claim 6 , further comprising the step of creating an account with said remote authentication service.

8. The method of claim 6 , further comprising the step of establishing an identity of said remote application client to said remote authentication service.

9. The method of claim 6 , wherein said remote application client can perform said actions on behalf of said user client without obtaining said one or more keys.

10. A method performed by a remote authentication service for managing one or more keys for a user client, comprising:

receiving said one or more keys from said user client;

receiving a notification from said user client, wherein said notification authorizes said remote authentication service to perform an authentication procedure without participation from said user client, wherein said authentication procedure comprises receiving a challenge from a remote application client without participation from said user client, generating a credential without participation from said user client based on said challenge received from said remote application client, and issuing said credential to said remote application client without participation from said user client, wherein said credential is based on at least one of said one or more keys, wherein said remote application client is remote from said server;

receiving said challenge and an identifier of said user client from said remote application client; and

providing said credential to said challenge to said remote application client.

11. The method of claim 10 , further comprising the step of establishing an identity of said user client.

12. The method of claim 10 , further comprising the step of establishing an identity of said remote application client.

13. The method of claim 10 , wherein said remote application client can perform said actions on behalf of said user client without obtaining said one or more keys.

14. The method of claim 10 , further comprising the step of notifying said user client when said credential is provided to said remote application client.

15. An apparatus implemented by a remote authentication service for managing one or more keys for a user client, the apparatus comprising:

a tangible readable recordable memory; and

at least one processor, coupled to the memory, operative to:

receive said one or more keys from said user client;

receive a notification from said user client, wherein said notification authorizes said remote authentication service to perform an authentication procedure without participation from said user client, wherein said authentication procedure comprises receiving a challenge from a remote application client without participation from said user client, generating a credential without participation from said user client based on said challenge received from said remote application client, and issuing said credential to said remote application client without participation from said user client, wherein said credential is based on at least one of said one or more keys, wherein said remote application client is remote from said server;

receive said challenge and an identifier of said user client from said remote application client; and

provide said credential to said challenge to said remote application client.

16. The apparatus of claim 15 , wherein said processor is further configured to establish an identity of said user client and said remote application client.

17. The apparatus of claim 15 , wherein said remote application client can perform said actions on behalf of said user client without obtaining said one or more keys.

Assignments (6)
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE'S ADDRESS PREVIOUSLY RECORDED AT REEL: 045397 FRAME: 0598. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Jul 12, 2018
From: ALCATEL LUCENT
To: BEIJING XIAOMI MOBILE SOFTWARE CO.,LTD.
Reel/Frame 046544/0365 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE ADDRESS PREVIOUSLY RECORDED AT REEL: 045397 FRAME: 0598. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Apr 10, 2018
From: ALCATEL LUCENT
To: BEIJING XIAOMI MOBILE SOFTWARE CO.,LTD.
Reel/Frame 046478/0193 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 21, 2018
From: ALCATEL LUCENT
To: BEIJING XIAOMI MOBILE SOFTWARE CO.,LTD.
Reel/Frame 045397/0598 →
CHANGE OF ADDRESS Recorded Feb 21, 2018
From: ALCATEL LUCENT
To: ALCATEL LUCENT
Reel/Frame 045815/0013 →
RELEASE OF SECURITY INTEREST Recorded Sep 30, 2014
From: CREDIT SUISSE AG
To: ALCATEL LUCENT
Reel/Frame 033868/0001 →
SECURITY AGREEMENT Recorded Jan 30, 2013
From: ALCATEL LUCENT
To: CREDIT SUISSE AG
Reel/Frame 029821/0001 →