CN111131208B

CN111131208B - Third-party service application login method and device, computer equipment and storage medium

Info

Publication number: CN111131208B
Application number: CN201911285841.0A
Authority: CN
Inventors: 刘舟; 郭文杰; 李奕臻; 谢林廷
Original assignee: Guangzhou Jisheng Network Technology Co ltd
Current assignee: Guangzhou Jisheng Network Technology Co ltd
Priority date: 2019-12-13
Filing date: 2019-12-13
Publication date: 2022-03-25
Anticipated expiration: 2039-12-13
Also published as: CN111131208A

Abstract

The application relates to a third-party service application login method, a third-party service application login device, computer equipment and a storage medium. The method comprises the following steps: loading a target third-party service application in an interface of the unified login platform; when detecting the preset trigger operation of the target third-party service application, recording application pre-login information; when the current login user is determined to have the login right of the target third-party service application, generating a first login check code corresponding to the target third-party service application; sending login indication information to the target third-party service application, wherein the login indication information carries a first login check code; acquiring an application login request sent by a target third-party service application, wherein the application login request carries a second login check code and application login information; and determining the login state of the target third-party service application according to the first login check code, the second login check code, the application pre-login information and the application login information. By adopting the method, the convenience of the third-party service application login operation can be improved.

Description

Third-party service application login method and device, computer equipment and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a third-party service application login method, apparatus, computer device, and storage medium.

Background

With the rapid development of computer technology, a large number of network service providers are brought, but some services of many network service providers require users to log in before being authorized to obtain. At present, more and more websites and mobile applications support third-party service application login operation, and when a user can access a certain website or application supporting third-party service application login through a mobile terminal such as a mobile phone, the user needs to input a third-party account and a password to log in different third-party service application logins to realize the operation of logging in the website or application, so that the third-party service application login operation is poor in convenience.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a third-party service application login method, an apparatus, a computer device, and a storage medium, which can improve convenience of a third-party service application login operation.

A third party service application login method comprises the following steps:

loading a target third-party service application corresponding to a current login user of the unified login platform in an interface of the unified login platform;

when detecting the preset trigger operation of the target third-party service application, recording application pre-login information;

when the current login user is determined to have the login right of the target third-party service application, generating a first login check code corresponding to the target third-party service application;

sending login indication information to the target third-party service application, wherein the login indication information carries a first login check code;

acquiring an application login request sent by a target third-party service application, wherein the application login request carries a second login check code and application login information;

and determining the login state of the target third-party service application according to the first login check code, the second login check code, the application pre-login information and the application login information.

In one embodiment, loading a target third-party service application corresponding to a current login user of a unified login platform in an interface of the unified login platform includes: acquiring a current user login request, wherein the current user login request carries a current user identifier corresponding to a current login user; logging in the unified login platform according to the current user login request, and acquiring a target third-party service application corresponding to the current user identifier; and loading the target third-party service application in an interface of the unified login platform.

In one embodiment, acquiring a target third-party service application corresponding to a current user identifier includes: acquiring a preset service application mapping list, wherein the preset service application mapping list comprises a mapping relation between an initial user identifier and a corresponding third-party service application; acquiring a target third-party service application corresponding to the current user identifier according to the mapping relation;

preferably, loading the target third-party service application in the interface of the unified login platform includes: acquiring a front-end code corresponding to a target third-party service application; and acquiring a preset access code corresponding to the target third-party service application, writing the preset access code into the front-end code, and loading the target third-party service application in an interface of the unified login platform.

In one embodiment, when determining that the current login user has the login right of the target third-party service application, the method includes: acquiring target user account information corresponding to the target third-party service application, wherein the target user account information has the authority of logging in the target third-party service application; acquiring current user account information corresponding to a current login user; and when the current user account information is matched with the target user account information, determining that the current login user has the login authority of the target third-party service application.

In one embodiment, sending login indication information to a target third party service application, where the login indication information carries a first login check code, includes: and sending login indication information to the target third-party service application through a Post Message mechanism by using the application pre-login information and the first login check code, and informing the target third-party service application of actively initiating login.

In one embodiment, determining the login state of the target third-party service application according to the first login check code, the second login check code, the application pre-login information and the application login information includes: when the first login check code is matched with the second login check code and the application pre-login information is matched with the application login information, determining that the login state of the target third-party service application is successful in login; or when the first login check code is not matched with the second login check code or the application pre-login information is not matched with the application login information, determining that the login state of the target third-party service application is login failure; or when the first login check code is not matched with the second login check code and the application pre-login information is not matched with the application login information, determining that the login state of the target third-party service application is login failure.

In one embodiment, the third-party service application login method further includes: recording a login state corresponding to the target third-party service application and application user login information corresponding to the target third-party service application; establishing an incidence relation between a service application identifier and a login state corresponding to a target third-party service application and login information of an application user; and storing the incidence relation, wherein the incidence relation is used for tracing the login condition of the third-party service application.

A third party service application login device, the device comprising:

the third-party service application loading module is used for loading a target third-party service application corresponding to a current login user of the unified login platform in an interface of the unified login platform;

