CN113225332B - User login management method, device, terminal equipment and storage medium - Google Patents
User login management method, device, terminal equipment and storage medium Download PDFInfo
- Publication number
- CN113225332B CN113225332B CN202110482074.3A CN202110482074A CN113225332B CN 113225332 B CN113225332 B CN 113225332B CN 202110482074 A CN202110482074 A CN 202110482074A CN 113225332 B CN113225332 B CN 113225332B
- Authority
- CN
- China
- Prior art keywords
- user
- account information
- target application
- state
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application is applicable to the technical field of information security, and provides a user login management method, a device, terminal equipment and a storage medium, wherein the method comprises the following steps: responding to a user login instruction received in a target application, and carrying out third party user detection on account information in the user login instruction; if the user represented by the account information is a user of a preset third-party application, detecting whether the user represented by the account information is a user of a target application; if the user represented by the account information is a user in the target application, determining a user state of the account information in the target application, and executing user login operation on the account information according to the user state. According to the application, whether the user represented by the account information is the user in the target application or not is detected, so that the account information can be uniformly managed in the target application, and the phenomenon of low user information management efficiency caused by directly logging in the target application through the corresponding account in the third party application is prevented.
Description
Technical Field
The present application relates to the field of information security, and in particular, to a user login management method, device, terminal device, and storage medium.
Background
With the development of technology, a user system of a system needs to be managed while the system is developed. However, as the enterprise scale increases, the number of users of the system increases; the user management system for establishing the system is also more and more complex, and the maintenance of the user management system is also more and more troublesome. Thus, more and more systems log in by interfacing with third party applications.
In the related art, after the third party application is docked, the login of the target application is directly realized through the corresponding account in the third party application, so that the account information of the user cannot be effectively managed in the target application.
Disclosure of Invention
In view of the above, the embodiments of the present application provide a method, an apparatus, a terminal device, and a storage medium for user login management, so as to solve the problem in the prior art that account information of a user cannot be effectively managed in a target application.
A first aspect of an embodiment of the present application provides a user login management method, including:
responding to a user login instruction received in a target application, carrying out third party user detection on account information in the user login instruction, wherein the third party user detection is used for detecting whether a user represented by the account information is a user of a preset third party application;
if the user represented by the account information is the user of the third party application, detecting whether the user represented by the account information is the user of the target application;
if the user represented by the account information is the user in the target application, determining the user state of the account information in the target application, and executing user login operation on the account information according to the user state.
Further, the determining the user state of the account information in the target application includes:
inquiring risk assessment data of the account information in the third party application, and determining a user state of the account information in the target application according to the risk assessment data; or (b)
And inquiring the registration information of the account information in the third-party application, and determining the user state of the account information in the target application according to the inquired registration information.
Further, after detecting whether the user represented by the account information is the user in the target application, the method further includes:
if the account information is not the user in the target application, a first registration prompt is sent to a sending end of the user login instruction;
and if registration information aiming at the first registration prompt is received, user registration is carried out on the account information in the target application according to the received registration information.
Further, after the third party user detection is performed on the account information in the user login instruction, the method further includes:
if the third party user of the account information detects that the third party user is unqualified, a second registration prompt is sent to the sending end of the user login instruction;
and if the registration information aiming at the second registration prompt is received, registering the account information in the third party application according to the received registration information.
Further, the executing the user login operation on the account information according to the user state includes:
if the user state is a normal state, user login is carried out in the target application according to the account information;
if the user state is the state to be checked or updated, sending a prompt to be checked to a sending end of the user login instruction;
if the user state is a frozen state, a user freezing prompt and an information updating prompt are sent to a sending end of the user login instruction;
and if the user state is the audit failed state, sending an audit failed prompt and an information updating prompt to a sending end of the user login instruction.
Further, after the user registration is performed on the account information in the target application according to the received registration information, the method further includes:
setting the user state of the account information in the target application as a to-be-checked state, and performing information checking on registration information corresponding to the account information according to a preset checking standard;
if the registration information corresponding to the account information passes the verification, setting the application authority of the account information, and setting the user state of the account information in the target application as a normal state;
and if the registration information auditing corresponding to the account information is not passed, setting the user state of the account information in the target application as an auditing not-passed state.
Further, the third party user detection on account information in the user login instruction includes:
sending a verification instruction to the third party application according to the account information, and receiving a verification result of the third party application aiming at the verification instruction, wherein the verification instruction is used for indicating the third party application to carry out account verification on the account information;
if the account verification of the account information is judged to be qualified according to the verification result, judging that the third party user of the account information is qualified;
and if the account verification of the account information is judged to be unqualified according to the verification result, judging that the third party user of the account information is unqualified.
A second aspect of an embodiment of the present application provides a user login management apparatus, including:
the third party user detection unit is used for responding to a user login instruction received in a target application, carrying out third party user detection on account information in the user login instruction, and detecting whether a user represented by the account information is a preset user of the third party application or not;
the target application user detection unit is used for detecting whether the user represented by the account information is the user of the target application or not if the user represented by the account information is the user of the third party application;
and the user state determining unit is used for determining the user state of the account information in the target application if the user represented by the account information is the user in the target application, and executing user login operation on the account information according to the user state.
A third aspect of the embodiments of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the terminal device, where the processor implements the steps of the user login management method provided in the first aspect when the processor executes the computer program.
A fourth aspect of the embodiments of the present application provides a computer-readable storage medium storing a computer program which, when executed by a processor, implements the steps of the user login management method provided in the first aspect.
The user login management method, the device, the terminal equipment and the storage medium provided by the embodiment of the application have the following beneficial effects: by detecting whether the user represented by the account information is a user in a preset third party application or not, the accuracy of user login management is improved, by detecting whether the user represented by the account information is a user in a target application or not, the account information can be effectively and uniformly managed in the target application, the phenomenon of low user information management efficiency caused by the fact that the user login in the target application is realized by directly corresponding accounts in the third party application is prevented, the accuracy of user login operation corresponding to the account information is improved by determining the user state of the account information in the target application, the user login management can be effectively carried out based on different state dimensions based on different user states, and the accuracy of user login management is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of a user login management method according to an embodiment of the present application;
FIG. 2 is a flowchart illustrating a method for user login management according to another embodiment of the present application;
FIG. 3 is a flowchart illustrating a method for user login management according to another embodiment of the present application;
fig. 4 is a block diagram of a user login management device according to an embodiment of the present application;
fig. 5 is a block diagram of a terminal device according to an embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
The user login management method according to the embodiment of the present application may be executed by a control device or a terminal (hereinafter referred to as a "mobile terminal").
Referring to fig. 1, fig. 1 shows a flowchart of an implementation of a user login management method according to an embodiment of the present application, including:
and step S10, responding to a user login instruction received in a target application, and carrying out third-party user detection on account information in the user login instruction.
The third party user detects whether the user represented by the account information is a user of a preset third party application or not, the preset third party application can be set according to the requirement of the user, in the step, the account information in a user login instruction can be called for account login, if the account login operation of the account information is successful in the login interface of the preset third party application, the user represented by the account information is judged to be the user of the preset third party application, and if the account login operation of the account information is unsuccessful in the login interface of the preset third party application, the user represented by the account information is judged not to be the user of the preset third party application. Further, in this step, a plurality of different preset third party applications may be set, and by respectively calling different preset login interfaces of the third party applications, whether the user represented by the account information is a user of the preset third party application is determined, and if the account information is successfully logged in by an account login operation in any of the called login interfaces, whether the user represented by the account information is a user of the preset third party application is determined.
Optionally, in this step, a user list of a preset third party application may be further obtained, the account information is matched with the obtained user list, if the account information is matched with the obtained user list, it is determined that the user represented by the account information is a user of the preset third party application, and account information corresponding to different users in the preset third party application is stored in the user list.
In the step, third party user detection is performed on account information in a user login instruction to detect whether a user represented by the account information is a user of a preset third party application, and whether the account information in the user login instruction can be logged in to the target application is judged based on judgment of whether the user represented by the account information is the user of the preset third party application.
Further, in this step, the third party user detection on account information in the user login instruction includes:
sending a verification instruction to the third party application according to the account information, and receiving a verification result of the third party application for the verification instruction, wherein the verification instruction is used for indicating a preset third party application to perform account verification on the account information;
if the account number verification of the account number information is judged to be qualified according to the verification result, judging that the third party user of the account number information is detected to be qualified, wherein if the third party user of the account number information is judged to be detected to be qualified, the user represented by the account number information is a user in a preset third party application;
if the account verification of the account information is judged to be unqualified according to the verification result, the detection of the third party user of the account information is judged to be unqualified, wherein if the detection of the third party user of the account information is judged to be unqualified, the user represented by the account information is not the user in the preset third party application.
And step S20, if the user represented by the account information is the user of the third party application, detecting whether the user represented by the account information is the user of the target application.
If the user represented by the account information is a user of a preset third party application, determining that the account information has login permission for a target application, and determining whether normal login can be performed in the target application based on the account information by detecting whether the user represented by the account information is a user of the target application.
In the step, account login can be performed through a login interface of the target application and based on account information in a user login instruction, if the account login operation of the account information is successful in the login interface of the target application, the user represented by the account information is judged to be the user of the target application, and if the account login operation of the account information is unsuccessful in the login interface of the target application, the user represented by the account information is judged not to be the user of the target application.
Optionally, in this step, a user list of the target application may be further acquired, and the account information may be matched with the acquired user list, so as to determine whether the user represented by the account information is a user of the target application.
Further, in this step, after detecting whether the user represented by the account information is the user in the target application, the method further includes:
if the account information is not the user in the target application, a first registration prompt is sent to the sending end of the user login instruction, wherein a first registration address is stored in the first registration prompt and used for pointing to a user registration page corresponding to the target application, and the first registration prompt is used for prompting the user corresponding to the user login instruction to register the user in the target application;
and if the registration information aiming at the first registration prompt is received, carrying out user registration on the account information in the target application according to the received registration information, wherein the login of the account information in the target application is ensured by carrying out user registration on the account information in the target application according to the received registration information.
Optionally, in the step, the user account is set for the received registration information, and the set user account and the received registration information are correspondingly stored in a user list of the target application, so as to achieve the user registration effect of the received registration information.
Further, in this step, if the user represented by the account information is a user of the third party application and it is determined that the account information is the first user login to the application information, a first registration prompt is sent to the sending end of the user login instruction.
Step S30, if the user represented by the account information is the user in the target application, determining the user state of the account information in the target application, and executing user login operation on the account information according to the user state.
By determining the user state of the account information in the target application, different user login operations can be effectively executed on the account information according to different user states, accuracy of the account information corresponding to the user login operations is improved, user login management can be effectively performed on the basis of different state dimensions based on different user states, and accuracy of the user login management is improved.
Optionally, in this step, after the third party user detection is performed on account information in the user login instruction, the method further includes:
if the third party user of the account information detects that the user is not qualified, a second registration prompt is sent to the sending end of the user login instruction, wherein the second registration prompt stores a second registration address, the second registration address is used for pointing to a user registration page corresponding to the preset third party application, and the second registration prompt is used for prompting the user corresponding to the user login instruction to register the user in the preset third party application;
and if the registration information aiming at the second registration prompt is received, registering the account information in the third party application according to the received registration information.
Further, in this step, after the user registration is performed on the account information in the target application according to the received registration information, the method further includes:
setting a user state of the account information in the target application as a to-be-checked state, and performing information checking on registration information corresponding to the account information according to a preset checking standard, wherein the user state of the account information in the target application is set as the to-be-checked state to prompt a user that the registration information corresponding to the account information also needs to be checked, and optionally, the preset checking standard can be set according to requirements, and the preset checking standard is used for checking whether the registration information corresponding to the account information is accurate;
if the registration information corresponding to the account information passes the verification, setting the application permission of the account information, and setting the user state of the account information in the target application to be a normal state, wherein the application operation of the account information corresponding to the user in the target application is ensured by setting the application permission of the account information, and optionally, in the step, the permission level of the registration information corresponding to the account information can be confirmed, and the application permission of the account information is set according to the determined permission level.
If the registration information corresponding to the account information is not approved, setting the user state of the account information in the target application as an approved failed state, wherein the user can be effectively reminded that the registration information corresponding to the account information is not approved by setting the user state of the account information in the target application as an approved failed state.
In this embodiment, by detecting the account information in the user login instruction by using the third party, it can be effectively detected whether the user represented by the account information is a user in a preset third party application, so that the accuracy of user login management is improved, by detecting whether the user represented by the account information is a user in a target application, the management of the account information can be effectively and uniformly performed in the target application, the phenomenon of low user information management efficiency caused by directly realizing the login in the target application through the corresponding account in the third party application is prevented, the accuracy of the account information corresponding to the user login operation is improved by determining the user state of the account information in the target application, and the user login management accuracy can be effectively improved based on different state dimensions based on different user states.
Referring to fig. 2, fig. 2 is a flowchart illustrating an implementation of a user login management method according to another embodiment of the present application. Compared to the embodiment of fig. 1, the user login management method provided in this embodiment is used to further refine step S30 in the embodiment of fig. 1, and includes:
step S31, querying risk assessment data and/or registration information of the account information in the third party application.
And respectively matching the account identification with a risk evaluation database and a registration database in a preset third party application to obtain corresponding risk evaluation data and registration information of the account information in the preset third party application, wherein corresponding relations between different account identifications and corresponding risk evaluation data and registration information are respectively stored in the risk evaluation database and the registration database.
In this step, the account identifier may be a name of the user in the account information, a contact way of the user, or an account of the user, where the risk assessment data stores a login record and an operation record of the account information in a preset third party application, and the login record stores a login address and a login time of the account information in the preset third party application.
And step S32, determining the user state of the account information in the target application according to the queried risk assessment data and/or the registration information.
The risk level of the account information is determined according to the queried risk assessment data and/or registration information, and the user state of the account information in the target application is determined according to the determined risk level.
In the step, aiming at the queried risk assessment data, acquiring the login times of account information in the risk assessment data within a preset time, matching the acquired login times with a risk assessment table to obtain the risk grade of the account information, and matching the risk grade of the account information with a state lookup table to obtain the user state of the account information in a target application, wherein the state lookup table stores the corresponding relations between different risk grades and corresponding user states, and the risk assessment table stores the corresponding relations between different login times and corresponding risk grades.
Preferably, in this step, if there is an abnormal address in the login address of the account information in the risk assessment data, the risk level of the account information is increased according to a level threshold, and the level threshold may be set according to requirements, for example, the level threshold may be set to level 1, level 2, level 3, or the like.
Optionally, for the queried registration information, determining the risk level of the account information according to the number of the abnormal information in the registration information by analyzing whether the abnormal information exists in the registration information, and matching the risk level of the account information with a state query table to obtain the user state of the account information in the target application.
In this embodiment, by querying risk assessment data and/or registration information of account information in a preset third party application, the risk level of the account information can be effectively determined, the user state of the account information in a target application can be effectively determined based on the risk level of the account information, the accuracy of user login operation corresponding to the account information is improved based on the user state of the account information in the target application, user login management can be effectively performed based on different state dimensions based on different user states, and the accuracy of user login management is improved.
Referring to fig. 3, fig. 3 is a flowchart illustrating an implementation of a user login management method according to another embodiment of the present application. Compared to the embodiment of fig. 2, the user login management method provided in this embodiment is used to further refine step S30 in the embodiment of fig. 2, and includes:
and step S33, if the user state is a normal state, user login is performed in the target application according to the account information.
If the user state is normal, it is determined that the account information is normally used in the target application, so that the user logs in the target application directly according to the account information.
And step S34, if the user state is a state to be checked or an updated state, sending a prompt to be checked to a sending end of the user login instruction.
If the user state is the to-be-checked state or the updated state, judging that checking is required for the account information or the updated account information, and prompting the user to wait for checking by sending a to-be-checked prompt to a sending end of the user login instruction.
Optionally, in the step, for a user of any account information in the target application, when it is detected that the account information is updated in the target application, after the user completes updating the registration information of the account information, the state of the account information in the target application is set to be an updated state.
And step S35, if the user state is a frozen state, a user freezing prompt and an information updating prompt are sent to a sending end of the user login instruction.
If the user state is a frozen state, judging that the account information has abnormal phenomenon, wherein the account information has no login permission for a target application, and prompting the user to update the registration information of the account information by sending a user freezing prompt and an information updating prompt to a sending end of a user login instruction.
And step S36, if the user state is the audit failed state, sending an audit failed prompt and an information update prompt to a sending end of the user login instruction.
If the user state is an audit failed state, an audit failed prompt and an information updating prompt are sent to a sending end of the user login instruction to prompt that the registration information of the user account information fails audit, and information updating operation of the user on the registration information is facilitated.
In the embodiment, the normal state, the to-be-checked state, the updated state, the frozen state and the checked failed state of the account information are set in the target application, so that the user login operation on the target application is managed in a multi-dimensional mode, and the accuracy of user login management is improved.
Referring to fig. 4, fig. 4 is a block diagram illustrating a user login management device 100 according to an embodiment of the application. The user login management apparatus 100 in this embodiment includes units for executing the steps in the embodiments corresponding to fig. 1, 2, and 3. Refer specifically to fig. 1, fig. 2, fig. 3, and the related descriptions in the embodiments corresponding to fig. 1, fig. 2, fig. 3. For convenience of explanation, only the portions related to the present embodiment are shown. Referring to fig. 4, the user login management apparatus 100 includes: a third party user detection unit 10, a target application user detection unit 11, and a user status determination unit 12, wherein:
and the third party user detection unit 10 is configured to respond to a user login instruction received in a target application, perform third party user detection on account information in the user login instruction, and detect whether a user represented by the account information is a user of a preset third party application.
Wherein the third party detection unit 10 is further configured to: sending a verification instruction to the third party application according to the account information, and receiving a verification result of the third party application aiming at the verification instruction, wherein the verification instruction is used for indicating the third party application to carry out account verification on the account information;
if the account verification of the account information is judged to be qualified according to the verification result, judging that the third party user of the account information is qualified;
and if the account verification of the account information is judged to be unqualified according to the verification result, judging that the third party user of the account information is unqualified.
And the target application user detection unit 11 is configured to detect whether the user represented by the account information is a user of the target application if the user represented by the account information is a user of the third party application.
And the user state determining unit 12 is configured to determine a user state of the account information in the target application if the user represented by the account information is a user in the target application, and perform a user login operation on the account information according to the user state.
Wherein the user status determination unit 12 is further configured to: inquiring risk assessment data of the account information in the third party application, and determining a user state of the account information in the target application according to the risk assessment data; or (b)
And inquiring the registration information of the account information in the third-party application, and determining the user state of the account information in the target application according to the inquired registration information.
Optionally, the user state determining unit 12 is further configured to: if the user state is a normal state, user login is carried out in the target application according to the account information;
if the user state is the state to be checked or updated, sending a prompt to be checked to a sending end of the user login instruction;
if the user state is a frozen state, a user freezing prompt and an information updating prompt are sent to a sending end of the user login instruction;
and if the user state is the audit failed state, sending an audit failed prompt and an information updating prompt to a sending end of the user login instruction.
Optionally, the user login management device 100 further includes:
a registration prompt unit 13, configured to send a first registration prompt to a sending end of the user login instruction if the account information is not the user in the target application;
and if registration information aiming at the first registration prompt is received, user registration is carried out on the account information in the target application according to the received registration information.
Optionally, the registration prompting unit 13 is further configured to: if the third party user of the account information detects that the third party user is unqualified, a second registration prompt is sent to the sending end of the user login instruction;
and if the registration information aiming at the second registration prompt is received, registering the account information in the third party application according to the received registration information.
The state setting unit 14 is configured to set a user state of the account information in the target application as a state to be checked, and perform information checking on registration information corresponding to the account information according to a preset checking standard;
if the registration information corresponding to the account information passes the verification, setting the application authority of the account information, and setting the user state of the account information in the target application as a normal state;
and if the registration information auditing corresponding to the account information is not passed, setting the user state of the account information in the target application as an auditing not-passed state.
In this embodiment, by detecting the account information in the user login instruction by using the third party, it can be effectively detected whether the user represented by the account information is a user in a preset third party application, so that the accuracy of user login management is improved, by detecting whether the user represented by the account information is a user in a target application, the management of the account information can be effectively and uniformly performed in the target application, the phenomenon of low user information management efficiency caused by directly realizing the login in the target application through the corresponding account in the third party application is prevented, the accuracy of the account information corresponding to the user login operation is improved by determining the user state of the account information in the target application, and the user login management accuracy can be effectively improved based on different state dimensions based on different user states.
Fig. 5 is a block diagram of a terminal device 2 according to another embodiment of the present application. As shown in fig. 5, the terminal device 2 of this embodiment includes: a processor 20, a memory 21 and a computer program 22 stored in said memory 21 and executable on said processor 20, for example a program of a user login management method. The steps in the embodiments of the above-described respective user login management methods are implemented when the processor 20 executes the computer program 23, for example, S10 to S30 shown in fig. 1, S31 to S32 shown in fig. 2, or S33 to S36 shown in fig. 3. Alternatively, the processor 20 may implement the functions of each unit in the embodiment corresponding to fig. 4, for example, the functions of the units 10 to 14 shown in fig. 4, when executing the computer program 22, and the detailed description of the embodiment corresponding to fig. 4 will be referred to herein, which is omitted.
Illustratively, the computer program 22 may be partitioned into one or more units that are stored in the memory 21 and executed by the processor 20 to complete the present application. The one or more units may be a series of computer program instruction segments capable of performing a specific function for describing the execution of the computer program 22 in the terminal device 2. For example, the computer program 22 may be divided into a third party user detection unit 10, a target application user detection unit 11, a user status determination unit 12, a registration prompt unit 13 and a status setting unit 14, each unit functioning specifically as described above.
The terminal device may include, but is not limited to, a processor 20, a memory 21. It will be appreciated by those skilled in the art that fig. 5 is merely an example of the terminal device 2 and does not constitute a limitation of the terminal device 2, and may include more or less components than illustrated, or may combine certain components, or different components, e.g., the terminal device may further include an input-output device, a network access device, a bus, etc.
The processor 20 may be a central processing unit (Central Processing Unit, CPU), other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 21 may be an internal storage unit of the terminal device 2, such as a hard disk or a memory of the terminal device 2. The memory 21 may be an external storage device of the terminal device 2, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the terminal device 2. Further, the memory 21 may also include both an internal storage unit and an external storage device of the terminal device 2. The memory 21 is used for storing the computer program as well as other programs and data required by the terminal device. The memory 21 may also be used for temporarily storing data that has been output or is to be output.
Embodiments of the present application also provide a computer readable storage medium storing a computer program which, when executed by a processor, performs the steps of the respective method embodiments described above.
The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.
Claims (8)
1. A user login management method, comprising:
responding to a user login instruction received in a target application, carrying out third party user detection on account information in the user login instruction, wherein the third party user detection is used for detecting whether a user represented by the account information is a user of a preset third party application;
if the user represented by the account information is the user of the third party application, detecting whether the user represented by the account information is the user of the target application; wherein the detecting whether the user represented by the account information is the user of the target application comprises: performing account login based on account information in the user login instruction through a login interface of the target application, if the account login operation of the account information is successful in the login interface of the target application, determining that a user represented by the account information is a user of the target application, and if the account login operation of the account information is unsuccessful in the login interface of the target application, determining that the user represented by the account information is not a user of the target application;
if the user represented by the account information is the user in the target application, determining the user state of the account information in the target application, and executing user login operation on the account information according to the user state;
the method for executing the user login operation on the account information according to the user state comprises the steps of:
if the user state is a normal state, user login is carried out in the target application according to the account information;
if the user state is the state to be checked or updated, sending a prompt to be checked to a sending end of the user login instruction;
if the user state is a frozen state, a user freezing prompt and an information updating prompt are sent to a sending end of the user login instruction;
if the user state is an audit failed state, sending an audit failed prompt and an information update prompt to a sending end of the user login instruction;
the determining the user state of the account information in the target application includes:
inquiring risk assessment data of the account information in the third party application, and determining a user state of the account information in the target application according to the risk assessment data; or (b)
And inquiring the registration information of the account information in the third-party application, and determining the user state of the account information in the target application according to the inquired registration information.
2. The method for managing login of a user according to claim 1, wherein after said detecting whether the user represented by the account information is the user in the target application, further comprises:
if the account information is not the user in the target application, a first registration prompt is sent to a sending end of the user login instruction;
and if registration information aiming at the first registration prompt is received, user registration is carried out on the account information in the target application according to the received registration information.
3. The method for managing user login according to claim 1, wherein after the third party user detection is performed on account information in the user login instruction, further comprising:
if the third party user of the account information detects that the third party user is unqualified, a second registration prompt is sent to the sending end of the user login instruction;
and if the registration information aiming at the second registration prompt is received, registering the account information in the third party application according to the received registration information.
4. The method according to claim 2, wherein after the user registration of the account information in the target application according to the received registration information, further comprising:
setting the user state of the account information in the target application as a to-be-checked state, and performing information checking on registration information corresponding to the account information according to a preset checking standard;
if the registration information corresponding to the account information passes the verification, setting the application authority of the account information, and setting the user state of the account information in the target application as a normal state;
and if the registration information auditing corresponding to the account information is not passed, setting the user state of the account information in the target application as an auditing not-passed state.
5. The method for user login management according to claim 1, wherein said performing third party user detection on account information in the user login instruction includes:
sending a verification instruction to the third party application according to the account information, and receiving a verification result of the third party application aiming at the verification instruction, wherein the verification instruction is used for indicating the third party application to carry out account verification on the account information;
if the account verification of the account information is judged to be qualified according to the verification result, judging that the third party user of the account information is qualified;
and if the account verification of the account information is judged to be unqualified according to the verification result, judging that the third party user of the account information is unqualified.
6. A user login management device, comprising:
the third party user detection unit is used for responding to a user login instruction received in a target application, carrying out third party user detection on account information in the user login instruction, and detecting whether a user represented by the account information is a preset user of the third party application or not;
the target application user detection unit is used for detecting whether the user represented by the account information is the user of the target application or not if the user represented by the account information is the user of the third party application; wherein the detecting whether the user represented by the account information is the user of the target application comprises: performing account login based on account information in the user login instruction through a login interface of the target application, if the account login operation of the account information is successful in the login interface of the target application, determining that a user represented by the account information is a user of the target application, and if the account login operation of the account information is unsuccessful in the login interface of the target application, determining that the user represented by the account information is not a user of the target application;
the user state determining unit is used for determining the user state of the account information in the target application if the user represented by the account information is the user in the target application, and executing user login operation on the account information according to the user state;
the user state determining unit is further configured to determine a user state of the account information in the target application, and perform different user login operations on the account information according to different user states, where the user state determining unit is further configured to:
if the user state is a normal state, user login is carried out in the target application according to the account information;
if the user state is the state to be checked or updated, sending a prompt to be checked to a sending end of the user login instruction;
if the user state is a frozen state, a user freezing prompt and an information updating prompt are sent to a sending end of the user login instruction;
if the user state is an audit failed state, sending an audit failed prompt and an information update prompt to a sending end of the user login instruction;
the user state determination unit is further configured to: inquiring risk assessment data of the account information in the third party application, and determining a user state of the account information in the target application according to the risk assessment data; or (b)
And inquiring the registration information of the account information in the third-party application, and determining the user state of the account information in the target application according to the inquired registration information.
7. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 5 when the computer program is executed.
8. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the steps of the method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110482074.3A CN113225332B (en) | 2021-04-30 | 2021-04-30 | User login management method, device, terminal equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110482074.3A CN113225332B (en) | 2021-04-30 | 2021-04-30 | User login management method, device, terminal equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113225332A CN113225332A (en) | 2021-08-06 |
| CN113225332B true CN113225332B (en) | 2023-08-18 |
Family
ID=77090678
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110482074.3A Active CN113225332B (en) | 2021-04-30 | 2021-04-30 | User login management method, device, terminal equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113225332B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104753943A (en) * | 2015-03-30 | 2015-07-01 | 努比亚技术有限公司 | Method and device for log-in control of third-party account |
| CN107911340A (en) * | 2017-10-25 | 2018-04-13 | 平安普惠企业管理有限公司 | Login validation method, device, equipment and the storage medium of application program |
| CN110602052A (en) * | 2019-08-15 | 2019-12-20 | 平安科技（深圳）有限公司 | Micro-service processing method and server |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104518876B (en) * | 2013-09-29 | 2019-01-04 | 腾讯科技（深圳）有限公司 | Service login method and device |
| CN105827600B (en) * | 2016-03-11 | 2020-09-29 | 腾讯科技（深圳）有限公司 | Method and device for logging in client |
-
2021
- 2021-04-30 CN CN202110482074.3A patent/CN113225332B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104753943A (en) * | 2015-03-30 | 2015-07-01 | 努比亚技术有限公司 | Method and device for log-in control of third-party account |
| CN107911340A (en) * | 2017-10-25 | 2018-04-13 | 平安普惠企业管理有限公司 | Login validation method, device, equipment and the storage medium of application program |
| CN110602052A (en) * | 2019-08-15 | 2019-12-20 | 平安科技（深圳）有限公司 | Micro-service processing method and server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113225332A (en) | 2021-08-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10073916B2 (en) | Method and system for facilitating terminal identifiers | |
| CN110417778B (en) | Access request processing method and device | |
| CN113489713B (en) | Network attack detection method, device, equipment and storage medium | |
| CN108038130B (en) | Automatic false user cleaning method, device, equipment and storage medium | |
| CN110222107B (en) | Data transmission method and related equipment | |
| CN109324959B (en) | Method for automatically transferring data, server and computer readable storage medium | |
| CN108830562B (en) | Attendance card punching method and related equipment | |
| CN110471912B (en) | Employee attribute information verification method and device and terminal equipment | |
| CN109547427B (en) | Blacklist user identification method and device, computer equipment and storage medium | |
| CN112464238B (en) | Vulnerability scanning method and electronic equipment | |
| CN113225332B (en) | User login management method, device, terminal equipment and storage medium | |
| CN111046393B (en) | Vulnerability information uploading method and device, terminal equipment and storage medium | |
| CN111221742A (en) | Test case updating method and device, storage medium and server | |
| CN111259368A (en) | Method and equipment for logging in system | |
| CN107678917B (en) | Test machine automation management method, device, equipment and storage medium | |
| CN114218577A (en) | API risk determination method, device, equipment and medium | |
| CN109165127B (en) | Problem interface positioning method and device and electronic equipment | |
| CN112699369A (en) | Method and device for detecting abnormal login through stack backtracking | |
| CN111475400A (en) | Verification method of service platform and related equipment | |
| CN106911678B (en) | Virus detection method and device | |
| CN111158935B (en) | Application program detection method and device, computer equipment and storage medium | |
| CN112637110B (en) | Method for detecting password, password detection device and storage medium | |
| CN114510507A (en) | Data verification method, device, terminal equipment and medium | |
| CN112148612A (en) | Credit investigation service detection method, apparatus, computer device and storage medium | |
| CN116846638A (en) | Unauthorized behavior detection method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |