Application identity verification method and device, equipment and storage medium
By deploying application stores and encryption applications in terminal devices, combined with the authentication status of encryption applications, the problem of application management differences in multi-user environments is solved and device security is improved.
Patent Information
- Application Number
- CN202311550654.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-11-20
- Publication Date
- 2025-05-20
AI Technical Summary
During the process of uninstalling deployed applications at the terminal, there are different requirements for uninstalling applications by multiple users and different users, resulting in differences in application management and lack of an authentication mechanism.
通过在待管理设备中部署应用商店和加密应用,获取目标操作指令并响应用户的身份验证状态,若加密应用已完成身份验证,则允许对目标应用进行管理。
实现了在多用户环境下对应用管理权限的确定和控制,减少了应用管理的差异,提高了设备的安全性。
Smart Images

Figure CN120020777A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of software technology, and in particular, to an identity authentication method, device, equipment, and storage medium for an application. Background Art
[0002] An application (APP) is also called an application, which refers to a computer program for completing one or more functions. To adapt to different usage scenarios, an electronic device (such as a terminal, a server) can manage an application in response to a user's demand. For example, the terminal uninstalls a deployed application.
[0003] Currently, during the process of the terminal uninstalling a deployed application, the terminal needs to receive an operation instruction input by the user in the application store to uninstall the deployed application, and in response to this operation instruction, uninstall the deployed application. However, in the above technical solution, there may be multiple users of the terminal, and the uninstallation requirements of the deployed applications in the terminal for different users are also different, resulting in differences in the management of applications. Therefore, how to perform identity authentication during the process of managing applications has become an urgent technical problem to be solved. Summary of the Invention
[0004] This application provides an identity authentication method, device, equipment, and storage medium for an application, which is used to solve the problem of how to perform identity authentication during the process of managing applications.
[0005] To achieve the above object, this application adopts the following technical solutions:
[0006] In a first aspect, this application provides an identity authentication method for an application. This method is applied to a device to be managed, and the device to be managed is deployed with an application store and an encrypted application. The method includes: The device to be managed obtains a target operation instruction, and the target operation instruction is used to indicate managing a target application in the application store. The device to be managed, in response to the target operation instruction, obtains target status information of the encrypted application, and the target status information is used to indicate the identity authentication status of the encrypted application. If the target status information is the first status information, the device to be managed manages the target application according to the target operation instruction, and the first status information is used to indicate that the encrypted application has completed identity authentication.
[0007] The technical solution provided by this application at least brings the following beneficial effects: The device to be managed is deployed with an application store and an encrypted application. The device to be managed can obtain a target operation instruction, which is used to indicate managing a target application in the application store. Then, the device to be managed can, in response to the target operation instruction, obtain the target status information of the encrypted application, and the target status information is used to indicate the authentication status of the encrypted application. Next, the device to be managed can determine whether the target status information is the first status information, and the first status information is used to indicate that the encrypted application has completed authentication. If the device to be managed determines that the target status information is the first status information, the device to be managed can manage the target application according to the target operation instruction. That is to say, the device to be managed can determine whether to respond to the user's management operation of the application in the application store according to the authentication status of the encrypted application for the user. In this way, in the case of multiple users, the device can, by authenticating the users, determine the management authority of each user over the applications in the device, reduce the differences in application management, and improve the security of the device.
[0008] Optionally, the device to be managed stores preset identity information, and the method further includes: If the target status information is the second status information, the device to be managed obtains the first identity information to be verified, and the second status information is used to indicate that the encrypted application has not completed authentication. The device to be managed determines whether the first identity information to be verified is the same as the preset identity information. The above method of "the device to be managed manages the target application according to the target operation instruction" further includes: If the identity information to be verified is the same as the preset identity information, the device to be managed manages the target application according to the target operation instruction.
[0009] Optionally, the method further includes: The device to be managed obtains a target operation instruction, which is used to indicate operating the device to be managed. The device to be managed, in response to the target operation instruction, obtains the second identity information to be verified. The device to be managed determines whether the second identity information to be verified is the same as the preset identity information. If the second identity information to be verified is the same as the preset identity information, the device to be managed updates the target status information to the first status information.
[0010] Optionally, the method further includes: If the second identity information to be verified is not the same as the preset identity information, the device to be managed updates the target status information to the second status information.
[0011] Optionally, the target operation instruction is any of the following instructions: a first operation instruction for indicating updating the target application, a second operation instruction for indicating uninstalling the target application, and a third operation instruction for indicating installing the target application.
[0012] Second aspect, the present application provides an authentication device for an application, which is applied to a device to be managed. The device to be managed is deployed with an application store and an encrypted application. The device includes: an acquisition module and a processing module.
[0013] The acquisition module is configured to acquire a target operation instruction, where the target operation instruction is used to indicate managing a target application in the application store. The acquisition module is further configured to, in response to the target operation instruction, acquire target status information of the encrypted application, where the target status information is used to indicate the authentication status of the encrypted application. The processing module is configured to, if the target status information is the first status information, manage the target application according to the target operation instruction, where the first status information is used to indicate that the encrypted application has completed authentication.
[0014] Optionally, the device to be managed stores preset identity information. The acquisition module is further configured to, if the target status information is the second status information, acquire first identity information to be verified, where the second status information is used to indicate that the encrypted application has not completed authentication. The processing module is further configured to determine whether the first identity information to be verified is the same as the preset identity information. Specifically, the processing module is configured to, if the identity information to be verified is the same as the preset identity information, manage the target application according to the target operation instruction.
[0015] Optionally, the acquisition module is further configured to acquire a target running instruction, where the target running instruction is used to indicate running the device to be managed. The acquisition module is further configured to, in response to the target running instruction, acquire second identity information to be verified. The processing module is further configured to determine whether the second identity information to be verified is the same as the preset identity information. The processing module is further configured to, if the second identity information to be verified is the same as the preset identity information, update the target status information to the first status information.
[0016] Optionally, the processing module is further configured to, if the second identity information to be verified is not the same as the preset identity information, update the target status information to the second status information.
[0017] Optionally, the target operation instruction is any one of the following instructions: a first operation instruction for indicating updating the target application, a second operation instruction for indicating uninstalling the target application, and a third operation instruction for indicating installing the target application.
[0018] Third aspect, the present application provides an authentication device for an application, which includes: a processor and a memory. The processor and the memory are coupled. The memory is used to store one or more programs, and the one or more programs include computer execution instructions. When the authentication device for the application runs, the processor executes the computer execution instructions stored in the memory to implement the authentication method for the application described in the first aspect or any optional one of the first aspect.
[0019] Fourthly, the present application provides a computer-readable storage medium. Instructions are stored in the computer-readable storage medium. When the instructions run on a computer, the computer is caused to execute the authentication method of the application described in the first aspect or any optional one of the first aspect.
[0020] Fifthly, the present application provides a computer program product, which is applied to a server. The computer program product includes computer instructions. When the computer instructions run on the server, the server implements the authentication method of the application described in the first aspect or any optional one of the first aspect.
[0021] In the above solutions, for the technical problems that can be solved and the technical effects achieved by the authentication device, equipment, computer storage medium or computer program product of the application, reference can be made to the technical problems solved and technical effects in the first aspect above, which will not be elaborated here. Description of the Drawings
[0022] Figure 1 It is a device system architecture diagram provided by an embodiment of the present application;
[0023] Figure 2 It is a schematic flowchart of an authentication method of an application provided by an embodiment of the present application;
[0024] Figure 3 It is a schematic flowchart of another authentication method of an application provided by an embodiment of the present application;
[0025] Figure 4 It is a schematic flowchart of another authentication method of an application provided by an embodiment of the present application;
[0026] Figure 5 It is a schematic flowchart of another authentication method of an application provided by an embodiment of the present application;
[0027] Figure 6 It is a schematic structural diagram of an authentication device of an application provided by an embodiment of the present application;
[0028] Figure 7 It is a schematic structural diagram of an authentication device of an application provided by an embodiment of the present application;
[0029] Figure 8 It is a conceptual partial view of a computer program product provided by an embodiment of the present application. Detailed Embodiments
[0030] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.
[0031] In this text, the character " / " generally indicates an "or" relationship between the associated objects before and after. For example, A / B can be understood as A or B.
[0032] The terms "first" and "second" in the description and claims of the present application are used to distinguish different objects, rather than to describe a specific order of the objects.
[0033] In addition, the terms "including" and "having" and any variations thereof mentioned in the description of the present application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or modules is not limited to the listed steps or modules, but optionally further includes other unlisted steps or modules, or optionally further includes other steps or modules inherent to these processes, methods, products, or devices.
[0034] In addition, in the embodiments of the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations, or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present concepts in a specific manner.
[0035] Before introducing the identity authentication method of the application provided in the embodiments of the present application in detail, the implementation environment and application scenarios of the embodiments of the present application will be introduced first.
[0036] First, the application scenarios of the embodiments of the present application will be introduced.
[0037] An application program (APP) is also called an application, which refers to a computer program for completing one or more functions. To adapt to different usage scenarios, an electronic device (such as a terminal, a server) can manage the application in response to the user's needs. For example, the terminal uninstalls the deployed application.
[0038] Currently, during the process of the terminal uninstalling the deployed application, the terminal needs to receive the operation instruction input by the user in the application store to uninstall the deployed application, and in response to this operation instruction, uninstall the deployed application.
[0039] However, in the above technical solution, there may be multiple users of the usage terminal, and different users have different uninstallation requirements for the applications already deployed in the terminal, resulting in differences in the management of applications.
[0040] Therefore, how to perform identity authentication during the process of managing applications has become a technical problem to be solved urgently.
[0041] To solve the above problems, the embodiments of the present application provide a method for authenticating the identity of an application. The method for authenticating the identity of an application provided by the embodiments of the present application is applied to the scenario of managing applications on a device. The device to be managed can receive a target operation instruction input by the user through the deployed application store, which is used to indicate the management of a target application, and obtain the identity authentication status of the deployed encrypted application. If the device to be managed determines that the identity authentication status of the encrypted application is that the encrypted application has completed identity authentication, the device to be managed can manage the target application through the application store according to the target operation instruction. That is to say, the device to be managed can determine whether to respond to the user's management operation on the application in the application store according to the identity authentication status of the encrypted application for the user. In this way, in the case of multiple users, the device can determine the management authority of each user for the applications in the device by authenticating the users, reduce the differences in application management, and improve the security of the device.
[0042] Next, the implementation environment of the embodiments of the present application will be introduced.
[0043] As Figure 1 shown, it is a device system architecture diagram provided by the embodiments of the present application. The device system architecture may include: an application store 101, an encrypted application 102, and a memory card 103. Among them, both the application store 101 and the encrypted application 102 are deployed in the device 104 to be managed. The memory card 103 stores preset identity information, and the memory card 103 is a storage component in the device 104 to be managed. The encrypted application 102 can communicate with the application store 101 and the memory card 103 respectively.
[0044] Specifically, the encrypted application 102 can receive the identity information to be verified input by the user, and determine whether the identity information to be verified is the same as the preset identity information in the memory card 103 by obtaining the preset identity information in the memory card 103, thereby authenticating the user. After that, when the encrypted application 102 determines that the verified identity information is different from the preset identity information, the encrypted application 102 can update the identity authentication status of the encrypted application 102 to the status of not having completed identity authentication. Similarly, when the encrypted application 102 determines that the verified identity information is the same as the preset identity information, the encrypted application 102 can update the identity authentication status of the encrypted application 102 to the status of having completed identity authentication.
[0045] The application store 101 can receive management instructions (such as update instructions, uninstall instructions, and install instructions, etc.) input by the user for the application to be managed, and obtain the authentication status of the encrypted application 102. If the authentication status of the encrypted application 102 is the status of incomplete authentication, the application store 101 does not respond to the management instructions input by the user. Similarly, if the authentication status of the encrypted application 102 is the status of complete authentication, the application store 101 manages the application to be managed corresponding to the management instructions input by the user.
[0046] It should be noted that, in the embodiments of the present application, the device to be managed can be a terminal, or the device to be managed can be a server.
[0047] Among them, the terminal can be a device such as a mobile phone, a tablet computer, a desktop type, a laptop, a handheld computer, a notebook computer, an Ultra-mobile Personal Computer (UMPC), a netbook, etc. with transceiver functions. The present application does not impose special restrictions on the specific form of the terminal. It can perform human-computer interaction with the user through one or more of a keyboard, a touchpad, a touch screen, a remote control, voice interaction, or a handwriting device.
[0048] The server can be a single physical server, or it can also be a server cluster composed of multiple servers. Or, the server cluster can also be a distributed cluster. Or, the server can be a cloud server. The embodiments of the present application do not limit the specific implementation manner of the server.
[0049] After introducing the application scenarios and implementation environments of the embodiments of the present application, the method for authenticating the identity of the application provided by the embodiments of the present application will be introduced in detail below in combination with the above implementation environment.
[0050] The methods in the following embodiments can all be implemented in the above application scenarios and implementation environments. The embodiments of the present application will be specifically described below in combination with the accompanying drawings of the specification.
[0051] Figure 2 It is a schematic flowchart of a method for authenticating the identity of an application provided by an embodiment of the present application. As Figure 2 shown, the method may include: S201 - S204.
[0052] S201. The device to be managed obtains a target operation instruction.
[0053] Among them, the device to be managed is deployed with an application store, and the application store includes multiple applications to be managed.
[0054] In a possible implementation manner, the device to be managed can obtain the application to be managed from the server of the application store through the application store.
[0055] In another possible implementation, the device to be managed can manage the applications to be managed deployed in the device to be managed through an application store.
[0056] In the embodiments of the present application, an encryption application is also deployed in the device to be managed. The encryption application includes preset identity information. The device to be managed can determine whether to respond to an operation instruction input by a user using the device to be managed according to the authentication status of the encryption application.
[0057] It should be noted that, in the embodiments of the present application, the authentication status of the encryption application can be that the encryption application has not completed authentication, or the authentication status of the encryption application can be that the encryption application has completed authentication.
[0058] In a possible design, if the authentication status of the encryption application can be that the encryption application has not completed authentication, the device to be managed does not respond to an operation instruction input by a user using the device to be managed.
[0059] In another possible design, if the authentication status of the encryption application can be that the encryption application has completed authentication, the device to be managed responds to an operation instruction input by a user using the device to be managed.
[0060] In the embodiments of the present application, the target operation instruction is used to indicate managing a target application in the application store, and the target application is any application to be managed in the application store.
[0061] In a possible implementation, the device to be managed can receive a target operation instruction input by a user using the device to be managed through the application store.
[0062] S202. In response to the target operation instruction, the device to be managed obtains target status information of the encryption application.
[0063] Wherein, the target status information is used to indicate the authentication status of the encryption application.
[0064] S203. The device to be managed determines whether the target status information is first status information.
[0065] Wherein, the first status information is used to indicate that the encryption application has completed authentication.
[0066] In a possible implementation, the device to be managed can determine whether the target status information is first status information through the application store.
[0067] In some embodiments, if the device to be managed determines that the target status information is first status information, the device to be managed executes S204.
[0068] S204. The device to be managed manages the target application according to the target operation instruction.
[0069] In a possible implementation, the device to be managed can manage the target application through the application store according to the target operation instruction.
[0070] In a possible design, the target operation instruction can be any of the following instructions: the first operation instruction for instructing to update the target application, the second operation instruction for instructing to uninstall the target application, the third operation instruction for instructing to install the target application, the fourth operation instruction for instructing to view the application details of the target application, and the fifth operation instruction for instructing to rate the target application.
[0071] That is to say, the device to be managed can manage the target application in the application store in response to the operation instructions such as updating, uninstalling, installing, viewing the application details, or rating the target application input by the user in the application store.
[0072] The technical solution provided by the above embodiments has at least the following beneficial effects: The device to be managed is deployed with an application store and an encrypted application. The device to be managed can obtain a target operation instruction, which is used to instruct to manage the target application in the application store. Then, the device to be managed can obtain the target status information of the encrypted application in response to the target operation instruction, and the target status information is used to indicate the authentication status of the encrypted application. Next, the device to be managed can determine whether the target status information is the first status information, and the first status information is used to indicate that the encrypted application has completed authentication. If the device to be managed determines that the target status information is the first status information, the device to be managed can manage the target application according to the target operation instruction. That is to say, the device to be managed can determine whether to respond to the user's management operation of the application in the application store according to the authentication status of the encrypted application for the user. In this way, in the case of multiple users, the device can determine the management authority of each user for the application in the device by authenticating the users, reduce the differences in application management, and improve the security of the device.
[0073] In some embodiments, the device to be managed can receive the identity information to be verified input by the user using the device to be managed through the encrypted application, and manage the authentication status of the encrypted application by determining whether the identity information to be verified is the same as the preset identity information.
[0074] In a possible design, the device to be managed includes a memory card storing the preset identity information. In the process of the device to be managed determining whether the identity information to be verified is the same as the preset identity information through the encrypted application, the device to be managed can call the memory card through the encrypted application to obtain the preset identity information, and then determine whether the identity information to be verified is the same as the preset identity information.
[0075] In the embodiments of the present application, as Figure 3 shown, after the device to be managed determines whether the target status information is the first status information (i.e., S203), if the device to be managed determines that the target status information is the second status information, the method may further include: S301 - S302. Wherein, the second status information is used to indicate that the encryption application has not completed authentication.
[0076] S301. The device to be managed obtains the first identity information to be verified.
[0077] In a possible implementation manner, after the device to be managed determines that the target status information is the second status information, the device to be managed may call the encryption application, and through the login interface of the encryption application, receive the first identity information to be verified input by the user using the device to be managed, and then obtain the first identity information to be verified.
[0078] S302. The device to be managed determines whether the first identity information to be verified is the same as the preset identity information.
[0079] In a possible implementation manner, the device to be managed may determine whether the first identity information to be verified is the same as the preset identity information through the encryption application.
[0080] In some embodiments, if the device to be managed determines that the first identity information to be verified is the same as the preset identity information, the device to be managed calls the application store and executes S204.
[0081] In other embodiments, if the device to be managed determines that the first identity information to be verified is not the same as the preset identity information, the device to be managed does not respond to the target operation instruction.
[0082] It can be understood that the device to be managed stores the preset identity information. The device to be managed may, when determining that the target status information is the second status information, obtain the first identity information to be verified and determine whether the first identity information to be verified is the same as the preset identity information. The second status information is used to indicate that the encryption application has not completed authentication. If the device to be managed determines that the first identity information to be verified is the same as the preset identity information, the device to be managed may manage the target application according to the target operation instruction. That is to say, the device to be managed may, in the case where the encryption application has not authenticated the user, determine whether to respond to the user's management operation of the application in the application store by comparing whether the identity information input by the user is the same as the identity information stored locally. In this way, the device can, in the case where the user has not completed authentication in advance, perform timely verification according to the identity information stored locally and the identity information input by the user, determine the user's management authority for the application in the device, and improve the operability of authentication.
[0083] In some embodiments, such as Figure 4 shown, before the device to be managed obtains the target operation instruction (i.e., S201), the method may further include: S401 - S404.
[0084] S401. The device to be managed obtains a target operation instruction.
[0085] Wherein, the target operation instruction is used to instruct to operate the device to be managed.
[0086] Exemplarily, the target operation instruction may be an instruction to instruct the device to be managed to power on.
[0087] In a possible implementation manner, the device to be managed may receive an operation instruction input by a user using the device to be managed to instruct to operate the device to be managed, and generate a target operation instruction.
[0088] S402. The device to be managed obtains second identity information to be verified in response to the target operation instruction.
[0089] In a possible implementation manner, the device to be managed may, in response to the target operation instruction, call an encryption application, and receive, through the login interface of the encryption application, second identity information to be verified input by a user using the device to be managed.
[0090] S403. The device to be managed determines whether the second identity information to be verified is the same as the preset identity information.
[0091] It should be noted that for the process of the device to be managed determining whether the second identity information to be verified is the same as the preset identity information, reference may be made to the description of the device to be managed determining whether the first identity information to be verified is the same as the preset identity information in the above embodiments, which will not be elaborated here.
[0092] In some embodiments, if the device to be managed determines that the second identity information to be verified is the same as the preset identity information, the device to be managed executes S404.
[0093] S404. The device to be managed updates the target status information to the first status information.
[0094] It can be understood that the user can log in to the application store for use without registering in the application store. When the device to be managed is powered on, the encryption application is launched to authenticate the user and obtain the authentication success information. In this way, the scope of users using the device can be controlled to a great extent, and the security and confidentiality of user data can be ensured.
[0095] In other embodiments, if the device to be managed determines that the second identity information to be verified is not the same as the preset identity information, the device to be managed updates the target status information to the second status information.
[0096] The following introduces the authentication method of the application provided by the embodiments of the present application in combination with specific examples, as Figure 5 shown, including:
[0097] Step 1: The device to be managed runs the client of this system (i.e., the application store).
[0098] Step 2: The device to be managed determines whether the encrypted application has been logged in (i.e., S203).
[0099] In some embodiments, if the device to be managed determines that the encrypted application has been logged in, it responds to the operation instruction input by the user in the client of this system (i.e., S204).
[0100] In other embodiments, if the device to be managed determines that the encrypted application has not been logged in, the device to be managed executes Step 3.
[0101] Step 3: The device to be managed calls the encrypted application and jumps to the login interface.
[0102] Step 4: The device to be managed receives the identity information to be verified through the encrypted application.
[0103] Step 5: The device to be managed verifies the identity information to be verified through the encrypted application to determine whether to log in to the encrypted application.
[0104] In some embodiments, if the device to be managed determines through the encrypted application that the identity information to be verified passes the verification, the device to be managed determines that the encrypted application has logged in successfully and executes Step 1 to respond to the operation instruction input by the user in the client of this system.
[0105] That is to say, after the encrypted application logs in successfully, the device to be managed can view all the applications that can be downloaded, updated, and uninstalled in this system, and manage the applications at will according to the user's needs; it can also set this system according to personal preferences, such as automatic download and update, automatically deleting the installation package after completion of installation, setting the download location, etc.
[0106] In other embodiments, if the device to be managed determines through the encrypted application that the identity information to be verified fails the verification, the device to be managed determines that the encrypted application has logged in failed and calls the client of this system without responding to the operation instruction input by the user in the client of this system.
[0107] It can be understood that when the device to be managed opens this system, it first invokes the terminal encrypted application to determine whether it has logged in. If it has not logged in, it first jumps to the encrypted application login interface. At this time, when reopening the login page of this system and querying that the terminal encrypted application has logged in successfully, this system can log in successfully. This ensures that the terminal cannot randomly download, update, or uninstall an application, protecting the user's data.
[0108] The above mainly introduces the solution provided by the embodiments of the present application from the perspective of computer devices. It can be understood that in order to implement the above functions, the computer device includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that in combination with the authentication method steps of each example of the application described in the embodiments disclosed in the present application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described function for each specific application, but such implementation should not be considered to exceed the scope of the present application.
[0109] The embodiments of the present application also provide an application authentication device. The application authentication device can be a computer device, or the CPU in the above computer device, or the processing module in the above computer device for authenticating the identity of the application, or the client in the above computer device for authenticating the identity of the application.
[0110] The embodiments of the present application can divide the application authentication device into functional modules or functional units according to the above method examples. For example, each functional module or functional unit can be divided corresponding to each function, or two or more functions can be integrated into a processing module. The above integrated module can be implemented in the form of hardware, or in the form of a software functional module or functional unit. Among them, the division of modules or units in the embodiments of the present application is illustrative, only a logical function division, and there can be other division methods in actual implementation.
[0111] As Figure 6 shown, it is a schematic structural diagram of an application authentication device provided by an embodiment of the present application. The application authentication device is applied to the device to be managed and is used to execute Figure 2 、 Figure 3 or Figure 4 the application authentication method shown. The application authentication device 600 may include: an acquisition module 601 and a processing module 602.
[0112] The acquisition module 601 is used to acquire a target operation instruction, and the target operation instruction is used to indicate managing a target application in an application store. The acquisition module 601 is further used to, in response to the target operation instruction, acquire target status information of the encrypted application, and the target status information is used to indicate the authentication status of the encrypted application. The processing module 602 is used to, if the target status information is the first status information, manage the target application according to the target operation instruction, and the first status information is used to indicate that the encrypted application has completed authentication.
[0113] Optionally, the device to be managed stores preset identity information. The obtaining module 601 is further configured to, if the target status information is the second status information, obtain first identity information to be verified, where the second status information is used to indicate that the encryption application has not completed identity verification. The processing module 602 is further configured to determine whether the first identity information to be verified is the same as the preset identity information. Specifically, the processing module 602 is configured to, if the identity information to be verified is the same as the preset identity information, manage the target application according to the target operation instruction.
[0114] Optionally, the obtaining module 601 is further configured to obtain a target operation instruction, where the target operation instruction is used to indicate running the device to be managed. The obtaining module 601 is further configured to, in response to the target operation instruction, obtain second identity information to be verified. The processing module 602 is further configured to determine whether the second identity information to be verified is the same as the preset identity information. The processing module 602 is further configured to, if the second identity information to be verified is the same as the preset identity information, update the target status information to the first status information.
[0115] Optionally, the processing module 602 is further configured to, if the second identity information to be verified is not the same as the preset identity information, update the target status information to the second status information.
[0116] Optionally, the target operation instruction is any one of the following instructions: a first operation instruction for indicating to update the target application, a second operation instruction for indicating to uninstall the target application, and a third operation instruction for indicating to install the target application.
[0117] Figure 7 FIG. is a schematic hardware structure diagram of an identity authentication device for an application shown according to an exemplary embodiment. The identity authentication device for the application may include a processor 702, and the processor 702 is configured to execute application program code to implement the identity authentication method for the application in the present application.
[0118] The processor 702 may be a CPU, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the solution of the present application.
[0119] As Figure 7 shown, the identity authentication device for the application may further include a memory 703. The memory 703 is used to store the application program code for executing the solution of the present application and is controlled by the processor 702 to execute.
[0120] The memory 703 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 703 can exist independently and be connected to the processor 702 through the bus 704. The memory 703 can also be integrated with the processor 702.
[0121] As Figure 7 shown, the authentication device of the application can further include a communication interface 701, where the communication interface 701, the processor 702, and the memory 703 can be coupled to each other, for example, through the bus 704. The communication interface 701 is used for information interaction with other devices, for example, to support information interaction between the authentication device of the application and other devices.
[0122] It should be noted that Figure 7 the device structure shown in Figure 7 does not constitute a limitation on the authentication device of the application. In addition to
[0123] the components shown, the authentication device of the application can include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.
[0123] In actual implementation, the functions implemented by the processing module 602 can all be implemented by Figure 7 the processor 702 shown calling the program code in the memory 703.
[0124] The present application also provides a computer-readable storage medium, on which instructions are stored. When the instructions in the computer-readable storage medium are executed by a processor of a computer device, the computer can perform the authentication of the application provided in the above-described embodiments. For example, the computer-readable storage medium may be a memory 703 including instructions, and the above instructions may be executed by a processor 702 of the computer device to complete the above method. Optionally, the computer-readable storage medium may be a non-transitory computer-readable storage medium. For example, the non-transitory computer-readable storage medium may be ROM, RAM, CD-ROM, magnetic tape, floppy disk, and optical data storage devices, etc.
[0125] Figure 8 Exemplarily shown is a conceptual partial view of a computer program product provided by an embodiment of the present application. The computer program product includes a computer program for executing a computer process on a computing device.
[0126] In one embodiment, the computer program product is provided using a signal-bearing medium 800. The signal-bearing medium 800 may include one or more program instructions, which when run by one or more processors can provide the functions or partial functions described above for Figure 2 、 Figure 3 or Figure 4 described. Thus, for example, referring to the embodiment shown in Figure 2 , one or more features of S201 to S204 may be borne by one or more instructions associated with the signal-bearing medium 800. In addition, Figure 8 the program instructions in also describe example instructions.
[0127] In some examples, the signal-bearing medium 800 may include a computer-readable medium 801, such as but not limited to, a hard disk drive, a compact disc (CD), a digital video disc (DVD), a digital tape, a memory, a read-only memory (ROM), or a random access memory (RAM), etc.
[0128] In some embodiments, the signal-bearing medium 800 may include a computer-recordable medium 802, such as but not limited to, a memory, a read / write (R / W) CD, R / W, DVD, etc.
[0129] In some embodiments, the signal-bearing medium 800 may include a communication medium 803, such as but not limited to, a digital and / or analog communication medium (e.g., an optical fiber cable, a waveguide, a wired communication link, a wireless communication link, etc.).
[0130] The signal-bearing medium 800 can be communicated by a communication medium 803 in a wireless form. One or more program instructions can be, for example, computer-executable instructions or logic-implemented instructions.
[0131] In some examples, such as for Figure 6 the authentication device of the described application can be configured to provide various operations, functions, or actions in response to one or more program instructions in the computer-readable medium 801, the computer-recordable medium 802, and / or the communication medium 803.
[0132] From the description of the above embodiments, those skilled in the art can clearly understand that, for the convenience and conciseness of description, only the above division of each functional module is used as an example. In actual applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
[0133] In several embodiments provided in the present application, it should be understood that the disclosed device and method can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of modules or units is only a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection to each other can be through some interfaces. The indirect coupling or communication connection of the device or unit can be in an electrical, mechanical or other form.
[0134] The units described as separate components may or may not be physically separated. The components displayed as units can be one physical unit or multiple physical units, that is, they can be in one place, or they can be distributed to multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0135] In addition, each functional unit in the various embodiments of the present application can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.
[0136] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of the present application, in essence, or the part that contributes to the prior art, or all or part of the full classification of this technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions for causing a device (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the methods of the various embodiments of the present application. The aforementioned storage medium includes various media that can store program codes, such as USB flash drives, mobile hard disks, ROM, RAM, magnetic disks, or optical discs.
[0137] The above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.
Claims
1. An identity authentication method for an application, characterized in that: Applied to a device to be managed, the device to be managed is deployed with an application store and an encryption application, the method includes: Obtaining a target operation instruction, wherein the target operation instruction is used to instruct management of a target application in the application store; In response to the target operation instruction, acquiring target state information of the encryption application, the target state information being used to indicate an identity authentication state of the encryption application; If the target status information is first status information, the target application is managed according to the target operation instruction, and the first status information is used to indicate that the encryption application has completed identity authentication.
2. The method according to claim 1, characterized in that The device to be managed stores preset identity information. After acquiring the target state information of the encryption application, the method further includes: If the target state information is the second state information, obtaining the first identity information to be verified, wherein the second state information is used to indicate that the encryption application has not completed identity authentication; Determining whether the first identity information to be verified is the same as the preset identity information; Managing the target application according to the target operation instruction also includes: If the identity information to be verified is the same as the preset identity information, the target application is managed according to the target operation instruction.
3. The method according to claim 2, characterized in that Before obtaining the target operation instruction, the method further includes: Obtaining a target operation instruction, wherein the target operation instruction is used to instruct to operate the device to be managed; In response to the target execution instruction, obtaining second identity information to be verified; Determining whether the second identity information to be verified is the same as the preset identity information; If the second identity information to be verified is the same as the preset identity information, the target state information is updated to the first state information.
4. The method according to claim 3, characterized in that The method further comprises: If the second identity information to be verified is different from the preset identity information, the target state information is updated to the second state information.
5. The method according to any one of claims 1 to 4, characterized in that The target operation instruction is any one of the following instructions: a first operation instruction for instructing to update the target application, a second operation instruction for instructing to uninstall the target application, and a third operation instruction for instructing to install the target application.
6. An identity verification device for an application, characterized in that: Applied to a device to be managed, the device to be managed is deployed with an application store and an encryption application, and the device includes: An acquisition module, used for acquiring a target operation instruction, wherein the target operation instruction is used for instructing to manage a target application in the application store; The acquisition module is further used to acquire target state information of the encryption application in response to the target operation instruction, wherein the target state information is used to indicate the identity authentication state of the encryption application; A processing module is used to manage the target application according to the target operation instruction if the target status information is first status information, and the first status information is used to indicate that the encryption application has completed identity authentication.
7. The device according to claim 6, characterized in that The device to be managed stores preset identity information; The acquisition module is further configured to acquire first identity information to be verified if the target state information is second state information, wherein the second state information is used to indicate that the encryption application has not completed identity authentication; The processing module is further used to determine whether the first identity information to be verified is the same as the preset identity information; The processing module is specifically configured to manage the target application according to the target operation instruction if the identity information to be verified is the same as the preset identity information.
8. The device according to claim 7, characterized in that The acquisition module is further used to acquire a target operation instruction, where the target operation instruction is used to instruct the operation of the device to be managed; The acquisition module is further used to acquire second identity information to be verified in response to the target running instruction; The processing module is further used to determine whether the second identity information to be verified is the same as the preset identity information; The processing module is further configured to update the target state information to the first state information if the second identity information to be verified is the same as the preset identity information.
9. The device according to claim 8, characterized in that The processing module is further configured to update the target state information to the second state information if the second identity information to be verified is different from the preset identity information.
10. The device according to any one of claims 6 to 9, characterized in that: The target operation instruction is any one of the following instructions: a first operation instruction for instructing to update the target application, a second operation instruction for instructing to uninstall the target application, and a third operation instruction for instructing to install the target application.
11. An identity verification device for an application, characterized in that: include: Processor and memory; The processor is coupled to the memory; The memory is used to store one or more programs, and the one or more programs include computer-executable instructions. When the authentication device of the application is running, the processor executes the computer-executable instructions stored in the memory to enable the authentication device of the application to perform the authentication method of the application as described in any one of claims 1-5.
12. A computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium, characterized in that: When a computer executes the instructions, the computer executes the identity authentication method of the application as described in any one of claims 1-5.