the third-party service application detection module is used for recording application pre-login information when detecting the preset trigger operation of the target third-party service application;

the login check code generation module is used for generating a first login check code corresponding to the target third-party service application when the current login user is determined to have the login right of the target third-party service application;

the login indication information sending module is used for sending login indication information to the target third-party service application, and the login indication information carries a first login check code;

the application login request acquisition module is used for acquiring an application login request sent by the target third-party service application, wherein the application login request carries a second login check code and application login information;

and the login state determining module is used for determining the login state of the target third-party service application according to the first login check code, the second login check code, the application pre-login information and the application login information.

A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:

A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:

The third-party service application login method, the device, the computer equipment and the storage medium load the target third-party service application corresponding to the current login user of the unified login platform in the interface of the unified login platform, record the application pre-login information once the preset trigger operation of the target third-party service application is detected, generate the first login check code corresponding to the target third-party service application when the current login user is determined to have the login right of the target third-party service application, further send the login indication information to the target third-party service application, the login indication information carries the first login check code, obtain the application login request sent by the target third-party service application, the application login request carries the second login check code and the application login information, and determine the login state of the target third-party service application according to the first login check code, the second login check code, the application pre-login information and the application login information, the user account and the user password corresponding to the target third-party service application do not need to be input again to realize the login of the target third-party service application, and the convenience of the third-party service application operation is improved.

Drawings

FIG. 1 is a diagram of an application environment for a third party service application login method in one embodiment;

FIG. 2 is a flowchart illustrating a third party service application login method according to an embodiment;

FIG. 3 is a flowchart illustrating the target third party service application loading step in one embodiment;

FIG. 4 is a flowchart illustrating the steps of obtaining a target third party service application in one embodiment;

FIG. 5 is a flowchart illustrating the steps of loading the target third-party service application in another embodiment;

FIG. 6 is a flowchart illustrating the login permission determination step of the current login user in one embodiment;

FIG. 7 is a flowchart illustrating the login status determination step of the target third-party business application in one embodiment;

FIG. 8 is a flowchart illustrating a third party service application login method according to another embodiment;

FIG. 9 is a block diagram of a third party service application login device in one embodiment;

FIG. 10 is a diagram showing an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

The third-party service application login method provided by the application can be applied to the application environment shown in fig. 1. Wherein the terminal 102 communicates with the server 104 via a network. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented by an independent server or a server cluster formed by a plurality of servers. The terminal 102 is provided with a unified login platform, where the unified login platform is a platform for the third-party service application to access and implement automatic login.

Specifically, a terminal user may load a target third-party service application corresponding to a current login user of the unified login platform in an interface of the unified login platform installed on the terminal 102; when detecting the preset trigger operation of the target third-party service application, recording application pre-login information; when the current login user is determined to have the login right of the target third-party service application, generating a first login check code corresponding to the target third-party service application; sending login indication information to the target third-party service application, wherein the login indication information carries a first login check code; acquiring an application login request sent by a target third-party service application, wherein the application login request carries a second login check code and application login information; and determining the login state of the target third-party service application according to the first login check code, the second login check code, the application pre-login information and the application login information. Further, the terminal 102 may return the login status of the target third-party service application to the server 104, informing the server 104.

In an embodiment, as shown in fig. 2, a third party service application login method is provided, which is described by taking the method as an example of being applied to the terminal in fig. 1, and includes the following steps:

step 202, loading a target third party service application corresponding to a current login user of the unified login platform in an interface of the unified login platform.

The terminal is provided with a unified login platform, the unified login platform is a platform which can be accessed by a third-party service application and can realize automatic login, and the platform can be used as an execution main body of the application. The current login user refers to a user who is currently logging in the unified login platform, a user login button is arranged on the unified login platform, and the current login user can generate a current user login request by operating the user login button arranged on the unified login platform. The operation includes but is not limited to click operation, voice operation, or setting a timing event, and the user login request is generated by the triggering of the timing event.

The current user login request generated by operating and triggering a user login button set by the platform carries a current user identifier and corresponding current user account information, wherein the current user identifier is used for uniquely identifying the current login user, and the current user account information is account information related to the current login user, and includes but is not limited to a current login user name, a current login user password and the like.

The target third-party service application refers to a third-party service application corresponding to a login request of a current user, that is, a third-party service application for which the current login user has login authority. The third-party business application is a business application provided by a provider different from the unified login platform, namely a business application which is provided by a professional service provider independently and provides a series of professional services for the client of the unified login platform in the role of a third party.

The authority relationship between the login user and the corresponding third-party service application can be pre-established, and once the login request corresponding to the current login user is obtained, the corresponding third-party service application, namely the target third-party service application, can be obtained according to the current user identifier in the login request of the current login user. The pre-establishing of the authority relationship between the login user and the corresponding third-party service application may specifically be that the corresponding login user may be pre-set during development of the third-party service application, or the user registers corresponding user account information on an independent setting interface of each third-party service application in advance to establish the authority relationship between the user account information and the corresponding third-party service application.

