CN111181907B

CN111181907B - Host side plug-in login method, device and equipment and storage medium

Info

Publication number: CN111181907B
Application number: CN201910673718.XA
Authority: CN
Inventors: 魏常伟
Original assignee: Tencent Technology Beijing Co Ltd
Current assignee: Tencent Technology Beijing Co Ltd
Priority date: 2019-07-24
Filing date: 2019-07-24
Publication date: 2022-05-24
Anticipated expiration: 2039-07-24
Also published as: CN111181907A

Abstract

The application provides a login method, a login device and a login storage medium of a host side plug-in, which are used for realizing the mutual independence of login states of the plug-in and the host side and meeting the requirement of independent login of the host side plug-in. The method comprises the following steps: responding a login request for logging in a plug-in through a third-party application, and acquiring a plug-in signature and a package name, wherein the plug-in is embedded in the host, the plug-in signature is consistent with the host signature, and the plug-in package name is modified according to the host Context; verifying the plug-in signature and the package name, and sending an authorization request for authorizing the login of the plug-in to a background server of the third-party application after the verification is passed; and receiving an authorization result returned after the authorization of the third-party application is passed, and controlling the service of the plug-in according to the authorization result, wherein the plug-in has an independent account system to realize independent login.

Description

Host side plug-in login method, device and equipment and storage medium

Technical Field

The present application relates to the field of wireless communications technologies, and in particular, to a method, an apparatus, and a device for logging in a host plug-in, and a storage medium.

Background

In order to avoid the overlarge installation package, some extended functions of the application program are realized by dynamically downloading the plug-in. The plug-in is formed by a plurality of service modules, and the plug-in the prior art must depend on the host.

When the host runs login and loads the plug-in the host, the plug-in uses the login information of the host. The login information used by the plug-in is not the login information of the plug-in, and therefore the plug-in is not logged in.

Disclosure of Invention

The embodiment of the application provides a login method, a login device and a login storage medium for a host side plug-in, which are used for realizing that the login states of the host side plug-in and a host side are mutually independent and meeting the requirement of independent login of the host side plug-in.

In one aspect, the present application provides a login method for a host-side plug-in, where the method includes:

responding a login request for logging in the plug-in through a third-party application, and acquiring a plug-in signature and a package name, wherein the plug-in is embedded in a host, the plug-in signature is consistent with the host signature, and the package name of the plug-in is modified according to the host Context;

verifying the signature and the package name of the plugin, and sending an authorization request for authorizing plugin login to a background server of the third-party application after the verification is passed;

and receiving an authorization result returned after the authorization of the third-party application is passed, and controlling the service of the plug-in according to the authorization result.

In one aspect, the present application provides a login device for a host-side plug-in, where the device includes:

the response module is used for responding a login request for logging in the plug-in through a third-party application, and acquiring a plug-in signature and a plug-in package name, wherein the plug-in is embedded in the host, the plug-in signature is consistent with the host signature, and the plug-in package name is modified according to the host Context;

the verification module is used for verifying the plug-in signature and the package name and sending an authorization request for authorizing the plug-in login to a background server of the third-party application after the verification is passed;

and the receiving module is used for receiving an authorization result returned after the authorization of the third-party application is passed and controlling the service of the plug-in according to the authorization result.

In one aspect, the present application provides a computer program comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the method of any of the above aspects when executing the computer program.

In one aspect, the present application provides a computer-readable storage medium having stored thereon processor-executable instructions for performing the method of any of the above aspects.

In the embodiment of the application, a login request of logging in a plugin through a third party is responded, a plugin signature and a package name are obtained, the plugin signature and the package name are verified, after the verification is passed, an authorization request for authorizing plugin login is sent to a background server of the third party application, an authorization result returned after the authorization of the third party application is passed is received, the service of the plugin is controlled according to the authorization result, the plugin signature is consistent with the host package name, the plugin package name is modified according to the host Context, and the plugin has an independent account system to realize independent login.

Additional features and advantages of the application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the application. The objectives and other advantages of the application may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

FIG. 1 is a schematic diagram of an application scenario in an embodiment of the present application;

fig. 2A is a schematic view of a display page of a host embedded plug-in the embodiment of the present application;

fig. 2B is a schematic diagram of a display page in which the host side and the host side plug-in are not logged in the embodiment of the present application;

fig. 2C is a schematic diagram of a display page in which the host side logs in but the host side plug-in is not logged in the embodiment of the present application;

fig. 2D is a schematic diagram of a display page in which both host side and host side plug-ins log in the embodiment of the present application;

FIG. 3 is a schematic diagram of a host plug-in login operation interface in an embodiment of the present application;

FIG. 4 is a flowchart illustrating a login method of a host side plugin in an embodiment of the present application;

fig. 5 is an overall flowchart of a login method of a first host-side plug-in the embodiment of the present application;

fig. 6 is an overall flowchart of a login method of a second host side plug-in the embodiment of the present application;

fig. 7 is an overall flowchart of a login method of a third host side plug-in the embodiment of the present application;

fig. 8 is an overall flowchart of a login method of a fourth host side plug-in the embodiment of the present application;

FIG. 9 is a diagram illustrating a configuration of a login device of a host side plug-in an embodiment of the present application;

fig. 10 is a diagram of a computing device in the embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application clearer, the present application will be described in further detail with reference to the accompanying drawings, and it should be understood that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Hereinafter, some terms in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

(1) Host: the method comprises the steps of installing various application programs (APP) in the mobile terminal and having the right of downloading and installing plug-ins, such as a mobile phone hundred-degree application, a hundred-degree browser application, a certain video APP and the like.

(2) Host end plug-in: the host end plug-in is packaged by a plurality of service modules and is embedded in the application program (host) without installation process; for example, a Doki service in a certain video APP, where the certain video APP is a host, and the Doki service is a host-side plug-in application embedded in the certain video APP (host).

