CN112182552A - Real-name authentication method and device, electronic equipment and storage medium - Google Patents
Real-name authentication method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112182552A CN112182552A CN202011003764.8A CN202011003764A CN112182552A CN 112182552 A CN112182552 A CN 112182552A CN 202011003764 A CN202011003764 A CN 202011003764A CN 112182552 A CN112182552 A CN 112182552A
- Authority
- CN
- China
- Prior art keywords
- real
- data
- name
- component
- target
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 238000012795 verification Methods 0.000 claims abstract description 80
- 238000013524 data verification Methods 0.000 claims abstract description 71
- 238000013502 data validation Methods 0.000 claims description 40
- 238000009877 rendering Methods 0.000 claims description 17
- 238000012552 review Methods 0.000 claims description 8
- 238000010200 validation analysis Methods 0.000 claims description 6
- 230000007246 mechanism Effects 0.000 claims description 4
- 238000011161 development Methods 0.000 abstract description 8
- 238000012550 audit Methods 0.000 description 19
- 230000008569 process Effects 0.000 description 14
- 238000004891 communication Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000004422 calculation algorithm Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000011835 investigation Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000000547 structure data Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/45—Structures or tools for the administration of authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
According to the real-name authentication method, the real-name authentication device, the electronic equipment and the storage medium, after user login information is received, a real-name authentication system identifier corresponding to the user login information is obtained, a preset target component corresponding to the real-name authentication system identifier is obtained, a real-name data submission page is rendered according to a target data component in the target component, so that a user can input corresponding real-name data on the real-name data submission page, the real-name data input by the user is received, and the real-name data is verified by using a target data verification rule component in the target component, so that a verification result is obtained. In the scheme, when the real-name authentication system is constructed, only the corresponding relation between the identification of the real-name authentication system and the component needs to be preset, corresponding services are quickly connected through componentized configuration to realize real-name authentication, codes do not need to be edited, development cost is saved, and cost of real-name authentication is reduced.
Description
Technical Field
The present application relates to the field of authentication technologies, and in particular, to a real-name authentication method and apparatus, an electronic device, and a storage medium.
Background
In recent years, with the rapid development of internet technology, service applications for enterprise users are also endless, and an enterprise real-name authentication system has become an admission threshold for an enterprise to develop subsequent services on an internet platform service provider.
The existing enterprise real-name authentication system, as one of the basic core services for developing enterprise related services, needs to deal with various authentication scenarios. In the process of developing and implementing the enterprise real name, because the requirements of each business line on the enterprise real name authentication service are different, a great deal of personalized requirements can be generated.
The existing enterprise real-name system is developed mostly in a hard code mode according to individual requirements of different service lines, and a large amount of manpower and material resources are invested to a certain extent to carry out partial repeated labor due to the complex real-name authentication process and the complex data structure. In the later period of the enterprise real-name project, codes are bloated along with the increase of the number of access service lines, and the maintenance cost is increased. When the time requirement of key business line access enterprise real-name authentication is met, the existing enterprise real-name authentication development team only invests a large amount of manpower and material resources, and overtime are completed, so that development resources are inclined.
Disclosure of Invention
In order to solve the technical problems described above or at least partially solve the technical problems, the present application provides a real-name authentication method, apparatus, electronic device, and storage medium.
In a first aspect, the present application provides a real-name authentication method, including:
when user login information is received, acquiring a real-name authentication system identifier corresponding to the user login information;
acquiring a preset target component corresponding to the real-name authentication system identifier, wherein the target component comprises a target data component and a target data verification rule component;
rendering a real-name data submission page in the terminal logged in by the user login information according to the target data component;
acquiring real-name data input by a user on the real-name data submission page;
and verifying the real-name data according to the target data verification rule component to obtain a verification result.
In a possible implementation manner, before obtaining the real-name authentication system identifier corresponding to the user login information, the method further includes:
after receiving developer login information, displaying a component selection page containing a plurality of component identifications in a terminal for developer login information login, wherein the component identification is at least one of a data component identification and a data verification rule component identification;
according to the received selection operation of the data component identification, acquiring a data component corresponding to the selected data component identification as a target data component;
according to the received selection operation of the data validation rule component identification, acquiring a data validation rule component corresponding to the selected data validation rule component identification as a target data validation rule component;
forming a target component by the target data component and the target data verification rule component;
generating a real-name authentication system identifier corresponding to the developer login information;
and constructing a corresponding relation between the target component and the real-name authentication system identifier, and storing the corresponding relation.
In a possible implementation manner, constructing a corresponding relationship between the target component and the real-name authentication system identifier includes:
generating a target code corresponding to the target component;
and constructing a corresponding relation between the target code and the real-name authentication system identifier.
In a possible implementation manner, acquiring a preset target component corresponding to the real-name authentication system identifier includes:
acquiring a preset target code corresponding to the real-name authentication system identifier;
and acquiring a preset target component corresponding to the target code as a target component corresponding to the real-name authentication system identifier.
In a possible implementation manner, the target data verification rule component includes a target data authenticity verification rule component;
verifying the real-name data according to the target data verification rule component to obtain a verification result, wherein the verification result comprises the following steps:
acquiring real data corresponding to the real-name data by using the target data authenticity verification rule component;
comparing the real name data with corresponding real data;
and if all the real name data are consistent with the corresponding real data, generating a verification result indicating that the verification is successful.
In one possible implementation, the target data validation rule component further comprises a target data structure validation rule component;
verifying the real-name data according to the target data verification rule component to obtain a verification result, and further comprising:
before the true and false verification rule component of the target data is used for acquiring the real data corresponding to the real-name data, the target data structure verification rule component is used for verifying whether the data structure of the real-name data conforms to a preset data structure;
if the data structures of all the real-name data accord with a preset data structure rule, executing a step of acquiring real data corresponding to the real-name data by using the data authenticity verification rule component;
if the real-name data with the data structure not conforming to the preset data structure rule exists in the real-name data, generating prompt information;
and prompting the user that the data structure of the real-name data does not conform to the preset data mechanism rule in a preset prompting mode based on the prompting information.
In a possible implementation manner, verifying the real-name data according to the target data verification rule component to obtain a verification result, further includes:
if real-name data inconsistent with corresponding real data exists in the real-name data, when developer login information corresponding to the real-name authentication system identification is detected to be in a login state, a manual review interface is rendered in a terminal where the developer login information logs in by using the target component, and the real-name data is verified manually to obtain a verification result.
In a second aspect, an embodiment of the present application further provides a real-name authentication apparatus, including:
the identification acquisition module is used for acquiring a real-name authentication system identification corresponding to user login information when the user login information is received;
the component acquisition module is used for acquiring a preset target component corresponding to the real-name authentication system identifier, and the target component comprises a target data component and a target data verification rule component;
the rendering module is used for rendering a real-name data submission page in the terminal logged in by the user login information according to the target data assembly;
the data acquisition module is used for acquiring real-name data input by a user on the real-name data submission page;
and the verification module is used for verifying the real-name data according to the target data verification rule component to obtain a verification result.
In a third aspect, an embodiment of the present application further provides an electronic device, including: a processor and a memory, wherein the processor is configured to execute the real-name authentication program stored in the memory to implement the real-name authentication method according to the first aspect.
In a fourth aspect, the present application further provides a storage medium storing one or more programs, where the one or more programs are executable by one or more processors to implement the real-name authentication method according to the first aspect.
Compared with the prior art, the technical scheme provided by the embodiment of the application has the following advantages:
according to the real-name authentication method, the real-name authentication device, the electronic equipment and the storage medium, after user login information is received, a real-name authentication system identifier corresponding to the user login information is obtained, a preset target component corresponding to the real-name authentication system identifier is obtained, a real-name data submission page is rendered according to a target data component in the target component, so that a user can input corresponding real-name data on the real-name data submission page, the real-name data input by the user is received, and the real-name data is verified by using a target data verification rule component in the target component, so that a verification result is obtained. In the scheme, when the real-name authentication system is constructed, only the corresponding relation between the identification of the real-name authentication system and the component needs to be preset, corresponding services are quickly connected through componentized configuration to realize real-name authentication, codes do not need to be edited, development cost is saved, and cost of real-name authentication is reduced.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a flowchart of a real-name authentication method according to an embodiment of the present application;
fig. 2 is a schematic diagram of a selected page of a real-name authentication system according to an embodiment of the present application;
fig. 3 is a schematic diagram of an identification input page of a real-name authentication system according to an embodiment of the present application;
fig. 4 is a schematic diagram of a real-name data submission page provided in the embodiment of the present application;
FIG. 5 is a flowchart illustrating a configuration of a target component corresponding to a real-name authentication system identifier according to an embodiment of the present disclosure;
FIG. 6 is a diagram illustrating a component selection page according to an embodiment of the present disclosure;
fig. 7 is a schematic diagram of a selected page in an audit process according to an embodiment of the present application;
FIG. 8 is a schematic diagram of a list of named application forms, provided by an embodiment of the present application;
fig. 9 is a schematic diagram of a real-name authentication method according to an embodiment of the present application;
fig. 10 is a block diagram of a real-name authentication device according to an embodiment of the present application;
fig. 11 is a schematic view of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
For the purpose of facilitating understanding of the embodiments of the present application, a brief description of some conceptual terms related to the embodiments of the present application will be provided below:
assembling: the method is a process of splitting and recombining a plurality of functional modules when a complex system is decoupled, has various attributes and states to reflect the internal characteristics, and is an application program framework in modularization, which is code encapsulation for the purpose of pursuing high multiplexing and high maintainability.
A rule engine: the method is a component nested in an application program, and realizes the separation of the business rules from the application program codes, so that the complex business rules are realized simply, and the business rules can be dynamically modified, thereby quickly responding to the requirement change.
Drools rules engine: drools is an open source business rule engine based on the Charles Forgy's RETE algorithm, easy to access enterprise policies, easy to adjust and easy to manage, meets the standards in the industry, and is fast and efficient. The business analyst or auditor can use it to easily view the business rules to verify whether the encoded rules implement the desired business rules. Drools is an open source rule engine written in the Java language that evaluates written rules using Rete algorithm. Drools allows the expression of business logic using declarative means. Rules may be written in a native language other than XML to facilitate learning and understanding. Furthermore, Java code may also be embedded directly into the rule file.
JSON: JSON (JavaScript Object Notation) is a lightweight data exchange format. It stores and represents data in a text format that is completely independent of the programming language, based on a subset of ECMAScript (js specification set by the european computer association). The simple and clear hierarchical structure enables JSON to become an ideal data exchange language, is easy to read and write by people, is easy to analyze and generate by machines, and effectively improves the network transmission efficiency.
XML: an extensible markup language, a subset of the standard generalized markup language, XML for short, is a markup language for marking electronic documents to be structured. In electronic computers, a label refers to a symbol of information that can be understood by a computer, and by this label, various information such as articles and the like can be handled between computers. XML can be used to mark data, define data types, is a source language that allows users to define their own mark-up language, is well suited for world wide web transmission, provides a uniform way to describe and exchange structured data independent of the application or provider, is a cross-platform, content-dependent technology in the Internet environment, and is an effective tool today for processing distributed structural information.
With the rapid development of internet technology in recent years, service applications facing enterprise users are also in a large quantity, and an enterprise real-name authentication system becomes an admission threshold for an enterprise to develop subsequent services on an internet platform service provider.
An internet platform service provider generally needs to create an enterprise real-name authentication system to realize real-name authentication of an enterprise, acquire real-name data of an enterprise user through the enterprise real-name authentication system and verify the real-name data, but because different internet platform service providers provide different services, namely different business lines, and different business lines have different requirements on the enterprise real-name authentication service, a large amount of personalized requirements can be generated, the existing enterprise real-name authentication system usually writes, copies and pastes codes according to requirements during development, and the mode needs more manpower and material resources, and later maintenance is difficult.
In order to solve the problems that the development of the existing real-name authentication system is time-consuming and labor-consuming, and the maintenance is difficult, so that the real-name authentication cost is high, the application provides a real-name authentication method.
The embodiment of the application provides a service system, which can execute at least two functions, wherein the first function is to configure different real-name authentication systems according to different requirements, and the second function is to perform real-name authentication by using a pre-configured real-name authentication system.
The first function is generally directed to a developer of the real-name authentication system, wherein the developer refers to a service platform, an enterprise, an individual, or the like that constructs the real-name authentication system, and the second function is generally directed to a user of the real-name authentication system, wherein the user refers to an enterprise, an individual, or the like that performs real-name authentication using the real-name authentication system, and specifically, a user login entry and a developer login entry may be provided in the system, and if the first function is to be used, the service system is logged in from the developer login entry, and if the second function is to be used, the service system is logged in from the user login entry.
In order to implement the first function of the service system, a real-name authentication componentization engine is set in the service system in advance, and the real-name authentication componentization engine includes a Drools rule engine, a dynamic page engine, a real-name data type file and a real-name data authentication rule file, wherein the real-name data type file is usually in a JSON format, the real-name data authentication rule file is usually in an XML format, and the real-name data refers to data which needs to be input by a user when real-name authentication is performed.
The real-name data type file comprises all types of real-name data required by real-name authentication, and the purpose is to meet the requirements of different real-name authentication systems, because different real-name authentication systems have different corresponding service lines, the types of the real-name data required to be authenticated are also different, and developers can select the corresponding type of the real-name data from the real-name data type file to be used for configuration of the real-name authentication system according to requirements.
In one embodiment, the real name data type file may contain the following:
of course, any real name data type may be contained in the real name data type file in addition to the above.
The real name data verification rule file comprises a verification rule used for verifying the real name data, a corresponding relation exists between the verification rule and the real name data type, and the corresponding verification rule can be determined under the condition of determining the real name data type.
In one embodiment, the data validation rule file may contain the following:
of course, in addition to the above, any rule for verifying real name data may be included in the data verification rule file.
The real-name authentication system generally comprises a real-name data submission module, a real-name data automatic auditing module and a real-name data manual auditing module.
The real-name data submission module comprises a real-name data submission page used for showing a user, the type of the real-name data needing to be submitted is shown in the real-name data submission page, and then the user can submit the real-name data corresponding to the type of the real-name data shown in the page on the real-name data submission page.
The real-name data automatic auditing module is used for automatically verifying the real-name data input by the user and verifying whether the real-name data accords with a preset data rule.
The manual real-name data auditing module comprises a manual auditing page for displaying to an auditor, and real-name data needing manual auditing is displayed in the manual auditing page so that the auditor can perform manual auditing according to the real-name data displayed in the manual auditing page.
When the service system is used for configuring the real-name authentication system, the Drools rule engine can utilize the regular + XML + JSON mode according to the configuration operation of the developer, the real-name data type, the real-name data verification rule and the corresponding relation between the real-name data type and the real-name data verification rule required by the real-name authentication system are analyzed from JSON and XML according to the configuration operation of a developer, and finally, a data component is generated according to the analyzed real-name data type, and generating a data verification rule component according to the analyzed real-name data verification rule, establishing a corresponding relation between the data component and the data verification rule according to the corresponding relation between the real-name data type and the real-name data verification rule, and establishing a corresponding relation between the data component and the data verification component and a real-name authentication system to be established by a developer, thereby completing the configuration of the real-name authentication system.
When real-name authentication is carried out by using a real-name authentication system which is configured in advance in a service system, a component corresponding to the real-name authentication system is obtained, a dynamic page engine is used for rendering real-name data based on the component to submit a page, the rendered page is displayed to a user of the real-name authentication system, so that the user inputs the real-name data according to the content displayed in the page, the real-name data is verified according to the component, and when wrong real-name data is verified, the page is manually verified based on rendering by using the dynamic page engine, so that the real-name data is further verified manually, and the accuracy of a final verification result is ensured.
A real-name authentication method provided in the present application is described below with specific examples.
Fig. 1 is a flowchart of a real-name authentication method according to an embodiment of the present application, where the method is applied to the service system, and as shown in fig. 1, the method may include the following steps:
s11, when user login information is received, acquiring a real-name authentication system identifier corresponding to the user login information.
In one embodiment, the application provides a service system, which is provided with a user login entry and a developer login entry, when the user clicks the user login entrance to log in, the service system is determined to receive the user login information, because the corresponding real-name authentication system is required to be opened when the user usually performs real-name authentication, and the service system provided by the application can configure different real-name authentication systems according to different business requirements, there may exist a plurality of pre-configured real-name authentication systems in the service system, so in order to identify the real-name authentication system corresponding to the user login information, after the user login information is obtained, the real-name authentication system identifier corresponding to the user login information is also obtained so as to load the corresponding real-name authentication system, the real-name authentication system identification corresponds to the real-name authentication system one by one, and different real-name authentication system identifications correspond to different real-name authentication systems.
In an embodiment, after receiving the user login information, the service system may display a real-name authentication system selection page, where the real-name authentication system selection page includes a plurality of buttons (for example, as shown in fig. 2) corresponding to real-name authentication system identifiers, one button corresponds to one real-name authentication system identifier, the user clicks the button corresponding to the corresponding real-name authentication system identifier according to a requirement of the user, the service system determines a clicked position, then the button selected by the user may be determined according to preset position information of each button, and then the real-name authentication system identifier corresponding to the selected button is determined as the real-name authentication system identifier corresponding to the user login information.
In another embodiment, after the service system receives the user login information, the service system may further display a real-name authentication system identifier input page, in which a window and a submit button (for example, as shown in fig. 3) for inputting a real-name authentication system identifier may be displayed, the user inputs the real-name authentication system identifier corresponding to the real-name authentication system that the user needs to use into the window and clicks the submit button, and when the service system detects that the submit button is clicked, the real-name authentication system identifier in the real-name authentication system identifier input window is used as the received real-name authentication system identifier, where the real-name authentication system identifier may be obtained by the user through table lookup and the like.
In an embodiment, the user may obtain the real-name authentication system identifier corresponding to the real-name authentication system that the user needs to use by looking up a table or the like.
S12, when a real-name authentication system identification is received, a preset target assembly corresponding to the real-name authentication system identification is obtained, and the target assembly comprises a target data assembly and a target data verification rule assembly.
The data component is used for setting the type of real-name data needing authentication in the real-name authentication system, and the data verification rule component is used for setting the rule for verifying the real-name data in the real-name authentication system.
The service system configures the real-name authentication system corresponding to the real-name authentication system identifier in advance, namely, the corresponding relationship between the real-name authentication system and the component is set, so that the component corresponding to the received real-name authentication system identifier, namely, the target component can be found according to the preset corresponding relationship after the real-name authentication system identifier is received.
And S13, rendering a real-name data submission page in the terminal logged in by the user login information according to the target data assembly.
The terminal where the user logs in the information is a terminal where the user logs in the service system, where the terminal may be a mobile phone, a notebook computer, a desktop computer, a tablet computer, or the like, for example, if the user logs in the service system on a computer a, the computer a is the terminal where the user logs in the information corresponding to the user.
In an embodiment, a dynamic page engine arranged in a service system is used for rendering a real-name data submission page in a terminal for logging in user login information based on a target data component, and different pages can be rendered according to different target components through the dynamic page engine.
After rendering the real-name data submission page in the terminal in which the user logs in according to the target data component, the type of the real-name data to be submitted by the user is shown in the real-name data submission page, for example, the type of the real-name data includes an enterprise unified organization code, an enterprise business license photo, a legal name, a legal identity card number, a legal identity card head portrait photo, a legal identity card national emblem photo, a mobile phone number, and the like (for example, shown in fig. 4).
And S14, acquiring real-name data input by a user on the real-name data submission page.
In an embodiment, a submit button (for example, as shown in fig. 4) is further disposed in the real-name data submit page, and after the user completes filling in all the real-name data, the service system may acquire the real-name data input by the user by clicking the submit button.
And S15, verifying the real-name data according to the target data verification rule component to obtain a verification result.
How to verify the real-name data according to the target data verification rule component is described below, and is not described in detail here.
According to the real-name authentication method provided by the embodiment of the application, after user login information is received, when a real-name authentication system identifier corresponding to the user login information is obtained, a preset target assembly corresponding to the real-name authentication system identifier is obtained, a real-name data submission page is rendered according to a target data assembly in the target assembly, so that a user can input corresponding real-name data on the real-name data submission page, the real-name data input by the user is received, and the real-name data is verified by using a target data verification rule assembly in the target assembly, so that a verification result is obtained. In the scheme, only the component corresponding to the real-name authentication system identifier needs to be preset, and when real-name authentication is carried out, the corresponding target component can be directly obtained according to the received real-name authentication system identifier, so that real-name data authentication is realized.
On the basis of the above embodiment, in order to ensure that the target component corresponding to the real-name authentication system identifier can be acquired, before executing S11, the real-name authentication system needs to be configured, so as to obtain the real-name authentication system identifier and the corresponding relationship between the real-name authentication system identifier and the component.
The configuration of the real-name authentication system is a first function of the service system, a developer logs in the service system from a developer login entrance of the service system, and completes the configuration of the real-name authentication system according to the prompt of the service system, and the configuration is to determine components for constructing the real-name authentication system.
In one embodiment, as shown in FIG. 5, the target component corresponding to the real-name authentication system identification may be configured by:
s101, after receiving developer login information, displaying a component selection page containing a plurality of component identifications in a terminal where the developer login information logs in, wherein the component identification is at least one of a data component identification and a data verification rule component identification.
In one embodiment, after the developer logs in the service system from the developer login entry, the service system receives the developer login information.
In one embodiment, a component selection page may be comprised of a plurality of data component identifications.
In one embodiment, a component selection page may be comprised of a plurality of data validation rule component identifications.
In one embodiment, one component selection page may also be composed of a plurality of data component identifications and data validation rule component identifications.
The data component identification corresponds to the data component, and the data validation rule component identification corresponds to the data validation rule component.
In one embodiment, the component identification may be a keyword that embodies the functionality of the component.
In one example, the data component is a data component for setting a real-name data type of the identification card photo avatar, and the corresponding data component is identified as the "identification card photo avatar".
S102, according to the received selection operation of the data component identification, the data component corresponding to the selected data component identification is obtained and used as a target data component.
S103, according to the received selection operation of the data verification rule component identification, the data verification rule component corresponding to the selected data verification rule component identification is obtained and used as a target data verification rule component.
And S104, forming a target component by the target data component and the target data verification rule component.
And S105, generating a real-name authentication system identifier corresponding to the login information of the developer.
In one embodiment, the real-name authentication system identification may be a random string generated using a random algorithm.
In another embodiment, the real-name authentication system identification may be a field entered by a developer or service system operator.
For example, since different real-name authentication systems are generally associated with different developers, the real-name authentication system identifier may be a content that is unique to the developer of the real-name authentication system, such as the name and ID of the developer, and is easily recognized by the user.
In one example, after the target component is determined, the service system displays an identification input page in a terminal used by a developer, a real-name authentication system identification input window is arranged in the identification input page, the developer inputs and submits a real-name authentication system identification in the window, and then the service system acquires the real-name authentication system identification corresponding to the login information of the developer.
And S106, establishing a corresponding relation between the target assembly and the real-name authentication system identification, and storing the corresponding relation.
In an embodiment, since a real-name authentication system usually needs to have a plurality of corresponding target components, in order to find the target components more conveniently, a target code corresponding to all the target components may be generated first when the corresponding relationship between the target components and the identification of the real-name authentication system is established, for example, the target components are grouped into a component set, a target code corresponding to the component set is generated, and then the corresponding relationship between the identification of the real-name authentication system and the target code is established. Thus, after the real-name authentication system identification is obtained, the target code corresponding to the real-name authentication system identification is determined, and then all target components corresponding to the real-name authentication system identification can be obtained after the component set corresponding to the target code is obtained.
S101-S103 are explained below:
when the real-name authentication system is configured by using the system, firstly, a component selection page (for example, as shown in fig. 6) consisting of a plurality of data component identifications is displayed, a developer selects the corresponding data component identification in the page according to the requirement, and clicks a submission button on the page after all the required data component identifications are selected, when the submission button is clicked, the system can obtain the data component identification selected by the developer, the system determines the corresponding data component as a target data component according to the data component identification selected by the developer, and obtains a data verification rule component corresponding to the target data component, then, the service system displays a component selection page consisting of the identification (namely, the data verification rule component identification) of the data verification rule component corresponding to the target data component, and the developer selects the corresponding data verification rule component identification in the page according to the requirement, and after all the required data validation rule component identifications are selected, clicking a submission button on the page, acquiring the data validation rule component identification selected by a developer by the system after the submission button is clicked, and determining the corresponding data validation rule component as a target data validation rule component by the system according to the data validation rule component identification selected by the developer.
In an embodiment, the system determines the corresponding data component as the target data component according to the data component identifier selected by the developer, and the following method may be adopted:
the system obtains a data component identifier selected by a developer, analyzes a field corresponding to the selected data component identifier from a real-name data file according to the data component identifier by using a Drools rule engine, encapsulates the analyzed field into a data component corresponding to the data component identifier, and uses the data component as a target data component, wherein the field can be a code.
In an embodiment, the system determines the corresponding data validation rule component as the target data validation rule component according to the data validation rule component identifier selected by the developer, and may adopt the following mode:
the system obtains a data verification rule component identification selected by a developer, a Drools rule engine is utilized to analyze a field corresponding to the selected data verification rule component identification from a real-name data verification rule file according to the data verification rule component identification, and the analyzed field is packaged into a data component corresponding to the data verification rule component identification and serves as a target data verification rule component.
Through the embodiment, a developer can easily acquire the data type and the data verification rule for constructing the real-name verification system only by executing the selection operation without compiling and modifying codes, so that time and labor are saved.
On the basis of any of the above embodiments, the data verification rule component can be generally divided into two components, one is a data structure verification rule component for verifying whether the data structure is standard, and the other is a data authenticity verification rule component for verifying the authenticity of the data.
On the basis of any one of the above embodiments, s15, verifying the real-name data according to the target data verification rule component to obtain a verification result, where the verifying may include:
acquiring real data corresponding to the real-name data by using the data authenticity verification rule component; comparing the real name data with corresponding real data; and if all the real name data are consistent with the corresponding real data, generating a verification result indicating that the verification is successful.
The data authenticity verification rule component is generally used for verifying whether real-name data is accurate, for example, whether an OCR verification picture of an enterprise license is correct, whether information of a license filled by a user is consistent with basic information of an industrial company for credit investigation, whether an OCR verification picture of an identity card is correct, whether information of a legal person identity card filled by the user is consistent with information of a person for credit investigation, and the like.
On the basis of the above embodiment, s15, verifying the real-name data according to the target data verification rule component to obtain a verification result, which may further include:
before the true and false data corresponding to the real-name data is obtained by the data true and false verification rule component, verifying whether the data structure of the real-name data conforms to a preset data structure by the data structure verification rule component; if the data structures of all the real-name data accord with a preset data structure rule, executing a step of acquiring real data corresponding to the real-name data by using the data authenticity verification rule component; and if real-name data with a data structure which does not accord with a preset data structure rule exists in the real-name data, generating prompt information, and prompting a user that the data structure of the real-name data does not accord with the preset data mechanism rule in a preset prompt mode based on the prompt information.
In an embodiment, the prompting mode may be set by the user, for example, the prompting mode may be set to be a voice broadcast, a short message prompt, a mail prompt, or the like, and the prompting mode set by the user is obtained after the prompting information is generated as the preset prompting mode.
In an embodiment, a default prompting mode may be set when the developer configures the real-name authentication system, and if the prompting mode set by the user is not obtained within a preset time (for example, 5s) after the prompting information is generated, the default prompting mode is used as the preset prompting mode, or the default prompting mode may be directly used as the preset prompting mode without obtaining the prompting mode set by the user.
The data structure validation rule component is generally used for verifying whether the real name data meets a unified specification (i.e., a specification common to all users), for example, whether the number of digits of the mobile phone number is accurate, whether the number of digits of the identification card number is accurate, whether the size of the picture meets a preset size requirement, and the like.
In this embodiment, the real-name data structure is verified a priori by the above method, and after the real-name data structure meets the preset rule, the authenticity of the real-name data is verified, because the authenticity of the real-name data is verified and the real-name data generally needs to be networked with an external system, the time consumption is large, and the calculation amount is large, so the verification cost can be reduced by the scheme.
Generally, a developer usually selects a plurality of data components when configuring the real-name authentication system, that is, selects a plurality of types of real-name data to be verified, and data verification rule components corresponding to different data components are different, and in order to ensure that the real-name authentication system can automatically and orderly complete verification of the real-name data, the developer can also set an auditing flow of the real-name data when configuring the real-name authentication system.
In an embodiment, after a developer selects a target data validation rule component, a service system generates one or more audit flows according to the target data validation component, wherein the audit flows mainly comprise the target data validation rule component and the sequence among the target data validation rule components, in order to enable the service system to automatically run the time of each target data validation rule component to validate real name data of each type according to the audit flows, a switch can be arranged between adjacent target data validation rule components in the audit flows by using the thought of a pre-buried switch, whether each target data validation rule component is started or not is determined by using JSON, and after one target data validation rule component is executed, the following switch is started so as to execute the next target data validation rule component.
In an embodiment, if the service system generates an audit flow according to the target data verification component, the audit flow is used as a default audit flow, and when the target data verification rule is used to verify the real-name data in S15, the real-name data is directly verified according to the default audit flow.
In an embodiment, if the service system generates multiple auditing flows according to the target data verification component, when the real-name authentication system is configured, after a developer selects the target data verification component, an auditing flow selection page is displayed, multiple auditing flow charts are displayed in the page, one auditing flow chart corresponds to one auditing flow, the developer selects a corresponding auditing flow chart in the page according to own requirements, and the auditing flow corresponding to the auditing flow chart selected by the developer is used as a target auditing flow. When the real-name data is verified by using the target data verification rule in the step S15, the corresponding target data verification rule is executed in order according to the target verification process to realize the automatic verification of the real-name data.
In an example, the data verification rule component selected by the user is a component for verifying the authenticity of a business license photo and a component for verifying the authenticity of an identity card photo, the service system generates two verification processes according to the two components, an audit flow chart corresponding to the generated audit process (for example, a flow chart including the two audit processes shown in fig. 7) is displayed in a displayed audit process selection page, the user clicks the selected audit flow chart according to the own requirement, the position of the audit flow chart is preset in the service system, the service system determines the position of a click operation to determine the audit flow chart selected by the user, and then the corresponding audit process is determined as a target audit process according to the audit flow chart selected by the user.
Because the external system is not updated timely, for example, the user makes a legal change, but the external system for acquiring the real data corresponding to the real-name data of the legal is not updated timely, the real data acquired when the target data authenticity verification component is used for verifying the authenticity of the real-name data is not accurate enough, so that the user submits an accurate verification result of the real-name data but the real-name data is wrong, and in order to prevent the problems, a developer configures a manual verification page when configuring the real-name authentication system.
In one embodiment, if real-name data inconsistent with corresponding real data exists in the real-name data, when developer login information corresponding to the real-name authentication system identifier is detected to be in a login state, a manual review interface containing the real-name data is rendered in a terminal where the developer login information logs in by using the target component, so that the real-name data is verified manually to obtain a verification result.
In an embodiment, all real-name data input by the user may be displayed in the manual review page, or only real-name data inconsistent with the real data may be displayed.
In the embodiment, by setting manual review, the accuracy of the real-name data verification result is improved, and the problems of error verification result and the like caused by untimely data updating are avoided.
In an embodiment, a dynamic page engine arranged in a service system is used for rendering a manual review page in a terminal logged in by developer login information based on a target component, and different pages can be rendered according to different components by using the dynamic page engine for page rendering.
Since one real-name authentication system may correspond to multiple users, there may be real-name data of multiple users that need to be manually reviewed.
Therefore, in an embodiment, before rendering a manual review interface in the terminal where the developer login information is logged in by using the target component, the real-name verification method further includes:
displaying a real-name application form list in a terminal where the developer logs in information, wherein the real-name application form list comprises real-name application form information, and the real-name application form information comprises user login information corresponding to real-name data needing manual auditing (for example, as shown in fig. 8), so that the developer can select user login information from the real-name application form list according to requirements and click an 'auditing' button, and then the service system acquires real-name data and a target component corresponding to the user login information according to the selected user login information and performs a step of rendering a manual auditing interface in the terminal where the developer logs in information by using the target component and the real-name data.
In this embodiment, the user login information is included in the real-name application form information, so that when real-name data of a plurality of users need to be audited, a developer can determine the order of auditing according to the users, for example, sometimes the user may make a call or send a mail to the developer if the user is in a hurry to complete auditing, so that the developer can quickly locate a specific user from the real-name application form information to be audited according to the user login information, and perform preferential auditing, which is convenient and time-saving.
One specific example is:
fig. 9 is a schematic diagram of a real-name authentication method according to an embodiment of the present application, as shown in fig. 9,
the method comprises the steps that a developer logs in from a developer login entrance of a service system at a developer end (namely, a terminal used for logging in by the developer) and then executes configuration operation of a real-name authentication system according to prompt of the service system, the service system determines a target component by a Drools rule engine in a regular + XML + JSON mode according to the configuration operation of the real-name authentication system of the developer, a real-name authentication system identification corresponding to the real-name authentication system configured by the developer is generated, a corresponding relation between the real-name authentication system identification and the target component is constructed, and the corresponding relation is stored.
After user login information sent by a user terminal (namely a terminal used for logging in by a user) is acquired, a service system acquires a real-name authentication system identifier corresponding to the user login information, acquires a target component corresponding to the real-name authentication system identifier, dynamically renders a real-name data submission page in the user terminal according to a target data component in the target component, the user inputs and submits real-name data in the real-name data submission page, after the service system acquires the real-name data submitted by the user, the real-name data is verified by using a target data verification rule in the target component, the verification mainly comprises verification of a data structure and verification of data accuracy (namely authenticity), if the data structure is verified to be wrong, a data structure error prompt is generated, if the data is verified to be inaccurate, the service system dynamically renders a manual verification page in a developer terminal according to the target component, the developer can manually check the real-name data submitted by the user, if the data structure and the data accuracy have no problem, the verification is passed, and fields such as 'verification pass' and the like can be displayed on the terminal used by the user.
The present application also provides a real-name authentication apparatus, which is configured to implement the real-name authentication method, and as shown in fig. 10, the apparatus may include:
an identifier obtaining module 1001, configured to obtain, when user login information is received, a real-name authentication system identifier corresponding to the user login information;
the component obtaining module 1002 is configured to obtain a preset target component corresponding to the real-name authentication system identifier, where the target component includes a target data component and a target data validation rule component;
a rendering module 1003, configured to render a real-name data submission page in the terminal where the user login information logs in according to the target data component;
the data acquisition module 1004 is configured to acquire real-name data input by a user on the real-name data submission page;
the verification module 1005 is configured to verify the real-name data according to the target data verification rule component to obtain a verification result.
In one embodiment, the apparatus further comprises: a configuration module (not shown in the figures) for:
after receiving developer login information, displaying a component selection page containing a plurality of component identifications in a terminal for developer login information login, wherein the component identification is at least one of a data component identification and a data verification rule component identification;
according to the received selection operation of the data component identification, acquiring a data component corresponding to the selected data component identification as a target data component;
according to the received selection operation of the data validation rule component identification, acquiring a data validation rule component corresponding to the selected data validation rule component identification as a target data validation rule component;
forming a target component by the target data component and the target data verification rule component;
generating a real-name authentication system identifier corresponding to the developer login information;
and constructing a corresponding relation between the target component and the real-name authentication system identifier, and storing the corresponding relation.
In an embodiment, constructing the correspondence between the target component and the real-name authentication system identifier may include:
generating a target code corresponding to the target component;
and constructing a corresponding relation between the target code and the real-name authentication system identifier.
In an embodiment, the component obtaining module 1002 is specifically configured to: acquiring a preset target code corresponding to the real-name authentication system identifier;
and acquiring a preset target component corresponding to the target code as a target component corresponding to the real-name authentication system identifier.
In one embodiment, the target data validation rule component comprises a target data authenticity validation rule component;
the verification module 1005 is specifically configured to:
acquiring real data corresponding to the real-name data by using the target data authenticity verification rule component;
comparing the real name data with corresponding real data;
and if all the real name data are consistent with the corresponding real data, generating a verification result indicating that the verification is successful.
In one embodiment, the target data validation rule component further comprises a target data structure validation rule component;
the verification module 1005 is specifically configured to:
before the true and false verification rule component of the target data is used for acquiring the real data corresponding to the real-name data, the target data structure verification rule component is used for verifying whether the data structure of the real-name data conforms to a preset data structure;
if the data structures of all the real-name data accord with a preset data structure rule, executing a step of acquiring real data corresponding to the real-name data by using the data authenticity verification rule component;
if the real-name data with the data structure not conforming to the preset data structure rule exists in the real-name data, generating prompt information;
and prompting the user that the data structure of the real-name data does not conform to the preset data mechanism rule in a preset prompting mode based on the prompting information.
In one embodiment, the verification module 1005 is further configured to:
if real name data inconsistent with corresponding real data exists in the real name data, when developer login information corresponding to the real name authentication system identification is detected to be in a login state, a manual review interface containing the real name data is rendered in a terminal where the developer login information logs in by using the target assembly, and the real name data is verified manually to obtain a verification result.
In another embodiment of the present application, an electronic device is further provided, as shown in fig. 11, including a processor 1101, a communication interface 1102, a memory 1103, and a communication bus 1104, where the processor 1101, the communication interface 1102, and the memory 1103 complete communication with each other through the communication bus 1104;
a memory 1103 for storing a computer program;
the processor 1101 is configured to implement the following steps when executing the program stored in the memory 1103:
when user login information is received, acquiring a real-name authentication system identifier corresponding to the user login information;
acquiring a preset target component corresponding to the real-name authentication system identifier, wherein the target component comprises a target data component and a target data verification rule component;
rendering a real-name data submission page in the terminal logged in by the user login information according to the target data component;
acquiring real-name data input by a user on the real-name data submission page;
and verifying the real-name data according to the target data verification rule component to obtain a verification result.
The communication bus 1104 mentioned in the above electronic device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus 1104 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface 1102 is used for communication between the electronic apparatus and other apparatuses.
The Memory 1103 may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor 1101 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.
In another embodiment of the present application, there is further provided a storage medium having a real-name authentication method program stored thereon, the real-name authentication method program implementing any one of the steps of the real-name authentication method described above when executed by a processor.
When the embodiment of the invention is specifically implemented, reference can be made to the above embodiments, and corresponding technical effects are achieved.
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The foregoing are merely exemplary embodiments of the present invention, which enable those skilled in the art to understand or practice the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A real-name authentication method is characterized by comprising the following steps:
when user login information is received, acquiring a real-name authentication system identifier corresponding to the user login information;
acquiring a preset target component corresponding to the real-name authentication system identifier, wherein the target component comprises a target data component and a target data verification rule component;
rendering a real-name data submission page in the terminal logged in by the user login information according to the target data component;
acquiring real-name data input by a user on the real-name data submission page;
and verifying the real-name data according to the target data verification rule component to obtain a verification result.
2. The method of claim 1, wherein prior to obtaining the real-name authentication system identifier corresponding to the user login information, the method further comprises:
after receiving developer login information, displaying a component selection page containing a plurality of component identifications in a terminal for developer login information login, wherein the component identification is at least one of a data component identification and a data verification rule component identification;
according to the received selection operation of the data component identification, acquiring a data component corresponding to the selected data component identification as a target data component;
according to the received selection operation of the data validation rule component identification, acquiring a data validation rule component corresponding to the selected data validation rule component identification as a target data validation rule component;
forming a target component by the target data component and the target data verification rule component;
generating a real-name authentication system identifier corresponding to the developer login information;
and constructing a corresponding relation between the target component and the real-name authentication system identifier, and storing the corresponding relation.
3. The method of claim 2, wherein constructing the target component to correspond to the real-name authentication system identifier comprises:
generating a target code corresponding to the target component;
and constructing a corresponding relation between the target code and the real-name authentication system identifier.
4. The method of claim 3, wherein obtaining a preset target component corresponding to the real-name authentication system identifier comprises:
acquiring a preset target code corresponding to the real-name authentication system identifier;
and acquiring a preset target component corresponding to the target code as a target component corresponding to the real-name authentication system identifier.
5. The method of claim 1, wherein the target data validation rule component comprises a target data authenticity validation rule component;
verifying the real-name data according to the target data verification rule component to obtain a verification result, wherein the verification result comprises the following steps:
acquiring real data corresponding to the real-name data by using the target data authenticity verification rule component;
comparing the real name data with corresponding real data;
and if all the real name data are consistent with the corresponding real data, generating a verification result indicating that the verification is successful.
6. The method of claim 5, wherein the target data validation rule component further comprises a target data structure validation rule component;
verifying the real-name data according to the target data verification rule component to obtain a verification result, and further comprising:
before the true and false verification rule component of the target data is used for acquiring the real data corresponding to the real-name data, the target data structure verification rule component is used for verifying whether the data structure of the real-name data conforms to a preset data structure;
if the data structures of all the real-name data accord with a preset data structure rule, executing a step of acquiring real data corresponding to the real-name data by using the data authenticity verification rule component;
if the real-name data with the data structure not conforming to the preset data structure rule exists in the real-name data, generating prompt information;
and prompting the user that the data structure of the real-name data does not conform to the preset data mechanism rule in a preset prompting mode based on the prompting information.
7. The method of claim 5, wherein verifying the real-name data according to the target data verification rule component results in a verification result, further comprising:
if real name data inconsistent with corresponding real data exists in the real name data, when developer login information corresponding to the real name authentication system identification is detected to be in a login state, a manual review interface containing the real name data is rendered in a terminal where the developer login information logs in by using the target assembly, and the real name data is verified manually to obtain a verification result.
8. A real-name authentication apparatus, comprising:
the identification acquisition module is used for acquiring a real-name authentication system identification corresponding to user login information when the user login information is received;
the component acquisition module is used for acquiring a preset target component corresponding to the real-name authentication system identifier, and the target component comprises a target data component and a target data verification rule component;
the rendering module is used for rendering a real-name data submission page in the terminal logged in by the user login information according to the target data assembly;
the data acquisition module is used for acquiring real-name data input by a user on the real-name data submission page;
and the verification module is used for verifying the real-name data according to the target data verification rule component to obtain a verification result.
9. An electronic device, comprising: a processor and a memory, the processor being configured to execute a real-name authentication program stored in the memory to implement the real-name authentication method of any one of claims 1-7.
10. A storage medium storing one or more programs, the one or more programs being executable by one or more processors to implement the real-name authentication method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011003764.8A CN112182552A (en) | 2020-09-22 | 2020-09-22 | Real-name authentication method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011003764.8A CN112182552A (en) | 2020-09-22 | 2020-09-22 | Real-name authentication method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112182552A true CN112182552A (en) | 2021-01-05 |
Family
ID=73955821
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011003764.8A Pending CN112182552A (en) | 2020-09-22 | 2020-09-22 | Real-name authentication method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112182552A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115190016A (en) * | 2022-07-25 | 2022-10-14 | 平安科技（深圳）有限公司 | System general switch configuration method, device, equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006123899A1 (en) * | 2005-05-18 | 2006-11-23 | Solmaze Co., Ltd. | Method for operating and authenticating password system, and storage media having program source thereof |
| KR20070018569A (en) * | 2005-08-10 | 2007-02-14 | 서울신용평가정보 주식회사 | Method of agent for authorization using identification code, sever and system thereof |
| CN106850693A (en) * | 2017-03-31 | 2017-06-13 | 深圳微众税银信息服务有限公司 | The method and real-name authentication system of a kind of real-name authentication |
| TW201935295A (en) * | 2018-02-09 | 2019-09-01 | 劉根田 | Real-name authentication service system and real-name authentication service method |
| CN110363533A (en) * | 2019-06-26 | 2019-10-22 | 山东普惠共享经济技术开发有限公司 | A kind of real-name authentication system and method |
| CN110766376A (en) * | 2019-09-18 | 2020-02-07 | 郑州卓通电子科技有限公司 | Multi-application integration platform for enterprise |
-
2020
- 2020-09-22 CN CN202011003764.8A patent/CN112182552A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006123899A1 (en) * | 2005-05-18 | 2006-11-23 | Solmaze Co., Ltd. | Method for operating and authenticating password system, and storage media having program source thereof |
| KR20070018569A (en) * | 2005-08-10 | 2007-02-14 | 서울신용평가정보 주식회사 | Method of agent for authorization using identification code, sever and system thereof |
| CN106850693A (en) * | 2017-03-31 | 2017-06-13 | 深圳微众税银信息服务有限公司 | The method and real-name authentication system of a kind of real-name authentication |
| TW201935295A (en) * | 2018-02-09 | 2019-09-01 | 劉根田 | Real-name authentication service system and real-name authentication service method |
| CN110363533A (en) * | 2019-06-26 | 2019-10-22 | 山东普惠共享经济技术开发有限公司 | A kind of real-name authentication system and method |
| CN110766376A (en) * | 2019-09-18 | 2020-02-07 | 郑州卓通电子科技有限公司 | Multi-application integration platform for enterprise |
Non-Patent Citations (1)
| Title |
|---|
| 张希奇;: "基于目录服务的统一身份认证和登录系统研究", 安徽电子信息职业技术学院学报, no. 02 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115190016A (en) * | 2022-07-25 | 2022-10-14 | 平安科技（深圳）有限公司 | System general switch configuration method, device, equipment and storage medium |
| CN115190016B (en) * | 2022-07-25 | 2023-04-28 | 平安科技（深圳）有限公司 | System general switch configuration method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11561846B2 (en) | API notebook tool | |
| CN105765527B (en) | The method and apparatus of software development kit (SDK) for customization | |
| CN105814539B (en) | The method and apparatus generated for code virtualization and remote process call | |
| US10108535B2 (en) | Web application test script generation to test software functionality | |
| US6973625B1 (en) | Method for creating browser-based user interface applications using a framework | |
| US8983935B2 (en) | Methods for utilizing a javascript emulator in a web content proxy server and devices thereof | |
| US20210216288A1 (en) | Api-based software development platform | |
| CN101193007A (en) | Testing method, scenario testing method and corresponding device for URL command | |
| CN111290742A (en) | Parameter verification method and device, electronic equipment and readable storage medium | |
| US11442670B2 (en) | Methods and systems for improving disclosure requirement compliance | |
| CN110727580A (en) | Response data generation method, full-flow interface data processing method and related equipment | |
| CN107943465A (en) | A kind of method and device for generating HTML form | |
| KR102226463B1 (en) | UI/UX solution providing server linked with process automation program, process automation method using the same, and computer program executing the same | |
| CN109542431A (en) | Control property analysis method, device, electronic equipment and storage medium | |
| CN112379888A (en) | Code change analysis method | |
| US10460019B2 (en) | Computer implemented system and method for transforming web content for display on multiple form factors | |
| CN112182552A (en) | Real-name authentication method and device, electronic equipment and storage medium | |
| CN111865726B (en) | Service message testing method, device, computer system and storage medium | |
| CN114296833A (en) | Business interface component configuration method and device, equipment and medium thereof | |
| CN113886216A (en) | Interface test and tool configuration method, device, electronic equipment and storage medium | |
| CN113312900A (en) | Data verification method and device | |
| US20220269795A1 (en) | Methods and systems to automatically generate natural language insights for software components from calculated scores | |
| CN116909873A (en) | Test method and device, terminal and storage medium | |
| CN116679927A (en) | Page configuration method and device, storage medium and computer equipment | |
| CN117908977A (en) | Application system access method and system |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: Room 221, 2 / F, block C, 18 Kechuang 11th Street, Daxing District, Beijing, 100176 Applicant after: Jingdong Technology Holding Co.,Ltd. Address before: Room 221, 2 / F, block C, 18 Kechuang 11th Street, Daxing District, Beijing, 100176 Applicant before: Jingdong Digital Technology Holding Co., Ltd |