Server based settings for client software with asymmetric signing

• US 10,218,505 B1
• Filed: 02/09/2018
• Issued: 02/26/2019
• Est. Priority Date: 08/11/2014
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Wright, Erik Lewis, Kay, Erik, Shield, Robert
• Primary Examiner(s): Shaifer Harriman, Dant B
• Application Number:
  US15/893,005
• Time in Patent Office: 382 Days
• Field of Search: 726 6
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 9/32 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
• CPC Class Codes: H04L 9/3247 involving digital signatures

Abstract

In one general aspect, a method can include receiving, by an application running on a computing device, an indication that a user of the computing device has been authenticated, and receiving a selection of a settings page, the settings page associated with the application and the user. The method can further include requesting the settings page for display on a display device included in the computing device, and receiving the settings page including a value for a preference for a setting included on the settings page, the value for the preference being signed by a private key associated with the user. The method can further include validating, by the application, the value for the preference using a public key associated with the application, and based on the validation, displaying, by the display device, the settings page including an indication of the value of the preference for the setting.

Claims

1. A method, comprising:

receiving, by a server, at least one value of settings for an application on a device separate from the server, the application configured to accept only signed settings values from the server and having a settings menu with preferences for how the application operates, the value associated with an authenticated user of the application;

signing the received value by the server;

storing, by the server, the received value in a database, wherein the received value is associated with the application and with the authenticated user in the database;

after storing the received value in the database, receiving, by the server, a request for the received value from the application on the device, the request generated by the authenticated user; and

in response to receiving the request for the received value, retrieving, by the server, the received value from the database, and providing a signed settings value corresponding to the received value to the application on the device.

2. The method of claim 1, wherein the at least one value controls at least one of:

application appearance, application default settings, application access to data, or application access to services outside the device.

3. The method of claim 1, wherein the server includes a frontend of the application, the frontend providing the signed settings value corresponding to the received value to the application on the device.

4. The method of claim 3, further comprising performing, by the frontend, user authentication regarding the authenticated user.

5. The method of claim 3, further comprising providing, by the frontend, a settings menu to the application on the device.

6. The method of claim 1, wherein signing the received value by the server comprises signing the received value by the server using a private key associated with the authenticated user.

7. The method of claim 6, wherein the private key is stored in the database, the method further comprising accessing, by the server, the private key in the database before signing the received value.

8. The method of claim 1, wherein the application on the device includes a browser application on the device.

9. The method of claim 1, wherein signing the received value by the server comprises signing the received value by the server before storing the received value in the database.

10. The method of claim 9, wherein storing the received value in the database comprises storing the signed received value in the database, and storing a signature associated with the received value in the database.

11. The method of claim 1, wherein signing the received value by the server comprises signing the received value by the server after storing the received value in the database and before providing the signed settings value corresponding to the received value to the application on the device.

12. The method of claim 1, further comprising performing a synchronization of the at least one value.

13. The method of claim 12, wherein the synchronization is performed with at least one other application associated with the authenticated user.

14. The method of claim 1, wherein multiple values of the settings are stored in the database, the method further comprising monitoring, by the server, access by the authenticated user to the multiple values of the settings.

15. The method of claim 14, further comprising analyzing the monitored access to identify suspicious behavior.

16. A computer program product tangibly embodied in a non-transitory storage medium, the computer program product including instructions that when executed by a processor cause operations to be performed, the operations comprising:

receiving, by a server, at least one value of settings for an application on a device separate from the server, the application configured to accept only signed settings values from the server and having a settings menu with preferences for how the application operates, the value associated with an authenticated user of the application;

signing the received value by the server;

storing, by the server, the received value in a database, wherein the received value is associated with the application and with the authenticated user in the database;

after storing the received value in the database, receiving, by the server, a request for the received value from the application on the device, the request generated by the authenticated user; and

in response to receiving the request for the received value, retrieving, by the server, the received value from the database, and providing a signed settings value corresponding to the received value to the application on the device.

17. A system comprising:

at least one processor; and

a memory having stored therein instructions that when executed by the processor cause operations to be performed, the operations comprising;

receiving at least one value of settings for an application on a device, the application configured to accept only signed settings values from a server and having a settings menu with preferences for how the application operates, the value associated with an authenticated user of the application;

signing the received value;

storing the received value in a database, wherein the received value is associated with the application and with the authenticated user in the database;

after storing the received value in the database, receiving a request for the received value from the application on the device, the request generated by the authenticated user; and

in response to receiving the request for the received value, retrieving the received value from the database, and providing a signed settings value corresponding to the received value to the application on the device.

18. The system of claim 17, further comprising a frontend of the application, wherein the frontend is configured to provide the signed settings value corresponding to the received value to the application on the device.

19. The system of claim 17, wherein the frontend is configured to perform user authentication regarding the authenticated user.

20. The system of claim 17, wherein the frontend is configured to provide a settings menu to the application on the device.