(3) A login component: for logging in a service SDK (SDK: a set of development tools used by a software engineer to establish application software for a specific software package, a software framework, a hardware platform or an operating system and the like), taking each mainstream communication software and a portal as a logging in mode, and logging in an own system through authentication of a third-party account under the premise of not acquiring security information of the third-party account through an Oauth2.0 protocol; the login mode can be WeChat login, QQ login, microblog login and the like. For example, the login mode is WeChat, the video APP needs to be logged in, and when the video APP does not know the password of the WeChat, the VIP account of the video APP can be logged in by using the account and the password of the WeChat after the WeChat interface authentication is passed.

(4) Hook agency: the Hook technology is used for hijacking an object or a method which is originally executed by an application program, and replacing the object or the method with the object or the method which is wanted to be executed; and the Hook technique is implemented by a Hook proxy, which provides an surrogate or placeholder for an object to control access to the object.

(5) Reflection: refers to a class of applications that are capable of self-describing and self-controlling. The application realizes the description and monitoring of own behaviors by adopting a certain mechanism, and can adjust or modify the states and related semantics of the behaviors described by the application according to the states and results of the own behaviors. Reflection mechanisms are methods and properties that invoke objects dynamically at runtime.

(6) ClassLoader loading: and loading a class loader, namely loading the class file into the virtual machine so as to ensure the correct operation of the program.

(7) The CP (ContentProvider) stores: the content provider provides some specific application data to other applications for use, and the data may be stored in a file system, SQLite, or other means. And data sharing is performed among different applications, and a uniform interface is provided. Is a class that implements a set of standard methods that enable other programs to store and read certain ContentProvider processable data.

(8) The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this document generally indicates that the preceding and following related objects are in an "or" relationship unless otherwise specified.

Some brief descriptions are given below to application scenarios to which the technical solution of the embodiment of the present application can be applied, and it should be noted that the application scenarios described below are only used for describing the embodiment of the present application and are not limited. In the specific implementation process, the technical scheme provided by the embodiment of the application can be flexibly applied according to actual needs.

As shown in fig. 1, an application scenario schematic diagram provided in this embodiment of the present application includes a terminal device 11 of a user 10, where the terminal device 11 is installed with a plurality of host applications 111 and third-party applications 112 (such as WeChat, QQ, microblog, etc.), a host application background server (such as a video application background server when a host application is a video) 12 and a third-party application background server 13; the terminal device 11 is in communication connection with the host application background server 12 and the third party application background server 13 through a network, and the network may be a local area network, a cellular network, a wide area network, and the like. The terminal device 11 may be a portable device (e.g., a mobile phone, a tablet, a notebook, a wearable device, or other portable intelligent terminal device), or may be a Personal Computer (PC), and the host application backend server 12 and the third party application backend server 13 may be any devices capable of providing internet services.

Currently, the host application 111 is different from the member user (the user registered with the account) in the interest enjoyed by the common user (the user unregistered with the account) at the time of running, and the member user enjoys more interest than the common user enjoys. When a member user logs in through an account in the host application 111, if third-party logging is adopted, a logging request needs to be reported to the host application background server 12, the host application background server 12 sends an authorization request to the third-party application background server 13 according to the logging request, and an authorization interface is pulled up in the third-party application program 112 to realize the logging of a host; when the member user logs in the host application 111 through an account, the member user logs in the host application 111 by inputting a registered account and an account password in the display interface.

More rights can be enjoyed after the user logs into the host application 111. Now, as the functions of the application expand, a plug-in packaged by a service module is embedded in the host application. Because the plug-in is embedded in the host, when the host side plug-in is loaded, the login information of the host is used, and the login account corresponding to the plug-in is the login account of the host application. However, the login account of the host application is not the real login account of the plug-in, and the plug-in is not logged in at the moment, so that the rights and interests shared by the plug-in user are still the rights and interests of the ordinary user. If the user wants to enjoy the rights of the member for the plug-in, the user needs to log in the real account for the plug-in. When the real account number of the plug-in is used for plug-in login, the account number of the host is kicked off, the host and the plug-in can not be logged in at the host side at the same time, the plug-in must rely on the login/logout of the host, share one login account number with the host, and can not log in independently.

The host end is used as a certain video application, the Doki service is used as a plug-in embedded in the host end for example, and an ordinary user can only enjoy the rights and interests of the ordinary user when watching programs by using the certain video application, and the ordinary user cannot watch the VIP video. When a user registers a member account number '123' of a certain video, the user can log in by using the member account number '123' to watch a VIP video, when a Doki service plug-in a certain video application is loaded, the Doki service plug-in uses login information of the certain video application, so that the login account number of the Doki service plug-in is the same as the login account number of the certain video and is '123', but the '123' is not the account number of the Doki service plug-in, and the plug-in of the Doki service account number is '456', so that the user can not enjoy member rights and interests when using the Doki service plug-in the certain video. If a user wants to enjoy the membership rights of the Doki service plug-in and needs to log in by using the account number ' 456 ', the user needs to log out of a certain video account number ' 123 ' and log in the account number ' 456 again at the moment, but the certain video account number is kicked off, obviously, the host end plug-in and the host end plug-in cannot log in at the same time, and the host end plug-in must rely on the login/log out of the host.

Therefore, the method aims at the problems that the host end plug-in unit in the prior art must rely on the host end to log in/log out, and the host end plug-in unit cannot log in and run simultaneously; the embodiment of the application provides a login method for a host end plug-in, which is used for realizing that when the plug-in is embedded in a host and loaded as a functional module, the host and the plug-in have independent account systems, and the login states of the host and the end plug-in are mutually independent, so that the multi-login requirement of a user when the plug-in is used in host application is met.