Specifically, a user login request is generated by triggering a unified login platform installed on a terminal, specifically, a login account and a login password corresponding to a current login user can be input in a user login interface provided on the platform, corresponding current login user account information is formed by the login account and the login password of the current login user, the current login user account information and a current login user identifier are logged in through the login request of the current login user, once the login request of the current login user is obtained, a corresponding target third-party service application is obtained according to the current login user account information in the login request in a matching manner, and finally, the target third-party service application corresponding to the current login user of the unified login platform is loaded in the interface of the unified login platform.

And 204, recording the application pre-login information when the preset trigger operation of the target third-party service application is detected.

The preset triggering operation is an operation which is set in advance to trigger the target third-party service application, and may be a click operation, a voice operation or a set timing event, where setting the timing event specifically may be to operate the target third-party service application through the timing event to implement login of the target third-party service application. The click operation may specifically be to click on the target third-party service application to realize the login of the target third-party service application, and the voice operation may specifically be to perform voice control on the target third-party application to realize the login of the target third-party service application.

The application pre-login information refers to related login information generated by realizing login of the target third-party service application through preset triggering operation, and the application pre-login information includes, but is not limited to, a target third-party service application identifier, a target third-party service application name, target third-party service application user login information, target third-party service application login time and the like. Specifically, when a preset trigger operation of the target third-party service application is detected, all application pre-login information of the target third-party service application is recorded and stored.

And step 206, when the current login user is determined to have the login right of the target third-party service application, generating a first login check code corresponding to the target third-party service application.

After the preset trigger operation of the target third-party service application is detected, in order to improve the login security of the target third-party service application, the login authority of the current login user needs to be detected. Specifically, target user account information corresponding to the target third-party service application is acquired, the target user account information has a right to log in the target third-party service application, current user account information corresponding to a current login user is acquired, whether the current user account information is matched with the target user account information is detected, and if the current user account information is matched with the target user account information, it is indicated that the current user account information has the login right of the target third-party service application, and it can be determined that the current login user has the login right of the target third-party service application.

Otherwise, if the current user account information is not matched with the target user account information, the current user account information does not have the login authority of the target third-party service application, and the login of the target third-party service application is refused.

Further, after the current login user is determined to have the login authority of the target third-party service application, a first login check code corresponding to the target third-party service application is generated. The first login check code is used for checking the correctness of login of the target third-party service application through preset triggering operation, and is unique and cannot be tampered.

And 208, sending login indication information to the target third-party service application, wherein the login indication information carries the first login check code.

The login indication information is used for informing the target third-party service application to actively initiate login, and the login indication information carries a first login check code. Specifically, after the first login check code corresponding to the target third-party service application is generated and obtained, login indication information can be sent to the target third-party service application to inform the target third-party service application to actively initiate login. Specifically, the Post Message mechanism may be used to send the login instruction information to the target third-party service application. The Post Message mechanism can realize the communication mechanism between the target third-party service application and the unified login platform.

Further, after the target third-party service application is notified to initiate login, once the target third-party service application receives the notification, an application login request of the target third-party service application is automatically triggered and generated, and the request is sent to the unified login platform.

Step 210, obtaining an application login request sent by the target third-party service application, where the application login request carries the second login check code and the application login information.

Specifically, after receiving login indication information sent by the unified login platform, the target third-party service application automatically initiates login to the unified login platform according to the login indication information without any operation. The target third-party service application sends an application login request to the unified login platform, wherein the application login request carries a second login check code and application login information, the second login check code is used for checking the correctness of login automatically initiated by the target third-party service application, and the second check code is unique and cannot be tampered.

The application login information is related login information for the target third-party service application to automatically initiate login at this time, and includes a target third-party service application identifier, a target third-party service application name, target third-party service application user login information, target third-party service application login time and the like.

And 212, determining the login state of the target third-party service application according to the first login check code, the second login check code, the application pre-login information and the application login information.

Specifically, after the first login check code, the second login check code, the application pre-login information and the application login information are obtained, the login state of the target third-party service application can be determined according to the first login check code, the second login check code, the application pre-login information and the application login information. The login state comprises login success and login failure, and different login states are determined in different modes. The login state of the target third-party service application can be determined by checking a first matching degree between the first login check code and the second login check code and a second matching degree between the application pre-login information and the application login information.

Otherwise, when the first login check code is not matched with the second login check code or the application pre-login information is not matched with the application login information, the login state of the target third-party service application is determined to be login failure, or when the first login check code is not matched with the second login check code and the application pre-login information is not matched with the application login information, the login state of the target third-party service application is determined to be login failure.

In the third-party service application login method, a target third-party service application corresponding to a current login user of a unified login platform is loaded in an interface of the unified login platform, application pre-login information is recorded once preset trigger operation of the target third-party service application is detected, when the current login user is determined to have login authority of the target third-party service application, a first login check code corresponding to the target third-party service application is generated, login indication information is further sent to the target third-party service application, the login indication information carries a first login check code, an application login request sent by the target third-party service application is obtained, the application login request carries a second login check code and application login information, and the login state of the target third-party service application is determined according to the first login check code, the second login check code, the application pre-login information and the application login information, the user account and the user password corresponding to the target third-party service application do not need to be input again to realize the login of the target third-party service application, and the convenience of the third-party service application operation is improved.

In one embodiment, as shown in fig. 3, loading a target third party service application corresponding to a current login user of the unified login platform in an interface of the unified login platform includes:

step 302, a current user login request is obtained, wherein the current user login request carries a current user identifier corresponding to a current login user.

The terminal is provided with a uniform login platform, wherein the uniform login platform is a platform which can be accessed by a third-party service application and can realize automatic login. The current user login request is generated by triggering a current login user who is logging in a platform, the current user login request is a request for logging in the platform, a user login button can be arranged on the platform, and the current user login request can be generated by operating the user login button arranged on the platform. The operation includes but is not limited to click operation, voice operation, or setting a timing event, and the user login request is generated by the triggering of the timing event.

The current user login request carries a current user identifier and corresponding current user account information, the current user identifier is used for uniquely identifying the current login user, and the current user account information is account information related to the current login user, and includes but is not limited to a current login user name, a current login user password and the like.

And 304, logging in the unified login platform according to the login request of the current user, and acquiring the target third-party service application corresponding to the current user identifier.

Specifically, after the current user login request is obtained, the unified login platform is logged in according to the current user login request, and after the unified login platform is successfully logged in, the target third-party service application corresponding to the current user identifier can be obtained. The target third-party service application refers to a third-party service application corresponding to the user login request, that is, a third-party service application for which the login user corresponding to the user login request has login authority. The third-party service application is a service application provided by a provider different from the platform, namely a service application which is provided by a professional service provider independently and provides a series of professional services for a platform client in the role of a third party.

The authority relationship between the login user and the corresponding third-party service application can be pre-established, and once the current user login request is obtained, the corresponding third-party service application, namely the target third-party service application, can be obtained according to the current user identifier in the current user login request. The pre-establishing of the authority relationship between the login user and the corresponding third-party service application may specifically be that the corresponding login user may be pre-set during development of the third-party service application, or the user registers corresponding user account information on an independent setting interface of each third-party service application in advance to establish the authority relationship between the user account information and the corresponding third-party service application.

Specifically, a user login request is generated by triggering through a unified login platform installed on a terminal, specifically, a current user login account and a corresponding current user login password can be input through a user login interface provided on the platform, corresponding current user account information is formed by the current user login account and the current user login password, the current user account information and the current user login request are logged in, and once the current user login request is obtained, a corresponding target third-party service application is obtained according to matching of the current user account information in the current user login request.

And step 306, loading the target third-party service application in the interface of the unified login platform.

After the target third-party service application corresponding to the current user identifier is obtained, the target third-party service application is loaded on the platform for the terminal user to check. Specifically, the step of loading the target third-party service application on the unified login platform may be to acquire a front-end code corresponding to the target third-party service application, acquire a corresponding preset access code, and write the preset access code into the front-end code, so that the target third-party service application can be loaded on the platform. The preset access code is determined according to a service requirement, and may be < iframe src ═ xxxxx "/>.

In one embodiment, as shown in fig. 4, acquiring a target third party service application corresponding to a current user identifier includes:

step 402, obtaining a preset service application mapping list, where the preset service application mapping list includes a mapping relationship between an initial user identifier and a corresponding third-party service application.

And step 404, acquiring a target third-party service application corresponding to the current user identifier according to the mapping relation.

The preset service application mapping list is a list which is set in advance and is used for reflecting the relationship between the third-party service application and the user identification, and the preset service application mapping list comprises the mapping relationship between each initial user identification and the corresponding third-party service application. The initial user identifier and the corresponding third-party service application may be in a one-to-one correspondence relationship, or may be in a one-to-many relationship, which may be specifically determined according to a service requirement or an actual application scenario.

The preset service application mapping list may specifically be that a mapping relationship between the initial user identifier and the corresponding third-party service application is established in advance according to an actual service requirement, an actual application scenario, or an actual product requirement, and the established mapping relationship is stored for subsequent use.

Specifically, a stored preset service application mapping list is obtained, and a target third-party service application corresponding to a current user identifier in a user login request is obtained according to a mapping relation in the preset service application mapping list. Specifically, an initial user identifier matched with a current user identifier in the user login request is obtained, and a third-party service application corresponding to the initial user identifier is used as a target third-party service application.

In one embodiment, as shown in fig. 5, loading a target third party service application in an interface of a unified login platform includes:

step 502, a front-end code corresponding to the target third-party service application is obtained.

And 504, acquiring a preset access code corresponding to the target third-party service application, writing the preset access code into a front-end code, and loading the target third-party service application in an interface of the unified login platform.

The front-end code refers to a source code used by a front end to render a target third-party service application, and when each third-party service application is displayed at the front end, the corresponding front-end code exists. Therefore, the front-end code corresponding to the target third-party service application is obtained, the preset access code corresponding to the target third-party service application is obtained, and the preset access code is written into the front-end code, so that the loading of the target third-party service application is realized. The preset access code is determined according to a service requirement, and may be < iframe src ═ xxxxx "/>.

