Proxy Bypass Login for Applications on Mobile Devices

• US 20150373009A1
• Filed: 08/31/2015
• Published: 12/24/2015
• Est. Priority Date: 03/20/2012
• Status: Active Grant

• Current Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Original Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Inventors: Alison, Thomas, Berdichevsky, Micha, Pandit, Shashank, Eldar, Bosmat Mazal
• Granted Patent: US 9,578,011 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: H04L 63/0281 Proxies
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• 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: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/0884 by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 4/21 for social networking applications

Abstract

In one embodiment, an intermediate server receives a request with a secure ID to authorize a software application, transmits the secure ID to a system, receives an access token from the system indicating that the software application has been authorized, evaluates the access token for validity, and transmits a response to the mobile device indicating the software application is authorized.

Claims

1. A method comprising:

authenticating, at a system, a user of a mobile device;

receiving, at the system via an intermediate server, a first request from the mobile device to install a software application on the mobile device;

transmitting, from the system via the intermediate server, data to the mobile device comprising the software application and a first secure ID;

receiving, at the system via the intermediate server, a second request from the mobile device to authorize the software application, the second request comprising a second secure ID, wherein the second secure ID is based on the first secure ID;

evaluating, at the system, the second secure ID for validity; and

transmitting, from the system via the intermediate server, a response to the mobile device in accordance with the evaluation.

2. The method of claim 1, wherein:

the second secure ID is evaluated as invalid; and

the response comprises a third request to the mobile device to authenticate the user of the mobile device.

3. The method of claim 1, wherein:

the second secure ID is evaluated as valid; and

the response comprises an access token, wherein the access token indicated the software application has been authorized by the system.

4. The method of claim 3, wherein the access token authorizes the software application to access social-networking data from the system.

5. The method of claim 1, wherein evaluating the second secure ID for validity comprises determining that the second secure ID is based on the first secure ID.

6. The method of claim 1, wherein evaluating the second secure ID for validity comprises determining that the second secure ID substantially matches the first secure ID.

7. The method of claim 1, wherein the second secure ID comprises a timestamp, wherein the timestamp is based on the time when the data was transmitted to the mobile device.

8. The method of claim 7, the method further comprising:

determining, at the system, that the timestamp is older than a threshold period of time; and

indicating, at the system via the intermediate server, that the second secure ID is not valid.

9. The method of claim 8, wherein the threshold period of time is 24 hours.

10. The method of claim 7, the method further comprising:

determining, at the system, that the timestamp is not older than a threshold period of time; and

indicating, at the system via the intermediate system, that the second secure ID is valid.

11. The method of claim 10, wherein the threshold period of time is 24 hours.

12. The method of claim 1, wherein the user is associated with a social-networking system.

13. The method of claim 1, wherein the first secure ID or second secure ID are encrypted.

14. The method of claim 1, wherein the second secure ID comprises information indicating that the user of the mobile device is authenticated.

15. The method of claim 1, further comprising:

generating, at the system, a session in response to the first request, the session comprising the first secure ID; and

storing, at the system, the session.

16. The method of claim 15, further comprising:

accessing, at the system via the intermediate server, the first secure ID from the stored session; and

wherein evaluating the second secure ID for validity comprises determining that the second secure ID substantially matches the first secure ID from the stored session.

17. The method of claim 16, wherein the session is an application programming interface (API) session.

18. An apparatus comprising:

one or more processors; and

a memory coupled to the processors comprising instructions executable by the processors, the processors operable when executing the instructions to;

authenticate, at a system, a user of a mobile device;

receive, at the system via an intermediate server, a first request from the mobile device to install a software application on the mobile device;

transmit, from the system via the intermediate server, data to the mobile device comprising the software application and a first secure ID;

receive, at the system via the intermediate server, a second request from the mobile device to authorize the software application, the second request comprising a second secure ID, wherein the second secure ID is based on the first secure ID;

evaluate, at the system, the second secure ID for validity; and

transmit, from the system via the intermediate server, a response to the mobile device in accordance with the evaluation.

19. One or more computer-readable non-transitory storage media embodying software that is operable when executed to:

authenticate, at a system, a user of a mobile device;

receive, at the system via an intermediate server, a first request from the mobile device to install a software application on the mobile device;

transmit, from the system via the intermediate server, data to the mobile device comprising the software application and a first secure ID;

receive, at the system via the intermediate server, a second request from the mobile device to authorize the software application, the second request comprising a second secure ID, wherein the second secure ID is based on the first secure ID;

evaluate, at the system, the second secure ID for validity; and

transmit, from the system via the intermediate server, a response to the mobile device in accordance with the evaluation.