Methods and systems for controlling mobile terminal access to a third-party server
The present disclosure includes an exemplary method for controlling access to a third-party server by a mobile terminal. The method comprises: acquiring, at the mobile terminal from a first-party server, login authorization information using which a user of the mobile terminal has logged in the first-party server through a client-side application corresponding to the first-party server, wherein the login authorization information includes a logged-in account; transmitting, to the third-party server, a login request, wherein the login request includes the login authorization information that is to be verified; and receiving authorization for the user to log in the third-party server using the logged-in account included in the verified login authorization information.
1. A computer-implemented method for controlling access to a third-party server by a mobile terminal, the method comprising:
receiving, at the mobile terminal, a cross-site login request from a first client-side application that corresponds to the third-party server for logging into a first account associated with the third-party server via a second account associated with a first-party server;
transmitting a first set of parameters to a second client-side application that corresponds to the first-party server and that is currently running on the mobile terminal, wherein the first set of parameters includes an application identifier assigned to the first client-side application;
receiving login status information from the second client-side application, wherein the login status information includes the application identifier assigned to the first client-side application and a login status indicator that indicates whether the second account that corresponds to the second-party server is currently logged in;
transmitting, to the first-party server, a login authentication request, wherein the login authentication request includes the application identifier and the login status information; and
receiving authorization from the first-parity server for the user to log into the first account associated with the third-party server, wherein one or more account information items from the second account associated with the first-party server are available to the user for using in the first account in the first client-side application.
2. The method according to claim 1 , further comprising:
receiving, at the mobile terminal via a browser, the cross-site login request;
receiving, from the third-party server, a login page including at least one account-system login link for logging into the first account associated with the third-party server via the second account associated with a first-party server;
displaying, via the browser, the login page;
detecting that the user has clicked on the at least one account-system login link included in the login page and the browser supports cross-cite login; and
based on the detection, performing the transmitting the first set of parameters to the second client-side application.
3. The method according to claim 1 , further comprising:
in accordance with a determination that the application identifier and the login status information are verified by the first-parity server,
receiving an authorization page prompting the user to confirm authorizing the third-party server to use the one or more account information items from the second account associated with the first-party server for the user to log in the third-party server.
4. The method according to claim 3 , further comprising:
displaying, at the mobile terminal, the authorization page;
receiving the user's confirmed authorization for the third-party server to use the one or more account information items from the second account associated with the first-party server to log in the third-party server; and
transmitting the user's confirmed authorization to the first-party server;
wherein:
a user identifier and an authorization token are transmitted to the third-party server;
an acquiring request for the one or more account information items from the second account is transmitted to the first-party server, the acquiring request including the user identifier and the authorization token; and
the one or more account information items from the second account are transmitted to the third-party server after the user identifier and the authorization token are verified.
5. The method according to claim 1 , wherein:
the login status information comprises a timestamp, the login status information being valid within a pre-determined time frame before the timestamp expires; and
the login status information is associated with the application identifier.
6. The method according to claim 1 , wherein the first set of parameters comprise the application identifier, a scope of operations that require user authorization to perform by the mobile device, and a resource identifier for redirecting a webpage.
7. The method according to claim 1 , wherein the first set of parameters are encrypted.
8. A mobile device, comprising:
one or more processors; and
memory storing one or more programs for execution by the one or more processors, the one or more programs including instructions for:
receiving, at the mobile device, a cross-site login request from a first client-side application that corresponds to the third-party server for logging into a first account associated with the third-party server via a second account associated with a first-party server;
transmitting a first set of parameters to a second client-side application that corresponds to the first-party server and that is currently running on the mobile device, wherein the first set of parameters includes an application identifier assigned to the first client-side application;
receiving login status information from the second client-side application, wherein the login status information includes the application identifier assigned to the first client-side application and a login status indicator that indicates whether the second account that corresponds to the second-party server is currently logged in;
transmitting, to the first-party server, a login authentication request, wherein the login authentication request includes the application identifier and the login status information; and
receiving authorization from the first-parity server for the user to log into the first account associated with the third-party server, wherein one or more account information items from the second account associated with the first-party server are available to the user for using in the first account in the first client-side application.
9. The mobile device of claim 8 , wherein the one or more programs further include instructions for:
receiving, at the mobile device via a browser, the cross-site login request;
receiving, from the third-party server, a login page including at least one account-system login link for logging into the first account associated with the third-party server via the second account associated with a first-party server;
displaying, via the browser, the login page;
detecting that the user has clicked on the at least one account-system login link included in the login page and the browser supports cross-cite login; and
based on the detection, performing the transmitting the first set of parameters to the second client-side application.
10. The mobile device of claim 8 , wherein the one or more programs further include instructions for:
in accordance with a determination that the application identifier and the login status information are verified by the first-parity server, receiving an authorization page prompting the user to confirm authorizing the third-party server to use the one or more account information items from the second account associated with the first-party server for the user to log in the third-party server.
11. The mobile device of claim 10 , wherein the one or more programs further include instructions for:
displaying, at the mobile device, the authorization page;
receiving the user's confirmed authorization for the third-party server to use the one or more account information items from the second account associated with the first-party server to log in the third-party server; and
transmitting the user's confirmed authorization to the first-party server;
wherein:
a user identifier and an authorization token are transmitted to the third-party server;
an acquiring request for the one or more account information items from the second account is transmitted to the first-party server, the acquiring request including the user identifier and the authorization token; and
the one or more account information items from the second account are transmitted to the third-party server after the user identifier and the authorization token are verified.
12. The mobile device of claim 8 , wherein:
the login status information comprises a timestamp, the login status information being valid within a pre-determined time frame before the timestamp expires; and
the login status information is associated with the application identifier.
13. The mobile device of claim 8 , wherein the first set of parameters comprise the application identifier, a scope of operations that require user authorization to perform by the mobile device, and a resource identifier for redirecting a webpage.
14. The mobile device of claim 8 , wherein the first set of parameters are encrypted.
15. A non-transitory computer-readable storage medium having instructions stored thereon, the instructions, when executed by one or more processors of a mobile device, cause the processors to perform operations comprising:
receiving, at a mobile device, a cross-site login request from a first client-side application that corresponds to the third-party server for logging into a first account associated with the third-party server via a second account associated with a first-party server;
transmitting a first set of parameters to a second client-side application that corresponds to the first-party server and that is currently running on the mobile device, wherein the first set of parameters includes an application identifier assigned to the first client-side application;
receiving login status information from the second client-side application, wherein the login status information includes the application identifier assigned to the first client-side application and a login status indicator that indicates whether the second account that corresponds to the second-party server is currently logged in;
transmitting, to the first-party server, a login authentication request, wherein the login authentication request includes the application identifier and the login status information; and
receiving authorization from the first-parity server for the user to log into the first account associated with the third-party server, wherein one or more account information items from the second account associated with the first-party server are available to the user for using in the first account in the first client-side application.
16. The non-transitory computer-readable storage medium of claim 15 , wherein the instructions further cause the processors to perform operations comprising:
receiving, at the mobile device via a browser, the cross-site login request;
receiving, from the third-party server, a login page including at least one account-system login link for logging into the first account associated with the third-party server via the second account associated with a first-party server;
displaying, via the browser, the login page;
detecting that the user has clicked on the at least one account-system login link included in the login page and the browser supports cross-cite login; and
based on the detection, performing the transmitting the first set of parameters to the second client-side application.
17. The non-transitory computer-readable storage medium of claim 15 , wherein the instructions further cause the processors to perform operations comprising:
in accordance with a determination that the application identifier and the login status information are verified by the first-parity server, receiving an authorization page prompting the user to confirm authorizing the third-party server to use the one or more account information items from the second account associated with the first-party server for the user to log in the third-party server.
18. The non-transitory computer-readable storage medium of claim 17 , wherein the instructions further cause the processors to perform operations comprising:
displaying the authorization page;
receiving the user's confirmed authorization for the third-party server to use the one or more account information items from the second account associated with the first-party server to log in the third-party server; and
transmitting the user's confirmed authorization to the first-party server;
wherein:
a user identifier and an authorization token are transmitted to the third-party server;
an acquiring request for the one or more account information items from the second account is transmitted to the first-party server, the acquiring request including the user identifier and the authorization token; and
the one or more account information items from the second account are transmitted to the third-party server after the user identifier and the authorization token are verified.
19. The non-transitory computer-readable storage medium of claim 15 , wherein:
the login status information comprises a timestamp, the login status information being valid within a pre-determined time frame before the timestamp expires; and
the login status information is associated with the application identifier.
20. The non-transitory computer-readable storage medium of claim 15 , wherein the first set of parameters comprise the application identifier, a scope of operations that require user authorization to perform by the mobile device, and a resource identifier for redirecting a webpage.