Specifically, a front-end code corresponding to the target third-party service application is acquired, and meanwhile, a preset access code corresponding to the target third-party service application, for example, < iframe src ═ xxxxx "/>, is acquired, and the preset access code is written into the front-end code, so that the third-party service application corresponding to the unified login platform can be loaded.

In one embodiment, as shown in fig. 6, when determining that the current login user has the login right of the target third-party service application, the method includes:

step 602, obtaining target user account information corresponding to the target third party service application, where the target user account information has a right to log in the target third party service application.

Step 604, current user account information corresponding to the current login user is obtained.

Step 606, when the current user account information matches the target user account information, it is determined that the current login user has the login authority of the target third party service application.

After the preset trigger operation of the target third-party service application is detected, the authority of the current login user can be verified in order to improve the login safety of the target third-party service application. Specifically, whether the current user account information corresponding to the current login user has the login authority is checked, and when the current user account information is checked to have the login authority, it is indicated that the current login user corresponding to the current user account information has the authority to login the target third-party service application.

Wherein, the specific step of checking whether the current user account information corresponding to the current login user has login authority can be that the target user account information corresponding to the target third-party service application is obtained, the target user account information is the login user account information corresponding to the target third-party service application which can be logged in, the login authority for logging in the target third-party service application is provided, then the current user account information corresponding to the current login user is obtained, the current user account information is matched with the target user account information, when the matching is successful, the current user account information is proved to have the login authority, i.e., it is determined that the currently logged-in user has the login rights of the target third-party service application, whereas, when the matching is unsuccessful, and if the current user account information does not have the login authority, the current login user is refused to login the target third-party service application.

In one embodiment, sending login indication information to a target third party service application, where the login indication information carries a first login check code, includes: and sending login indication information to the target third-party service application through a Post Message mechanism by using the application pre-login information and the first login check code, and informing the target third-party service application of actively initiating login. Specifically, after the first login check code corresponding to the target third-party service application, the target third-party service application may be notified to initiate login according to the first login check code, specifically, login instruction information is sent to the target third-party service application by using a Post Message mechanism, the target third-party service application is notified to initiate login, and the login instruction information is used for notifying the target third-party service application to initiate login. The Post Message mechanism can realize the communication mechanism between the target third-party service application and the unified login platform.

After the unified login platform establishes communication with the target third-party service application by using a Post Message mechanism, and after the first login check code is obtained, the unified login platform can inform the target third-party service application of the application pre-login information and the first login check code through the Post Message mechanism and tell the target third-party service application that formal login can be actively initiated. Further, after receiving the notification of initiating the formal login, the target third-party service application automatically logs in, and sends a second login check code and application login information to the unified login platform, where the application login information is related login information of the target third-party service application automatically logging in this time, and includes but is not limited to a target third-party service application identifier, a target third-party service application name, a target third-party service application login ID, and the like, and the second login check code is used to verify the correctness of the target third-party service application automatically logging in this time.

In one embodiment, as shown in fig. 7, determining the login status of the target third-party service application according to the first login check code, the second login check code, the application pre-login information, and the application login information includes:

step 702, when the first login check code and the second login check code are matched and the application pre-login information is matched with the application login information, determining that the login state of the target third-party service application is successful in login.

Specifically, the login state of the target third-party service application may be determined according to the first login check code, the second login check code, the application pre-login information and the application login information, and the login state of the target third-party service application may be determined by checking a first matching degree between the first login check code and the second login check code and a second matching degree between the application pre-login information and the application login information.

When the first login check code is the same as the second login check code, and the application pre-login information is the same as the application login information, it is indicated that the first login of the target third-party service application realized through the preset trigger operation is the same as the login information of the subsequent automatic login initiated through the target third-party service application, and the login state of the target third-party service application can be determined to be successful login.

Step 704, when the first login check code is not matched with the second login check code or the application pre-login information is not matched with the application login information, determining that the login state of the target third-party service application is login failure.

Step 706, when the first login check code and the second login check code are not matched and the application pre-login information and the application login information are not matched, determining that the login state of the target third-party service application is login failure.

Specifically, when the first login check code is different from the second login check code, or the application pre-login information is different from the application login information, it indicates that the first login of the target third-party service application realized by the preset trigger operation is different from the login information of the subsequent automatic login initiated by the target third-party service application, and it is determined that the login state of the target third-party service application is login failure.

And when the first login check code is different from the second login check code and the application pre-login information is different from the application login information, the first login of the target third-party service application realized through the preset trigger operation is different from the login information of the automatic login initiated through the target third-party service application later, and the login state of the target third-party service application can be determined to be login failure.

That is, only if the first login check code is the same as the second login check code and the pre-login application information is the same as the application login information, the login state of the target third-party service application can be determined to be successful login, otherwise, the login state of the target third-party service application is determined to be failed login.

