Systems and methods for login and authorization

• US 10,462,118 B2
• Filed: 12/18/2017
• Issued: 10/29/2019
• Est. Priority Date: 06/25/2013
• Status: Active Grant

• Current Assignee: Tencent Technology Company Limited (Tencent Holdings Limited)
• Original Assignee: Tencent Technology Company Limited (Tencent Holdings Limited)
• Inventors: Ren, Min
• Primary Examiner(s): Lwin, Maung T
• Assistant Examiner(s): Debnath, Suman
• Application Number:
  US15/845,822
• Publication Number:
  US 20180109509A1
• Time in Patent Office: 680 Days
• 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/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/77 Graphical identity

Abstract

Systems and methods are provided for login and authorization. For example, a third-party terminal receives a login request from a user and sends an authorization request from the third-party terminal to a network server; the network server generates first two-dimensional-barcode information and sends the first two-dimensional-barcode information to the third-party terminal; the third-party terminal displays a first two-dimensional-barcode image; a mobile terminal extracts the first two-dimensional-barcode information from the first two-dimensional-barcode image and sends first user account information and the first two-dimensional-barcode information to the network server; the network server validates the first user account information and the first two-dimensional-barcode information based on at least information associated with stored second user account information and second two-dimensional-barcode information generated by the network server.

Claims

1. A method for login and authorization, the method comprising:

receiving, at a third-party terminal executing a first third-party application, a login request from a user;

in response to the login request, sending an authorization request from the third-party terminal to a network server to trigger the network server to generate first two-dimensional-barcode information, wherein the authorization request includes authorization parameters to be validated by the network server, and the authorization parameters include an application identifier, authorization scope information indicating allowed types of operations associated with a user account to be performed after a third-party server corresponding to the first third-party application receives validation from the network server, an application callback address indicating an address at which the third-party terminal receives login state information, anti-disguise information and an application key;

generating, by the network server, the first two-dimensional-barcode information according to the authorization request;

sending the first two-dimensional-barcode information to the third-party terminal;

displaying, at the third-party terminal, a first two-dimensional-barcode image;

extracting, by a mobile terminal, the first two-dimensional-barcode information from the first two-dimensional-barcode image;

sending, by the mobile terminal, first user account information and the first two-dimensional-barcode information to the network server;

validating, by the network server, the first user account information and the first two-dimensional-barcode information based on at least information associated with stored second user account information and second two-dimensional-barcode information generated by the network server;

in response to the first user account information and the first two-dimensional-barcode information being validated, sending, by the network server, an authorization and a predetermined user identifier to the third-party server;

setting, by the third-party server, the user account associated with the user identifier to a logged-in state;

acquiring, by the third-party terminal, information related to the logged-in state from the third-party server; and

setting an interface of the first third-party application to a user-logged-in state.

2. The method of claim 1, wherein:

the method further comprises;

validating, by the network server, the authorization parameters in the authorization request.

3. The method of claim 2, wherein the first two-dimensional-barcode information includes the authorization parameters.

4. The method of claim 1, further comprising:

sending, by the third-party terminal, at a predetermined time an authorization inquiry to the third-party server.

5. The method of claim 1, wherein the in response to the first user account information and the first two-dimensional-barcode information being validated, sending, by the network server, an authorization and a predetermined user identifier to a third-party server includes:

in response to the first user account information and the first two-dimensional-barcode information being validated, sending, by the network server, validation-success information to the mobile terminal;

displaying, by the mobile terminal, information related to authorization confirmation;

receiving, by the mobile terminal, an authorization confirmation from the user;

sending the authorization confirmation to the network server; and

sending, by the network server, the authorization and the predetermined user identifier to the third-party server.

6. The method of claim 5, wherein the information related to authorization confirmation includes a name and an authorization scope of the first third-party application.

7. The method of claim 1, wherein:

the user identifier corresponds to the user account; and

the user account corresponds to different user identifiers when the user account logs into different third-party applications.

8. The method of claim 1, further comprising:

validating, by the third-party server, the authorization.

9. The method of claim 8, wherein the authorization includes an authorization-validity character string and the anti-disguise information.

10. The method according to claim 1, wherein:

the allowed types of operations associated with the user account indicated by the authorization scope information comprises at least one of;

using a headshot associated with the user account, using a nickname associated with the user account, and post a microblog message on behalf of the user account.

11. The method according to claim 1, further comprising:

inquiring, by the third-party terminal, at predetermined times to the third-party server about the login state information of the user account;

receiving, by the third-party terminal, the login state information of the user account at the application callback address; and

updating and presenting, by the third-party terminal, the received login state information.

12. A third-party terminal comprising:

a computer-readable storage medium; and