In the embodiment of the application, when the host-side plug-in logs in, an independent login process of the host-side plug-in is started, in the login process, after a login request for logging in the host-side plug-in through a third-party application is triggered, the login request for logging in the host-side plug-in through the third-party application is responded, a signature and a package name of the host-side plug-in are obtained for verification, an authorization request for authorizing the login of the host-side plug-in is sent to a background server of the third-party application after the verification is passed, an authorization result returned after the authorization of the third-party application is passed is received, the service of the host-side plug-in is controlled according to the authorization result, the host-side plug-in has an independent account number system, the host-side plug-in is independently logged in, the plug-in and the host can log in at the same time, and the multi-account number login/logout requirements are met.

The method for host-side plug-in login provided by the exemplary embodiment of the present application is described below with reference to fig. 2A to 10 in conjunction with the application scenarios described above, it should be noted that the application scenarios described above are shown in order to facilitate understanding of the spirit and principles of the present application, and the embodiments of the present application are not limited in any way in this respect.

The login method of the host side plug-in is further described with the scenario of fig. 1. In practical application, a host (APP) with an embedded plug-in and a third-party application program are installed in the terminal equipment; and when the host end plug-in is loaded in the host, loading the host end plug-in by using ClassLoader.

In the present application, a host is taken as a certain video APP, and a Doki service in the certain video APP is taken as a host-side plug-in to run in the certain video APP for example, as shown in fig. 2A, a fourth Tab of a first page of the certain video APP runs as a host-side plug-in for the Doki service; as shown in fig. 2B, it can be known from fig. 2B that both a video member account and a Doki service are currently in an unregistered state, and after clicking a video to log in, and selecting a logged-in account to log in, a display interface after successful video login is shown in fig. 2C. It can be seen from fig. 2C that when a video is successfully logged in, the Doki service is still in the unregistered state. When the host-side plug-in login is triggered, a display interface after the host-side plug-in login is successfully performed by selecting a login account is shown in fig. 2D, and it can be known from fig. 2D that a certain video and a Doki service are both in a login state currently. The login module of the Doki service is adjacent to a certain video login module, the login states of a host (a certain video) and a host-side plug-in (Doki) are completely independent, the host and the video do not interfere with each other, the plug-in and the host can log in independently, and the multi-login requirement of a user when the plug-in is used in host application is met.

In practical application, after receiving an operation of logging in a host end plug-in triggered by a user, a terminal device responds to the operation of logging in the host end plug-in by the user, and displays a host end plug-in login operation interface on a display screen, wherein the host end plug-in login operation interface is generated by ClassLoader loading.

As shown in fig. 3, for the host side plug-in login operation interface in the embodiment of the present application, it is displayed in the login operation interface that the host side plug-in can log in through an account number and through a short message or other fast login manners;

the account login comprises the following steps: adopting the mode of inputting account number and password to log in and adopting the authorization mode of third party application to log in, wherein the third party application comprises: WeChat, QQ, microblog, Taobao, etc.

When the account password is adopted for login, after the account and the password are input into the host side plug-in login operation interface shown in the figure 3 and the login key in the host side plug-in login operation interface is clicked, the terminal equipment generates a login request, reports the login request to a background server, and can log in after the account password is verified; or

When the third-party application authorization mode is adopted for login, the third-party application is required to be authorized, and the login can be performed after the third-party application authorization is passed. The following describes a scheme for logging in the host-side plug-in by using a third-party application authorization mode in detail.

In practical application, after receiving a trigger instruction of selecting a third-party application in a host-side plug-in login operation interface by a user, a terminal device determines to log in a host-side plug-in through the third-party application, responds to the trigger instruction of the user, calls a login component corresponding to the host-side plug-in or a login component of a host, and reports a login request for logging in the host-side plug-in through the third-party application to a background server corresponding to the host-side plug-in, wherein the login request carries a login mode, and the login mode is any one of a WeChat login mode, a QQ login mode, a microblog login mode and the like for logging in through the third-party application.

A login system corresponding to a login mode is stored in the login component, and the login system comprises a login service SDK of a third-party application; the login service SDK of the third-party application is used for verifying the signature and the package name of the host-side plug-in, reporting a login request to a background server corresponding to the host-side plug-in after the verification is passed, determining the background server corresponding to the third-party application according to a login mode in the login request after the background server corresponding to the host-side plug-in receives the login request, and sending an authorization request to the background server corresponding to the third-party application so as to pull up an authorization interface in the third-party application stored in the terminal device.

In order to control the login of the host side plug-in, a corresponding login component is stored in the terminal device, the login component can be independently set for the host side plug-in or can be combined with the login component of the host, and when a login request is received, the terminal device calls the login component to control. When the terminal device calls the login component corresponding to the host side plug-in or the login component of the host, the terminal device mainly determines whether the login component corresponding to the host side plug-in is stored in the terminal. And if the login component corresponding to the host side plug-in is stored, directly calling the login component corresponding to the host side plug-in, and reporting a login request for logging in the host side plug-in through a third party application to the login component corresponding to the host side plug-in, wherein the login request comprises a login mode and can also comprise a host side plug-in signature and a package name. And if the login component corresponding to the host end plug-in does not exist, the host end plug-in and the host share the login component corresponding to the host, and the host end plug-in reports a login request for logging in the host end plug-in through a third party application to the login component corresponding to the host, wherein the login request comprises a host end plug-in name and a login mode, and further comprises a host end plug-in signature and a package name.

In practical application, if a login component of a host is called, a login request carries a host end plug-in name and a login mode, the host end plug-in login is determined according to the host end plug-in name carried in the login request, and if the login request does not carry the host end plug-in name, the host login is determined.

The following describes the login of the host side plug-in detail with reference to the flowchart.

As shown in fig. 4, a flowchart of a method for logging in a host plug-in provided in an embodiment of the present application is applied to a terminal device, and mainly includes the following steps:

and step 400, responding to a login request for logging in the plug-in through the third-party application, and acquiring a plug-in signature and a package name, wherein the plug-in is embedded in the host, the plug-in signature is consistent with the host signature, and the package name of the plug-in is modified according to the host Context.