In one embodiment, as shown in fig. 8, the third-party service application login method further includes:

step 802, recording a login state corresponding to the target third-party service application and application user login information corresponding to the target third-party service application.

Step 804, establishing the incidence relation between the service application identification and the login state corresponding to the target third-party service application and the login information of the application user.

Step 806, storing the association relationship, wherein the association relationship is used for tracing the login situation of the third-party service application.

Specifically, in the third-party service application login process, the unified login platform may record a login state corresponding to the target third-party service application and login information of an application user corresponding to the target third-party service application, where the login state refers to a login status of the target third-party service application, including but not limited to success of login and failure of login, the login information of the application user refers to account information corresponding to a login user who logs in the target third-party service application, and the unified login platform may record these information corresponding to the target third-party service application in the third-party service application login process.

Furthermore, an association relation between a service application identifier corresponding to the target third-party service application and the login state and the login information of the application user is established, wherein the service application identifier is used for uniquely identifying the target third-party service application, and the corresponding third-party service application can be determined according to the service application identifier. Specifically, the service application identifier corresponding to the target third-party service application is obtained, and an association relationship between the service application identifier corresponding to the target third-party service application and the login state and application login information corresponding to the target third-party service application is established.

And finally, storing the established association relationship so as to be used for tracking the login condition of the third-party service application in the following process. That is, the association is used to trace the login situation of the third-party service application, and the login situation includes, but is not limited to, login user information, login status (login success or login failure), login address (login ID), and the like.

In a specific embodiment, a third party service application login method is provided, which specifically includes the following steps:

1. and loading the target third-party service application corresponding to the current login user of the unified login platform in an interface of the unified login platform.

1-1, obtaining a current user login request, wherein the current user login request carries a current user identifier corresponding to a current login user.

And 1-2, logging in the unified login platform according to the current user login request, and acquiring the target third-party service application corresponding to the current user identifier.

1-2-1, acquiring a preset service application mapping list, wherein the preset service application mapping list comprises a mapping relation between an initial user identifier and a corresponding third-party service application.

And 1-2-2, acquiring the target third party service application corresponding to the current user identification according to the mapping relation.

And 1-3, loading the target third-party service application in an interface of the unified login platform.

1-3-1, acquiring a front-end code corresponding to the target third-party service application.

1-3-2, acquiring a preset access code corresponding to the target third party service application, writing the preset access code into a front end code, and loading the target third party service application in an interface of the unified login platform.

2. And when the preset triggering operation of the target third-party service application is detected, recording the application pre-login information.

3. And when the current login user is determined to have the login right of the target third-party service application, generating a first login check code corresponding to the target third-party service application.

And 3-1, acquiring target user account information corresponding to the target third-party service application, wherein the target user account information has the authority of logging in the target third-party service application.

And 3-2, acquiring current user account information corresponding to the current login user.

And 3-3, when the current user account information is matched with the target user account information, determining that the current login user has the login authority of the target third-party service application.

4. And sending login indication information to the target third-party service application, wherein the login indication information carries a first login check code.

And 4-1, sending login indication information to the target third-party service application through a Post Message mechanism by using the application pre-login information and the first login check code, and informing the target third-party service application of actively initiating login.

5. And acquiring an application login request sent by the target third-party service application, wherein the application login request carries a second login check code and application login information.

6. And determining the login state of the target third-party service application according to the first login check code, the second login check code, the application pre-login information and the application login information.

6-1, when the first login check code is matched with the second login check code and the application pre-login information is matched with the application login information, determining that the login state of the target third-party service application is successful in login.

6-2, when the first login check code is not matched with the second login check code or the application pre-login information is not matched with the application login information, determining that the login state of the target third-party service application is login failure.

And 6-3, when the first login check code is not matched with the second login check code and the application pre-login information is not matched with the application login information, determining that the login state of the target third-party service application is login failure.

7. And recording the login state corresponding to the target third-party service application and the login information of the application user corresponding to the target third-party service application.

8. And establishing an incidence relation between a service application identifier and a login state corresponding to the target third-party service application and the login information of the application user.

9. And storing the incidence relation, wherein the incidence relation is used for tracing the login condition of the third-party service application.

It should be understood that, although the steps in the above-described flowcharts are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in the above-described flowcharts may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or the stages is not necessarily sequential, but may be performed alternately or alternatingly with other steps or at least a portion of the sub-steps or stages of other steps.

In one embodiment, as shown in fig. 9, there is provided a third party service application login apparatus 900, including: a third-party service application loading module 902, a third-party service application detecting module 904, a login check code generating module 906, a login indication information sending module 908, an application login request obtaining module 910, and a login state determining module 912, wherein:

and a third party service application loading module 902, configured to load, in the interface of the unified login platform, a target third party service application corresponding to a current login user of the unified login platform.

The third party service application detection module 904 is configured to record application pre-login information when a preset trigger operation of the target third party service application is detected.

And a login check code generating module 906, configured to generate a first login check code corresponding to the target third-party service application when it is determined that the current login user has the login right of the target third-party service application.

