Method, device and system for logging in through a browser application at a client terminal
View Patent ↗The current invention discloses methods, devices and systems for logging in a third party server through a browser application at a client terminal. After receiving a validation request from a third party server, the main server for the browser application may choose to grant or deny the request. The validation request, which may include a third party identifier, a user identifier, and a session key, can be triggered by a data access request from the browser application. If there is an active communication session between the client terminal and the server, the server may send an authorization request to the third party so that the third party server allows the client terminal to access non-sensitive data associated with the user identifier through the browser application without further validation of the data access request. The current invention provides additional convenience and security for third party login operations.
1. A method performed at a main server having one or more processors and memory storing programs executed by the one or more processors, wherein the main server is communicatively connected to a client terminal and a third party server, respectively:
receiving a validation request from the third party server, wherein the validation request is triggered by a data access request from a browser application at the client terminal to the third party server and the validation request comprises a third party identifier, a user identifier, and a session key;
determining whether there is an active communication session between the main server and the client terminal corresponding to the session key; and
in accordance with a determination that the communication session is an active session, sending an authorization request to the third party server based on the third party identifier, the authorization request including the session key, wherein the third party server is configured to allow the client terminal to access a predefined portion of data associated with the user identifier through the browser application without further validating the data access request and require further authentication by the main server from the client terminal when the browser application requests to access sensitive data outside the predefine portion in the third party server.
2. The method of claim 1 , wherein:
the data access request comprises the user identifier and the session key.
3. The method of claim 1 , wherein:
the sensitive data is related to private information of the user or completion of a financial transaction.
4. The method of claim 1 , wherein:
the further authentication comprises a login phrase and a password.
5. The method of claim 1 , wherein:
the third party server sends an authorization notice to the client terminal after receiving the authorization request.
6. The method of claim 5 , wherein:
the client terminal displays the authorization notice as a log in success status.
7. The method of claim 1 , wherein:
a login time period associated with the client terminal is used to determine whether there is an active communication session between the main server and the client terminal corresponding to the session key.
8. A main server that is communicatively connected to a client terminal and a third party server, respectively, the main server comprising:
one or more processors;
memory; and
one or more programs modules stored in the memory and configured for execution by the one or more processors, the one or more program modules including:
a receiving module configured to receive a validation request from the third party server, wherein the validation request is triggered by a data access request from a browser application at the client terminal to the third party server and the validation request comprises a third party identifier, a user identifier, and a session key;
a determination module configured to determine whether there is an active communication session between the main server and the client terminal corresponding to the session key; and
a sending module configured to send an authorization request to the third party server based on the third party identifier, in accordance with a determination that the communication session is an active session, the authorization request including the session key, wherein the third party server is configured to allow the client terminal to access a predefined portion of data associated with the user identifier through the browser application without further validating the data access request and require further authentication by the main server from the client terminal when the browser application requests to access sensitive data outside the predefine portion in the third party server.
9. The main server of claim 8 , wherein:
the data access request comprises the user identifier and the session key,
the third party server comprises a further authorization module configured to require further authentication by the main server from the client terminal when the browser application requests to access sensitive data outside the predefine portion in the third party server.
10. The main server of claim 8 , wherein:
the sensitive data is related to private information of the user or completion of a financial transaction.
11. The main server of claim 8 , wherein:
the further authentication comprises a login phrase and a password.
12. The main server of claim 8 , wherein:
the third party server comprises a authorization notice module configured to send an authorization notice to the client terminal after receiving the authorization request.
13. The main server of claim 12 , wherein:
the client terminal displays the authorization notice as a log in success status.
14. The main server of claim 8 , wherein:
a login time period associated with the client terminal is used to determine whether there is an active communication session between the main server and the client terminal corresponding to the session key.
15. A non-transitory computer readable storage medium having stored therein one or more instructions, which, when executed by a main server that is communicatively connected to a client terminal and a third party server, respectively, cause the main server to:
receive a validation request from the third party server, wherein the validation request is triggered by a data access request from a browser application at the client terminal to the third party server and the validation request comprises a third party identifier, a user identifier, and a session key;
determine whether there is an active communication session between the main server and the client terminal corresponding to the session key; and
in accordance with a determination that the communication session is an active session, send an authorization request to the third party server based on the third party identifier, the authorization request including the session key, wherein the third party server is configured to allow the client terminal to access a predefined portion of data associated with the user identifier through the browser application without further validating the data access request and require further authentication by the main server from the client terminal when the browser application requests to access sensitive data outside the predefine portion in the third party server.
16. The non-transitory computer readable storage medium of claim 15 , wherein:
the third party server sends an authorization notice to the client terminal after receiving the authorization request.
17. The non-transitory computer readable storage medium of claim 15 , wherein:
a login time period associated with the client terminal is used to determine whether there is an active communication session between the main server and the client terminal corresponding to the session key.