In the host side plug-in login process, a login component in the terminal equipment needs to verify the host side plug-in signature and the package name, so that after receiving a login request for logging in the host side plug-in through a third party application, the login component responds to the login request for logging in the host side plug-in through the third party application, determines to log in the host side plug-in through the third party application, and further obtains the host side plug-in signature and the package name so as to verify the host side plug-in signature and the package name.

Since the host side plug-in is in the running environment of the host, verifying the host side plug-in signature and the package name in the login process is to verify the host side plug-in running environment signature and the package name, the consistency of the host side plug-in signature, the package name, the host signature and the package name needs to be ensured.

The host side plug-in signature is pre-stored and is consistent with the host signature, and the host side plug-in package name is modified according to the host Context.

When the host side plug-in package name is modified according to the host Context, the host side plug-in package name is replaced by the host Context by adopting the Hook proxy technology, and the host side plug-in package name is obtained through the host side plug-in package Context modified by the Hook proxy technology.

In practical application, when the login component acquires the host side plug-in signature and the package name, the host side plug-in signature and the package name carried in the login request can be acquired; or directly acquiring the host side plug-in signature and the packet name through a stored host side plug-in Context internal interface, and at the moment, acquiring the host side plug-in signature and the packet name through a login request or other modes is not needed.

Step 410, checking the signature and the package name of the host side plug-in, and after the check is passed, sending an authorization request for authorizing the login of the host side plug-in to a background server of the third party application;

in practical application, the acquired host side plug-in signature and the acquired package name are verified, whether the host side plug-in signature and the package name are registered at a third party application side corresponding to a login mode is determined, if the host side plug-in signature and the package name are registered at the third party application side corresponding to the login mode is determined, the verification is determined to be passed, after the verification is determined to be passed, a login request is reported to a background server corresponding to the host side plug-in, so that the host side plug-in determines the third party application according to the login mode in the login request, and an authorization request for authorizing the login of the host side plug-in is sent to the background server of the third party application determined according to the login mode in the login request, so that an interface for authorizing the login is displayed in the third party application corresponding to the login mode.

And if the verification fails, determining that the host side plug-in signature and the package name are not registered in the selected third party application side, and prompting the user to perform application registration on an open platform of the third party application side corresponding to the login mode.

And when the terminal equipment receives an authorization approval instruction triggered by a user on an authorization login interface, determining that authorization passes, reporting an authorization result passing the authorization to a background server of the third-party application corresponding to the login mode, and returning the authorization result to a login component in the terminal by the background server of the third-party application corresponding to the login mode.

And step 420, receiving an authorization result returned after the authorization of the third-party application is passed, and controlling the service of the host-side plug-in according to the authorization result.

And after the host side plug-in is determined to log in, the authorization result is put back to the host side plug-in the terminal equipment, so that the host side plug-in determines that the log-in is successful according to the authorization result and controls the service of the host side plug-in according to the authorization result.

According to the scheme, a login request for logging in the host side plug-in through the third party is responded, a host side plug-in signature and a package name are obtained, the host side plug-in signature and the package name are verified, after the verification is passed, an authorization request for authorizing the login of the host side plug-in is sent to a background server of the third party application, an authorization result returned after the authorization of the third party application is passed is received, the service of the host side plug-in is controlled according to the authorization result, wherein the host side plug-in signature is consistent with the host package name, the host side plug-in package name is modified according to the host Context, and the host side plug-in can log in independently, so that the host side plug-in and the host can log in at the same time, and the multi-account login/logout requirements are met.

In practical application, different login modes correspond to different login systems, different operation flows correspond to different login systems, and meanwhile, since the login component corresponding to the host end plug-in or the login component of the host is called when the login component is called, the operation flows corresponding to the different login components are called differently. The following description will be made by taking two registration methods, i.e., WeChat registration and QQ registration, as an example.

The login method is as follows: and (6) logging in the WeChat.

1. And calling the login component corresponding to the host side plug-in.

When the login component corresponding to the host side plug-in is called, the login component corresponding to the host side plug-in needs to be integrated, and the login/logout and local login information storage functions of the host side plug-in are realized; and setting the login refreshing frequency of the host side plug-in according to the service requirement.

As shown in fig. 5, an overall flowchart of a login method of a first host-side plug-in the embodiment of the present application is shown, which includes the following steps:

and 500, responding to the operation of logging in the host side plug-in by the user by the host side plug-in the terminal equipment, and displaying a host side plug-in login operation interface.

In practical application, the host side plug-in login operation interface is generated through ClassLoader loading.

Step 501, responding to an instruction that a user selects WeChat in a host side plug-in login operation interface by a host side plug-in the terminal equipment, and determining a login request for logging in the host side plug-in through WeChat.

Step 502, the host side plug-in the terminal equipment calls the login component corresponding to the host side plug-in stored in the terminal equipment, and reports the login request logged in through the WeChat to the login component corresponding to the host side plug-in.

The user selects the operation of logging in the host side plug-in through the third party application WeChat in the host side plug-in login operation interface of FIG. 3, the terminal device responds to the operation of the user in the host side plug-in login operation interface, determines the login request of logging in the host side plug-in through WeChat, calls the login component corresponding to the host side plug-in stored in the terminal device, and reports the login request of logging in the host side plug-in through WeChat to the login component corresponding to the host side plug-in.

In practical application, the login component corresponding to the host side plug-in is called and the login request for logging in the host side plug-in through the WeChat can be carried out simultaneously or in a time-sharing manner;

for example, when the host-side plug-in is started, a login component corresponding to the host-side plug-in stored in the terminal device is called, after an operation that a user selects to log in through WeChat in a host-side plug-in login operation interface is received, the operation of the user is responded, a login request for logging in the host-side plug-in through WeChat is determined, and the login request is reported to the login component corresponding to the host-side plug-in; or

After receiving an operation of logging in the host side plug-in triggered by a user, responding to the operation of logging in the host side plug-in by the user, displaying a host side plug-in login operation interface, and calling a login component of the host side plug-in; after receiving the operation that the user selects to log in through the WeChat in the host side plug-in unit login operation interface, determining a login request for logging in the host side plug-in unit through the WeChat, responding to the login request of the user for logging in the host side plug-in unit through the WeChat, and reporting the login request to a login component corresponding to the host side plug-in unit.