And a login indication information sending module 908, configured to send login indication information to the target third-party service application, where the login indication information carries the first login check code.

An application login request obtaining module 910, configured to obtain an application login request sent by a target third-party service application, where the application login request carries a second login check code and application login information.

A login state determining module 912, configured to determine a login state of the target third-party service application according to the first login check code, the second login check code, the application pre-login information, and the application login information.

In one embodiment, the third-party service application loading module 902 is further configured to obtain a current user login request, where the current user login request carries a current user identifier corresponding to a current login user; logging in the unified login platform according to the current user login request, and acquiring a target third-party service application corresponding to the current user identifier; and loading the target third-party service application in an interface of the unified login platform.

In one embodiment, the third-party service application loading module 902 is further configured to obtain a preset service application mapping list, where the preset service application mapping list includes a mapping relationship between an initial user identifier and a corresponding third-party service application; and acquiring the target third-party service application corresponding to the current user identifier according to the mapping relation.

In one embodiment, the third-party service application loading module 902 is further configured to obtain a front-end code corresponding to the target third-party service application; and acquiring a preset access code corresponding to the target third-party service application, writing the preset access code into the front-end code, and loading the target third-party service application in an interface of the unified login platform.

In one embodiment, the login check code generating module 906 is further configured to obtain target user account information corresponding to the target third-party service application, where the target user account information has a right to login the target third-party service application; acquiring current user account information corresponding to a current login user; and when the current user account information is matched with the target user account information, determining that the current login user has the login authority of the target third-party service application.

In one embodiment, the login indication information sending module 908 is further configured to send the application pre-login information and the first login check code to the target third party service application through a Post Message mechanism, so as to notify the target third party service application to actively initiate login.

In one embodiment, the login status determining module 912 is further configured to determine that the login status of the target third-party service application is successful when the first login check code and the second login check code are matched and the application pre-login information is matched with the application login information, determine that the login status of the target third-party service application is failed login when the first login check code is not matched with the second login check code or the application pre-login information is not matched with the application login information, and determine that the login status of the target third-party service application is failed login when the first login check code is not matched with the second login check code and the application pre-login information is not matched with the application login information.

In an embodiment, the third-party service application login apparatus 900 is further configured to record a login state corresponding to the target third-party service application and application user login information corresponding to the target third-party service application, establish an association relationship between a service application identifier and the login state corresponding to the target third-party service application and the application user login information, and store the association relationship, where the association relationship is used to trace the login situation of the third-party service application.

For specific limitations of the third-party service application login device, reference may be made to the above limitations of the third-party service application login method, which is not described herein again. All or part of the modules in the third-party service application login device can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

FIG. 10 is a diagram illustrating an internal structure of a computer device in one embodiment. The computer device may specifically be the terminal 102 in fig. 1. As shown in fig. 10, the computer apparatus includes a processor, a memory, a network interface, an input device, and a display screen connected through a system bus. Wherein the memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and may also store a computer program, which, when executed by the processor, causes the processor to implement the third party service application login method. The internal memory may also have a computer program stored therein, which when executed by the processor, causes the processor to perform a third party application login method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.

Those skilled in the art will appreciate that the architecture shown in fig. 10 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program: loading a target third-party service application corresponding to a current login user of the unified login platform in an interface of the unified login platform; when detecting the preset trigger operation of the target third-party service application, recording application pre-login information; when the current login user is determined to have the login right of the target third-party service application, generating a first login check code corresponding to the target third-party service application; sending login indication information to the target third-party service application, wherein the login indication information carries a first login check code; acquiring an application login request sent by a target third-party service application, wherein the application login request carries a second login check code and application login information; and determining the login state of the target third-party service application according to the first login check code, the second login check code, the application pre-login information and the application login information.

In one embodiment, the processor, when executing the computer program, further performs the steps of: acquiring a current user login request, wherein the current user login request carries a current user identifier corresponding to a current login user; logging in the unified login platform according to the current user login request, and acquiring a target third-party service application corresponding to the current user identifier; and loading the target third-party service application in an interface of the unified login platform.

In one embodiment, the processor, when executing the computer program, further performs the steps of: acquiring a preset service application mapping list, wherein the preset service application mapping list comprises a mapping relation between an initial user identifier and a corresponding third-party service application; acquiring a target third-party service application corresponding to the current user identifier according to the mapping relation;

in one embodiment, the processor, when executing the computer program, further performs the steps of: acquiring a front-end code corresponding to a target third-party service application; and acquiring a preset access code corresponding to the target third-party service application, writing the preset access code into the front-end code, and loading the target third-party service application in an interface of the unified login platform.

In one embodiment, the processor, when executing the computer program, further performs the steps of: acquiring target user account information corresponding to the target third-party service application, wherein the target user account information has the authority of logging in the target third-party service application; acquiring current user account information corresponding to a current login user; and when the current user account information is matched with the target user account information, determining that the current login user has the login authority of the target third-party service application.

In one embodiment, the processor, when executing the computer program, further performs the steps of: and sending login indication information to the target third-party service application through a Post Message mechanism by using the application pre-login information and the first login check code, and informing the target third-party service application of actively initiating login.