one or more data processors configured to;

receive, at a third-party application, a login request from a user;

in response to the login request, send an authorization request to a network server to trigger the network server to generate first two-dimensional-barcode information, wherein the authorization request includes authorization parameters to be validated by the network server, and the authorization parameters include an application identifier, authorization scope information indicating allowed types of operations associated with a user account to be performed after a third-party server corresponding to the third-party application receives validation from the network server, an application callback address indicating an address at which the third-party terminal receives login state information, anti-disguise information and an application key;

receive the two-dimensional-barcode information from the network server according to the authorization request;

display a two-dimensional-barcode image;

receive information related to a logged-in state of the user account from the third-party server;

set an interface of a third-party application to a user-logged-in state based on at least information associated with the information related to the logged-in state of the user account;

wherein the third-party server sets the user account to the logged-in state and sends the information related to the logged-in state of the user account after the network server validates user account information sent from a mobile terminal and the two-dimensional-barcode information extracted from the first two-dimensional-barcode image.

13. The third-party terminal of claim 12, wherein the two-dimensional-barcode information includes the authorization parameters.

14. The third-party terminal of claim 12, wherein the one or more data processors are further configured to send at a predetermined time an authorization inquiry to the third-party server.

15. A non-transitory computer readable storage medium comprising programming instructions for login, the programming instructions configured to cause one or more data processors to execute operations comprising:

receiving, at a third-party application, a login request from a user;

in response to the login request, sending an authorization request to a network server to trigger the network server to generate first two-dimensional-barcode information, wherein the authorization request includes authorization parameters to be validated by the network server, and the authorization parameters include an application identifier, authorization scope information indicating allowed types of operations associated with a user account to be performed after a third-party server corresponding to the third-party application receives validation from the network server, an application callback address indicating an address at which the third-party terminal receives login state information, anti-disguise information and an application key;

receiving the two-dimensional-barcode information from the network server, the two-dimensional-barcode information being generated by the network server according to the authorization request;

displaying a two-dimensional-barcode image;

acquiring information related to a logged-in state of the user account from the third-party server; and

setting an interface of the third-party application to a user-logged-in state;

wherein the third-party server sets the user account to the logged-in state and sends the information related to the logged-in state of the user account after the network server validates user account information sent from a mobile terminal and the two-dimensional-barcode information extracted from the first two-dimensional-barcode image.

16. The storage medium of claim 15, wherein the first two-dimensional-barcode information includes the authorization parameters.

17. The storage medium of claim 15, wherein the programming instructions are further configured to cause one or more data processors to execute:

sending, at a predetermined time, an authorization inquiry to the third-party server.

18. A non-transitory computer readable storage medium comprising programming instructions for authorization, the programming instructions configured to cause one or more data processors to execute operations comprising:

receiving an authorization request from a third-party terminal executing a first third-party application, to trigger the one or more data processors to generate first two-dimensional-barcode information, wherein the authorization request includes authorization parameters to be validated by the network server, and the authorization parameters include an application identifier, authorization scope information indicating allowed types of operations associated with a user account to be performed after a third-party server corresponding to the first third-party application receives validation from the network server, an application callback address indicating an address at which the third-party terminal receives login state information, anti-disguise information and an application key;

generating the first two-dimensional-barcode information according to the authorization request;

sending the first two-dimensional-barcode information to the third-party terminal so that the third-party terminal displays a first two-dimensional-barcode image;

validating first user account information and the first two-dimensional-barcode information sent from a mobile terminal based on at least information associated with stored second user account information and second two-dimensional-barcode information, wherein the first two-dimensional-barcode information sent from the mobile terminal is extracted by the mobile terminal from the first two-dimensional-barcode image displayed on the third-party terminal; and

in response to the first user account information and the first two-dimensional-barcode information being validated, sending an authorization and a predetermined user identifier to the third-party server.

19. The storage medium of claim 18, wherein the in response to the first user account information and the first two-dimensional-barcode information being validated, sending, by the network server, an authorization and a predetermined user identifier to a third-party server includes:

in response to the first user account information and the first two-dimensional-barcode information being validated, sending validation-success information to the mobile terminal, so that the mobile terminal displays information related to authorization confirmation and obtains an authorization confirmation from the user;

receiving the authorization confirmation from the mobile terminal; and

when receiving the authorization confirmation, sending the authorization and the predetermined user identifier to the third-party server.

20. The storage medium of claim 19, wherein the information related to authorization confirmation includes a name and an authorization scope of a third-party application.

21. The storage medium of claim 18, wherein:

the predetermined user identifier corresponds to a user account; and

the user account corresponds to different user identifiers when the user account logs into different third-party applications.