Step 503, after the login component corresponding to the host side plug-in the terminal device receives the login request reported by the login component, the host side plug-in signature and the package name are obtained.

The host end plug-in signature and the package name can be determined according to a host end plug-in signature and a package name carried in the login request, the host end plug-in signature and the package name can also be determined to execute the login process of the host end plug-in after the login request is determined, after the host end plug-in signature and the package name need to be verified, the host end plug-in signature and the package name are obtained through a PluginContext internal interface stored in a login component corresponding to the host end plug-in, wherein the host end plug-in signature is consistent with the host signature, and the host end plug-in package name is modified according to the host Context.

Step 504, the login component corresponding to the host side plug-in the terminal device verifies the host side plug-in signature and the package name.

And 505, determining whether the check is passed or not by a login component corresponding to the host side plug-in the terminal equipment, if so, executing step 506, and otherwise, executing step 517.

In practical application, the acquired host side plug-in signature and the acquired package name are verified, whether the host side plug-in signature and the package name are registered at the third party application side corresponding to the login mode is determined, if the host side plug-in signature and the package name are registered at the third party application side corresponding to the login mode, the verification is determined to be passed, and if the verification is not determined to be passed, the verification is determined to be not passed.

Step 506, the login component corresponding to the host side plug-in the terminal device reports the login request of logging in the host side plug-in through the WeChat to the background server corresponding to the host side plug-in.

And 507, responding to the login request by the background server corresponding to the host side plug-in the terminal equipment, and determining the third-party application background server for logging in through WeChat according to the login mode in the login request.

For example, if the login mode in the login request is login through WeChat, the third-party application background server is determined to be the background server corresponding to the WeChat.

And step 508, the background server corresponding to the host side plug-in the terminal equipment sends an authorization request to the background server corresponding to the WeChat.

Step 509, the background server corresponding to the wechat sends the authorization request to the third party application wechat in the terminal device.

And step 510, responding to the authorization request by the third-party application WeChat in the terminal equipment, and displaying an authorization login interface.

And 511, responding to an authorization passing instruction triggered by the user on an authorization login interface by the third-party application WeChat in the terminal equipment.

And after the third-party application receives the authorization request, responding to the authorization request, pulling up an authorization login interface in a display interface of the WeChat, displaying a key for authorizing login in the authorization login interface, and after a user clicks the key for authorizing login in the authorization login interface, responding to the operation of the user and determining that the authorization is passed.

And step 512, the third-party application micro-message in the terminal equipment returns the authorization result carrying the login information to the login component corresponding to the host-side plug-in the terminal through the corresponding background server.

Step 513, the login component corresponding to the host side plug-in the terminal device receives an authorization result returned after the authorization of the third party application passes, and judges whether the login is the login of the host side plug-in, if the login is the login of the host side plug-in, step 514 is executed, otherwise step 516 is executed;

in practical application, after receiving an authorization result, a login component corresponding to a host-side plug-in a terminal device pulls up a host login result page through reflection, and judges whether a login source is the host-side plug-in login, if the login source is the host-side plug-in login, login information in the received authorization result is distributed to the host-side plug-in through Intent so as to store the login information in a host-side plug-in CP, otherwise, plug-in information is stored in the host CP.

And 514, distributing the login information to the host side plug-in by the login component corresponding to the host side plug-in the terminal equipment.

Step 515, the host plug-in the terminal device stores the login information in the host plug-in CP.

And step 516, the login component corresponding to the host side plug-in the terminal device stores the login information in the host CP.

In practical application, the login information includes a WeChat account ID, a WeChat nickname, a WeChat head portrait, and the like.

And step 517, the login component corresponding to the host side plug-in the terminal equipment returns the information that the verification fails to pass to the host side plug-in.

And step 518, responding to the information that the verification fails by the host-side plug-in the terminal equipment, and displaying prompt information for performing application registration on the open platform of the WeChat in a display interface.

2. The login component of the host is invoked.

When the login component of the host is called, the login/logout and local login information storage functions of the host side plug-in are realized by sharing the login component of the host; and setting the login refreshing frequency of the host side plug-in according to the service requirement.

As shown in fig. 6, a flowchart of a method for logging in a second host plug-in the embodiment of the present application includes the following steps:

step 600, the host side plug-in the terminal device responds to the operation of the user for logging in the host side plug-in, and displays a host side plug-in login operation interface.

Step 601, responding to an instruction of selecting WeChat in a host side plug-in login operation interface by a user in the terminal equipment, and determining a login request for logging in through WeChat.

Step 602, the host side plug-in the terminal device calls the host login component stored in the terminal device, and reports the login request logged in by the WeChat to the host login component.

The user selects the operation of logging in the host side plug-in through the third party application WeChat in the host side plug-in login operation interface shown in the figure 3, the terminal device responds to the operation of the user in the host side plug-in login operation interface, determines the login request of logging in the host side plug-in through the WeChat, calls the login component corresponding to the host stored in the terminal device, and reports the login request of logging in the host side plug-in through the WeChat to the login component corresponding to the host.

In practical application, the login component of the calling host and the login request for determining the login of the host end plug-in through the WeChat can be carried out simultaneously or in a time-sharing manner;

for example, when the host side plug-in is started, a login component corresponding to a host stored in the terminal device is called, after an operation that a user selects to log in through WeChat in a host side plug-in login operation interface is received, the operation of the user is responded, a login request for logging in the host side plug-in through WeChat is determined, and the login request is reported to the login component corresponding to the host; or

After receiving an operation of logging in the host side plug-in triggered by a user, responding to the operation of logging in the host side plug-in by the user, displaying a host side plug-in login operation interface, and calling a host login component; after receiving the operation that a user selects to log in the host end plug-in the host end plug-in login operation interface through WeChat, determining a login request for logging in the host end plug-in through WeChat, responding to the login request of the user for logging in the host end plug-in through WeChat, and reporting the login request to a login component.