In one embodiment, the processor, when executing the computer program, further performs the steps of: when the first login check code is matched with the second login check code and the application pre-login information is matched with the application login information, determining that the login state of the target third-party service application is successful in login; or when the first login check code is not matched with the second login check code or the application pre-login information is not matched with the application login information, determining that the login state of the target third-party service application is login failure; or when the first login check code is not matched with the second login check code and the application pre-login information is not matched with the application login information, determining that the login state of the target third-party service application is login failure.

In one embodiment, the processor, when executing the computer program, further performs the steps of: recording a login state corresponding to the target third-party service application and application user login information corresponding to the target third-party service application; establishing an incidence relation between a service application identifier and a login state corresponding to a target third-party service application and login information of an application user; and storing the incidence relation, wherein the incidence relation is used for tracing the login condition of the third-party service application.

In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: loading a target third-party service application corresponding to a current login user of the unified login platform in an interface of the unified login platform; when detecting the preset trigger operation of the target third-party service application, recording application pre-login information; when the current login user is determined to have the login right of the target third-party service application, generating a first login check code corresponding to the target third-party service application; sending login indication information to the target third-party service application, wherein the login indication information carries a first login check code; acquiring an application login request sent by a target third-party service application, wherein the application login request carries a second login check code and application login information; and determining the login state of the target third-party service application according to the first login check code, the second login check code, the application pre-login information and the application login information.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A third party service application login method comprises the following steps:

loading a target third-party service application corresponding to a current login user of a unified login platform in an interface of the unified login platform, wherein the target third-party service application is a plurality of third-party service applications of which the current login user has login authority, and the third-party service applications are provided by different providers;

sending login indication information to the target third-party service application, wherein the login indication information carries the first login check code;

acquiring an application login request sent by the target third-party service application, wherein the application login request carries a second login check code and application login information;

2. The method of claim 1, wherein loading, in an interface of a unified login platform, a target third-party business application corresponding to a current login user of the unified login platform comprises:

acquiring a current user login request, wherein the current user login request carries a current user identifier corresponding to a current login user;

logging in the unified login platform according to the current user login request, and acquiring a target third-party service application corresponding to the current user identifier;

and loading the target third-party service application in an interface of the unified login platform.

3. The method of claim 2, wherein the obtaining the target third-party service application corresponding to the current user identifier comprises:

acquiring a preset service application mapping list, wherein the preset service application mapping list comprises a mapping relation between an initial user identifier and a corresponding third-party service application;

acquiring a target third-party service application corresponding to the current user identifier according to the mapping relation;

preferably, the loading the target third-party service application in the interface of the unified login platform includes:

acquiring a front-end code corresponding to the target third-party service application;

and acquiring a preset access code corresponding to the target third-party service application, and writing the preset access code into the front-end code to load the target third-party service application in an interface of a unified login platform.

4. The method of claim 1, wherein the determining that the current logged-in user has the login right of the target third-party service application comprises:

acquiring target user account information corresponding to the target third-party service application, wherein the target user account information has the authority of logging in the target third-party service application;

acquiring current user account information corresponding to the current login user;

and when the current user account information is matched with the target user account information, determining that the current login user has the login authority of the target third-party service application.

5. The method according to claim 1, wherein the sending of login indication information to the target third party service application, the login indication information carrying the first login check code, comprises:

and sending login indication information to the target third-party service application by the application pre-login information and the first login check code through a Post Message mechanism, and informing the target third-party service application to actively initiate login.

6. The method of claim 1, wherein determining the login status of the target third-party business application from the first login check code, the second login check code, the application pre-login information, and the application login information comprises:

when the first login check code is matched with the second login check code and the application pre-login information is matched with the application login information, determining that the login state of the target third-party service application is successful in login; or

When the first login check code is not matched with the second login check code or the application pre-login information is not matched with the application login information, determining that the login state of the target third-party service application is login failure; or the like, or, alternatively,

and when the first login check code is not matched with the second login check code and the application pre-login information is not matched with the application login information, determining that the login state of the target third-party service application is login failure.

7. The method of claim 1, further comprising:

recording a login state corresponding to the target third-party service application and application user login information corresponding to the target third-party service application;

establishing an association relation between a service application identifier corresponding to the target third-party service application and the login state and the login information of the application user;

and storing the incidence relation, wherein the incidence relation is used for tracing the login condition of the third-party service application.

8. A third party service application login apparatus, the apparatus comprising:

the third-party service application loading module is used for loading a target third-party service application corresponding to a current login user of a unified login platform in an interface of the unified login platform, wherein the target third-party service application is a plurality of third-party service applications of which the current login user has login authority, and the third-party service applications are provided by different providers;

a login indication information sending module, configured to send login indication information to the target third-party service application, where the login indication information carries the first login check code;

an application login request acquisition module, configured to acquire an application login request sent by the target third-party service application, where the application login request carries a second login check code and application login information;

9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of claims 1 to 7 are implemented when the computer program is executed by the processor.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.