Step 603, the login component corresponding to the host in the terminal equipment determines to perform host side plug-in login.

The login component corresponding to the host in the terminal equipment determines that the host side plug-in logs in according to the host side plug-in name or the host side plug-in identification carried in the login request, and determines that the login request is the login request for logging in the host side plug-in through WeChat; and if the login request does not carry the host side plug-in name or the host side plug-in identifier, determining that the login request is the login request for logging in the host through the WeChat.

Step 604, the login component corresponding to the host in the terminal device obtains the host side plug-in package name and signature.

Step 605, the login component corresponding to the host in the terminal device checks the signature and the entry of the host-side plug-in.

In step 606, the login component corresponding to the host in the terminal device determines whether the verification passes, if so, step 607 is executed, otherwise, step 618 is executed.

Step 607, the login component corresponding to the host in the terminal device reports the login request for logging in the host side plug-in through the WeChat to the background server corresponding to the host side plug-in.

The login request carries a login mode.

And 608, responding to the login request by the background server corresponding to the host side plug-in the terminal equipment, and determining the third-party application background server for the WeChat login according to the login mode in the login request.

In practical application, a background server corresponding to a host side plug-in the terminal device determines that the third-party application is WeChat according to a login request which is reported by a login component corresponding to a host in the terminal device and logs in the host side plug-in through WeChat.

Step 609, the background server corresponding to the host side plug-in the terminal equipment sends an authorization request to the background server corresponding to the WeChat.

And step 610, the background server corresponding to the WeChat sends the authorization request to a third party application WeChat in the terminal equipment.

Step 611, the third party application in the terminal device responds to the authorization request by WeChat and displays an authorization login interface.

And step 612, responding to an authorization passing instruction triggered by the user in the authorization login interface by the third-party application WeChat in the terminal equipment.

Step 613, the third party application WeChat in the terminal equipment returns the authorization result with the login information to the login component corresponding to the host in the terminal equipment through the corresponding background server.

Step 614, the login component corresponding to the host in the terminal equipment receives an authorization result returned after the authorization of the third-party application passes, whether the login is a host-side plug-in login is judged, if the login is the host-side plug-in login, step 615 is executed, and if the login is not the host-side plug-in login, step 617 is executed;

Step 615, the login component corresponding to the host in the terminal device distributes the login information to the host plug-in.

In step 616, the host plug-in the terminal device stores the login information in the host plug-in CP.

In step 617, the corresponding login component of the home in the terminal device stores the login information in the home CP.

Step 618, the login component corresponding to the host in the terminal device returns the information that the verification fails to pass to the host side plug-in.

Step 619, the host side plug-in the terminal equipment responds to the information that the verification fails, and prompt information for carrying out application registration on the open platform of the WeChat is displayed in the display interface.

And a second login mode: and (5) logging in the QQ.

1. And calling the login component corresponding to the host side plug-in.

As shown in fig. 7, a flowchart of a third method for login of a host plug-in the embodiment of the present application is shown, which includes the following steps:

step 700, the host side plug-in the terminal equipment responds to the operation of the user for logging in the host side plug-in, and displays a host side plug-in login operation interface.

Step 701, responding to a command that a user selects a QQ in a host side plug-in login operation interface by a host side plug-in the terminal equipment, and determining a login request for logging in the host side plug-in through the QQ.

Step 702, the host side plug-in the terminal device calls the login component corresponding to the host side plug-in stored in the terminal device, and reports the login request logged in through the QQ to the login component corresponding to the host side plug-in.

The user selects the operation of logging in the host-side plug-in through the third-party application QQ in the host-side plug-in login operation interface in fig. 3, the terminal device responds to the operation of the user in the host-side plug-in login operation interface, determines the login request of logging in the host-side plug-in through the QQ, calls the login component corresponding to the host-side plug-in stored in the terminal device, and reports the login request of logging in the host-side plug-in through the QQ to the login component corresponding to the host-side plug-in.

In practical application, the login component corresponding to the host end plug-in is called, and the login request for logging in the host end plug-in through the WeChat can be carried out simultaneously or in a time-sharing manner;

for example, when the host-side plug-in is started, a login component corresponding to the host-side plug-in stored in the terminal device is called, after an operation that a user selects to log in through a QQ in a login operation interface of the host-side plug-in is received, the operation of the user is responded, a login request for logging in the host-side plug-in through the QQ is determined, and the login request is reported to the login component corresponding to the host-side plug-in; or

After receiving the operation of logging in the host side plug-in triggered by the user, responding the operation of logging in the host side plug-in by the user, displaying a host side plug-in login operation interface, and calling a login component of the host side plug-in; after receiving the operation that the user selects to log in the host side plug-in through the QQ in the host side plug-in login operation interface, determining a login request for logging in the host side plug-in through the QQ, responding the login request of the user for logging in the host side plug-in through the QQ, and reporting the login request to the login component.

In step 703, after receiving the login request reported by the login component, the login component corresponding to the host side plugin in the terminal device obtains the host side plugin signature and package name.

Step 704, the login component corresponding to the host side plug-in the terminal device checks the host side plug-in signature and the package name.

Step 705, the login component corresponding to the host side plug-in the terminal device determines whether the verification passes, if so, step 706 is executed, otherwise, step 715 is executed.

Step 706, the login component corresponding to the host side plug-in the terminal device reports the login request for logging in the host side plug-in through the QQ to the background server corresponding to the host side plug-in.

And 707, responding to the login request by the background server corresponding to the host side plug-in the terminal device, and determining the third-party application background server for QQ login according to the login mode in the login request.

Step 708, the background server corresponding to the host side plug-in the terminal device sends an authorization request to the background server corresponding to the QQ.

And 709, the background server corresponding to the QQ sends the authorization request to a third party application QQ in the terminal equipment.

And step 710, responding to the authorization request by a third party application QQ in the terminal equipment, and displaying an authorization login interface.

And 711, responding to an authorization passing instruction triggered by the user authorization login interface by the third party application QQ in the terminal equipment.

And after receiving the authorization request, the third-party application responds to the authorization request, pulls up an authorization login interface in the display interface of the QQ, displays a key for authorizing login in the authorization login interface, and responds to the operation of the user after the user clicks the key for authorizing login in the authorization login interface to determine that the authorization is passed.

And 712, the third party application QQ in the terminal device returns the authorization result with the login information to the login component corresponding to the host side plug-in the terminal through the corresponding background server.

And 713, receiving an authorization result returned after the authorization of the third-party application is passed by a login component corresponding to the host-side plug-in the terminal equipment, and returning the login information in the authorization result to the host-side plug-in a page CallBack mode.

In step 714, the host plug-in the terminal device stores the login information in the authorization result in the host plug-in CP.

In practical applications, the login information includes the ID of the QQ, the nickname of the QQ, the QQ avatar, and the like.

And 715, returning the information that the verification fails to pass to the host-side plug-in by the login component corresponding to the host-side plug-in the terminal equipment.

And 716, displaying prompt information for application registration on the QQ open platform in a display interface of the terminal device.

2. The login component of the host is invoked.

As shown in fig. 8, a flowchart of a fourth method for login of a host plug-in the embodiment of the present application is shown, which includes the following steps:

step 800, responding to the operation of logging in the host side plug-in by the user by the host side plug-in the terminal equipment, and displaying a host side plug-in login operation interface.

Step 801, responding to a command that a user selects a QQ in a host plug-in login operation interface by a host plug-in the terminal equipment, and determining a login request for logging in through the QQ.

Step 802, the host side plug-in the terminal device calls the host login component stored in the terminal device, and reports the login request logged in through the QQ to the host login component.

In the host side plug-in login operation interface of fig. 3, the user selects the third party application QQ, and the terminal device responds to the selection of the user and determines to log in the host side plug-in through the QQ.

And step 803, determining to log in the host-side plug-in by the login component corresponding to the host in the terminal equipment.

The login component corresponding to the host in the terminal equipment determines that the host side plug-in logs in according to the host side plug-in name or the host side plug-in identification carried in the login request, and determines that the login request is the login request for logging in the host side plug-in through WeChat; and if the login request does not carry the host side plug-in name or the host side plug-in identification, determining that the login request is the login request for logging in the host through the WeChat.

And step 804, the login component corresponding to the host in the terminal equipment acquires the host end plug-in package name and the signature.

Step 805, the login component corresponding to the host in the terminal device checks the signature and the entry of the host-side plug-in.

Step 806 is that the corresponding login component hosted in the terminal device determines whether the verification passes, if so, step 807 is executed, otherwise, step 816 is executed.

In step 807, the login component corresponding to the host in the terminal device reports the login request of logging in the host side plug-in through the QQ to the background server corresponding to the host side plug-in.

The login request carries a login mode.

And 808, responding to the login request by the background server corresponding to the host-side plug-in the terminal equipment, and determining the third-party application background server for logging in through QQ according to the login mode in the login request.

In practical application, the background server corresponding to the host-side plug-in the terminal device determines that the third-party application is the QQ according to the login request reported by the login component corresponding to the host in the terminal device and logged in the host-side plug-in through the QQ.

Step 809, the background server corresponding to the host side plug-in the terminal device sends an authorization request to the background server corresponding to the QQ.

Step 810, the QQ corresponding to the background server sends the authorization request to the third party application QQ in the terminal device.

Step 811, the third party application QQ in the terminal device responds to the authorization request and displays an authorization login interface.

In step 812, the third party application QQ in the terminal device responds to the authorization passing instruction triggered by the user in the authorization interface.

Step 813, the third party application QQ in the terminal device returns the authorization result with the login information to the corresponding login component hosted in the terminal device through the corresponding background server.

And 814, the login component corresponding to the host in the terminal device receives an authorization result returned after the authorization of the third-party application passes, and returns the login information in the authorization result to the host-side plug-in a page CallBack mode.

Step 815, the host plug-in the terminal device stores the login information in the authorization result in the host plug-in CP.

Step 816, the login component corresponding to the host side plug-in the terminal device returns the information that the verification fails to pass to the host side plug-in.

And 817, displaying prompt information for performing application registration on the QQ open platform in a display interface of the terminal device.

In practical application, after the host side plug-in logs in, the login result carried in the received authorization result is stored in CP, and the login result is distributed to each service module in the host side plug-in, and each service module in the host side plug-in refreshes own service.

Based on the foregoing embodiments, an embodiment of the present application provides a login apparatus for a host-side plug-in, as shown in fig. 9, the apparatus 900 at least includes:

a response module 901, configured to respond to a login request for logging in a plug-in through a third-party application, and obtain a plug-in signature and a package name, where the plug-in is embedded in a host, the plug-in signature is consistent with the host signature, and the package name of the plug-in is modified according to a host Context;

the verification module 902 is configured to verify the plug-in signature and the package name, and send an authorization request for authorizing plug-in login to a background server of the third-party application after the verification is passed;

and the receiving module 903 is configured to receive an authorization result returned after the authorization of the third-party application passes, and control a service of the plug-in according to the authorization result.

Optionally, the response module 901 is specifically configured to:

responding to the operation of a user for logging in the plug-in, and displaying a plug-in login operation interface, wherein the plug-in login operation interface is generated by ClassLoader loading;

and determining the login request as a login request for logging in the plug-in through the third-party application according to the third-party application selected by the user in the plug-in login operation interface.

Optionally, the checking module 902 is specifically configured to:

and calling a login component corresponding to the plug-in or a host login component, checking the signature and the package name of the plug-in, and sending an authorization request for authorizing the plug-in to log in to a background server of the third-party application after the verification is passed.

Optionally, the receiving module 903 is further configured to: and storing the login information carried in the authorization result in the plug-in CP.

For convenience of description, the above parts are separately described as units (or modules) according to functional division. Of course, the functionality of the various elements (or modules) may be implemented in the same one or more pieces of software or hardware in practicing the present application.

After introducing the method and apparatus for host-side plug-in login according to the exemplary embodiments of the present application, a computing apparatus according to another exemplary embodiment of the present application is introduced next.

As will be appreciated by one skilled in the art, aspects of the present application may be embodied as a system, method or program product. Accordingly, various aspects of the present application may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.

In some possible implementations, a computing device according to the present application may include at least one processor, and at least one memory. Wherein the memory stores program code which, when executed by the processor, causes the processor to perform the steps of the host-side plug-in login according to various exemplary embodiments of the present application described above in the present specification. For example, the processor may perform the steps as shown in fig. 4-8.

The computing device 100 according to this embodiment of the present application is described below with reference to fig. 10. The computing device 100 shown in fig. 10 is only an example and should not bring any limitation to the function and scope of use of the embodiments of the present application.

As shown in fig. 10, computing device 100 is embodied in the form of a general purpose computing device. Components of computing device 100 may include, but are not limited to: the at least one processor 101, the at least one memory 102, and a bus 103 connecting the various system components (including the memory 102 and the processor 101).

Bus 103 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a processor, or a local bus using any of a variety of bus architectures.

Memory 102 may include readable media in the form of volatile memory, such as Random Access Memory (RAM)1021 and/or cache memory 1022, and may further include Read Only Memory (ROM) 1023.

Memory 102 may also include a program/utility 1025 having a set (at least one) of program modules 1024, such program modules 1024 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

The computing device 100 may also communicate with one or more external devices 104 (e.g., keyboard, pointing device, etc.), with one or more devices that enable a user to interact with the computing device 100, and/or with any devices (e.g., router, modem, etc.) that enable the computing device 100 to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface 105. Also, the computing device 100 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) through the network adapter 106. As shown, the network adapter 106 communicates with other modules for the computing device 100 over the bus 103. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the computing device 100, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

In some possible embodiments, the aspects of the method for logging in a host-side plug-in provided by the present application may also be implemented in the form of a program product including program code for causing a computer device to perform the steps in the method for logging in a host-side plug-in according to various exemplary embodiments of the present application described above in this specification when the program product is run on the computer device, for example, the computer device may perform the steps as shown in fig. 4 to 8.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The program product for host side plug-in login of the embodiments of the present application may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a computing device. However, the program product of the present application is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user computing device, partly on the user equipment, as a stand-alone software package, partly on the user computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

It should be noted that although in the above detailed description several units or sub-units of the apparatus are mentioned, such a division is merely exemplary and not mandatory. Indeed, the features and functions of two or more units described above may be embodied in one unit, according to embodiments of the application. Conversely, the features and functions of one unit described above may be further divided into embodiments by a plurality of units.

Further, while the operations of the methods of the present application are depicted in the drawings in a particular order, this does not require or imply that these operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A login method of a host side plug-in is characterized by comprising the following steps:

the terminal equipment responds to a login request for logging in a plug-in through a third-party application through a login component, and obtains a plug-in signature and a package name, wherein the plug-in is embedded in the host, the plug-in signature is consistent with the host signature, and the plug-in package name is modified according to the host Context;

verifying the plug-in signature and the package name through a login service SDK of the third-party application stored in the login component, determining that the plug-in signature and the package name are registered at the third-party application terminal based on a verification result, and sending an authorization request for authorizing the login of the plug-in to a background server of the third-party application through a background server corresponding to the plug-in;

2. The method of claim 1, wherein responding to the login request via the third party application login plug-in is preceded by:

and determining the login request as a login request for logging in the plugin through the third-party application according to the third-party application selected by the user in the plugin login operation interface.

3. The method according to claim 1, wherein the verifying the plug-in signature and the package name, and sending an authorization request for authorizing a plug-in login to a backend server of the third-party application after the verification is passed specifically includes:

and calling a login component corresponding to the plug-in or the login component of the host, checking the signature and the package name of the plug-in, and sending an authorization request for authorizing the login of the plug-in to a background server of the third-party application after the check is passed.

4. The method of claim 1, wherein after receiving an authorization result returned after the third-party application passes the authorization, the method further comprises:

and storing the login information carried in the authorization result in the plug-in CP.

5. A login device of a host side plug-in, the device comprising:

the response module is used for responding a login request for logging in a plug-in through a third-party application through a login component and acquiring a plug-in signature and a package name, wherein the plug-in is embedded in the host, the plug-in signature is consistent with the host signature, and the plug-in package name is modified according to the host Context;

the verification module is used for verifying the plug-in signature and the package name through a login service SDK of the third-party application stored in the login component, determining that the plug-in signature and the package name are registered at the third-party application terminal based on a verification result, and sending an authorization request for authorizing the login of the plug-in to a background server of the third-party application through a background server corresponding to the plug-in;

and the receiving module is used for receiving an authorization result returned after the authorization of the third-party application passes and controlling the service of the plug-in according to the authorization result.

6. The apparatus of claim 5, wherein the response module is further configured to display a plugin login operation interface in response to an operation of a user to login a plugin, wherein the plugin login operation interface is generated by ClassLoader loading; and determining the login request as a login request for logging in the plugin through the third-party application according to the third-party application selected by the user in the plugin login operation interface.

7. The apparatus according to claim 5, wherein the verification module is specifically configured to invoke a login component corresponding to the plug-in or a login component of the host, verify the plug-in signature and the package name, and send an authorization request for authorizing a plug-in login to the backend server of the third-party application after the verification is passed.

8. The apparatus of claim 5, wherein the receiving module is further configured to store the login information carried in the authorization result in the plug-in CP.

9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the program implements the method of any of claims 1 to 4.

10. A computer-readable storage medium storing processor-executable instructions for performing the method of any one of claims 1 to 4.