CN114546872B - Certificate management testing method and device, computer equipment and storage medium - Google Patents

Abstract

The utility model provides a voucher management test method, a device, a computer device and a storage medium, which pre-configures the incidence relation of the number information of the voucher to be verified, the service identification to be verified and the voucher verification test interface, wherein the test method comprises the following steps: receiving a service request; searching a request service identifier and a request certificate number in the service request in the association relationship, if the search fails, verifying a normal interface according to a certificate corresponding to the request service identifier, and calling an interface service for processing; if the search is successful, the interface service is called to process according to the searched service identification to be verified and the certificate verification test interface associated with the certificate number to be verified. According to the method, the construction of a gray level issuing environment can be omitted, the testing interface service can be verified in a real issuing environment by pre-configuring the incidence relation among the number information of the certificate to be verified, the service identification to be verified and the certificate verification testing interface service, the comprehensiveness of verification is guaranteed, and the verification error is reduced.

Description

A credential management test method, device, computer equipment and storage medium

technical field

This article relates to the field of testing, in particular to a credential management testing method, device, computer equipment and storage medium.

Background technique

Today, deposits, financial management, shopping, loans, etc. in people's lives all depend on voucher numbers, such as bank card numbers. Shopping through bank cards, no need to bring cash, no need to write checks, no need to show ID card, safe and reliable, not restricted by region or banking institution, every transaction is recorded. Based on regulatory requirements and banking business development needs, all types of transactions require credential verification when responding, and the credential verification for each type of transaction is different. When the credential verification algorithm is updated, it needs to be tested, and it can be put into use only after the test is passed. The verification method of the credential verification algorithm in the prior art is: simulate the release of the credential verification algorithm in the test environment (that is, build a gray release environment), pass the test credential The number is verified against the credential verification algorithm.

The verification method of the above credential verification algorithm has the following defects: the test environment is different from the real production environment, and the credential number used for verification is not the real credential number of the user. Therefore, there are problems of incomplete verification and large verification errors. When the credential verification algorithm is put into production There will also be a risk that users will not be able to handle business, which will cause adverse social impacts, lead to the loss of users, and receive a series of negative impacts such as notifications from regulatory agencies.

Contents of the invention

This paper is used to solve the problem of incomplete verification and large verification errors in the way of verifying the credential verification algorithm in the test environment in the prior art.

In order to solve the above technical problems, the first aspect of this paper provides a credential management testing method, which pre-configures the relationship between the credential number information to be verified, the business identifier to be verified, and the credential verification test interface. The test method includes:

Receive business requests;

Searching for the requested service identifier and request voucher number in the service request in the association relationship, and if the search fails, verifying the normal interface according to the voucher corresponding to the requested service identifier. Call the interface service for processing; if the search is successful, then verify the test interface based on the searched business identifier to be verified and the certificate number associated with the certificate number to be verified. Call the service for processing.

As a further embodiment of this paper, searching for the request service identifier and request voucher number in the service request in the association relationship includes:

Searching for the requested voucher number in the voucher number information to be verified in the association relationship;

If the search is successful, then search for the requested service identifier in the service identifier to be verified associated with the found certificate number to be verified;

If the search is successful, it is determined that the search for the requested service identifier and request voucher number in the service request in the association relationship is successful.

As a further embodiment of this document, if the execution result of the credential verification test interface service is failure, call the interface service for processing according to the normal credential verification interface corresponding to the requested service identifier.

As a further embodiment herein, the process of determining the number information of the certificate to be verified includes:

For unlinked user vouchers, set the voucher number information to be verified according to the voucher number managed by the preset staff;

For the credentials of the associated user, set it as follows:

Obtain historical service requests within a predetermined time period;

According to the historical business request, screen out users whose transaction volume is greater than a predetermined value under each business identifier and each user profile;

Use the voucher number information of users screened out under each business identifier and each user portrait as the voucher number information to be verified for each business identifier.

As a further embodiment of this paper, the transaction device attribute information is also pre-configured;

Before searching for the request service identifier and request voucher number in the service request in the association relationship, it also includes:

Find the transaction device attribute information in the service request in the pre-configured transaction device attribute information, where the transaction device attribute information includes one or more of the transaction device identification, transaction device attribution, and transaction device type;

If the search is successful, then perform the steps of searching for the request service identifier and request voucher number in the service request in the association relationship;

If the search fails, the normal interface is verified according to the certificate corresponding to the requested service identifier, and the interface service is invoked for processing.

As a further embodiment herein, the credential verification normal interface service includes a plurality of normal sub-interface services, and the credential verification test interface service includes a plurality of test sub-interface services;

When processing according to the credential verification test interface service, call the corresponding test sub-interface service to perform verification according to the execution sequence of the test sub-interface service in the credential verification test interface service. When a test sub-interface service fails to verify, call the test The normal sub-interface service corresponding to the sub-interface service and the normal sub-interface service after the normal sub-interface service perform verification.

As a further embodiment herein, the credential management testing method also includes:

According to the execution result of each credential verification test interface service, calculate the verification index value of each credential verification test interface service;

Determine whether the verification index value of each credential verification test interface service conforms to the preset response index value, if so, use the credential verification test interface service to replace the corresponding credential verification normal interface service, and delete the relevant information of the credential verification test interface from the association relationship .

A second aspect of this document provides a credential management testing device, comprising:

The storage unit is used to pre-configure the relationship between the voucher number information to be verified, the business identifier to be verified, and the voucher verification test interface service;

a receiving unit, configured to receive a service request;

A verification unit, configured to search for the requested service identifier and request voucher number in the service request in the association relationship, and if the search fails, verify the normal interface according to the voucher corresponding to the requested service identifier, and call the interface service for processing; If the search is successful, call the interface service for processing according to the certificate verification test interface associated with the searched business identifier and the certificate number to be verified.

The third aspect of this document provides a computer device, including a memory, a processor, and a computer program stored on the memory, when the computer program is run by the processor, the method according to any of the preceding embodiments is executed instructions.

A fourth aspect of this document provides a computer storage medium, on which a computer program is stored, and when the computer program is run by a processor of a computer device, instructions of the method according to any one of the preceding embodiments are executed.

The credential management testing method and device provided in this paper can pre-configure the relationship between the credential number information to be verified, the business identifier, and the credential verification test interface, and determine whether the user credential number in the user service request needs to perform test verification through the correlation relationship. Eliminate the construction of a gray-scale release environment, arrange the certificate verification test interface service in the real release environment, and verify the certificate verification test interface service according to the certificate number in the real environment to ensure the comprehensiveness of the verification and reduce the verification error.

In order to make the above and other objects, features and advantages of this document more comprehensible, preferred embodiments will be described in detail below together with the attached drawings.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of this paper or the prior art, the accompanying drawings that need to be used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the accompanying drawings in the following description are only For some embodiments herein, those skilled in the art can also obtain other drawings based on these drawings without creative effort.

Fig. 1 shows the structural diagram of the voucher management test system of the embodiment of this paper;

Fig. 2 shows the first flowchart of the certificate management testing method of the embodiment herein;

Fig. 3 shows the second flowchart of the certificate management testing method of the embodiment herein;

Fig. 4 shows the flowchart of the process of determining the voucher number information to be verified according to the embodiment herein;

Fig. 5 shows the third flowchart of the certificate management testing method of the embodiment herein;

Fig. 6 shows the first structural diagram of the credential management testing device of the embodiment of this paper;

Fig. 7 shows the second structural diagram of the credential management test device of the embodiment of this paper;

FIG. 8 shows a structural diagram of a computer device in the embodiment of this paper.

Explanation of reference symbols:

110. database;

120. Trading equipment;

130. server;

610. Storage unit;

620. Receiving unit;

630. Verification unit;

611. The first storage module;

612. The second storage module;

631. Check the module;

632. Interface call module;

802. Computer equipment;

804. Processor;

806. memory;

808. Driving mechanism;

810. Input/output module;

812. Input device;

814. Output device;

816. Presentation equipment;

818. Graphical user interface;

820. Network interface;

822. Communication link;

824. Communication bus.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments herein in conjunction with the accompanying drawings in the embodiments herein. Obviously, the described embodiments are only some of the embodiments herein, not all of them. Based on the embodiments herein, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts fall within the scope of protection herein.

It should be noted that the terms "first" and "second" in the description herein and the above drawings are used to distinguish similar objects, but not necessarily used to describe a specific sequence or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances such that the embodiments herein described herein can be practiced in sequences other than those illustrated or described herein. In addition, the terms "comprising" and "having" in the description and claims and the above drawings, as well as any variations thereof, are intended to cover non-exclusive inclusion, for example, processes, methods, A device, product or device is not necessarily limited to those steps or elements explicitly listed, but may include other steps or elements not explicitly listed or inherent to the process, method, product or device.

This specification provides the operation steps of the method described in the embodiment or flow chart, but more or less operation steps may be included based on routine or non-creative work. The sequence of steps enumerated in the embodiments is only one of the execution sequences of many steps, and does not represent the only execution sequence. When an actual system or device product is executed, it may be executed sequentially or in parallel according to the methods shown in the embodiments or drawings.

It should be noted that the credential management test method and device in this paper can be used in the financial field, and can also be used in any field other than the financial field, such as membership card business management. The application field of the credential management test method and device in this paper is not limited . The voucher number described in this article is the account number for asset management, taking bank vouchers as an example, including non-blank vouchers and blank vouchers. Non-blank credentials refer to credentials of associated users, including but not limited to bank cards, passbooks, etc. Blank vouchers refer to vouchers of unlinked users, including but not limited to fund certificates, transfer checks, cash checks, bank drafts, bond collection documents, letter of credit amendments, etc.

It should be noted that user portraits (including but not limited to user gender, age, occupation, income, etc.) and business request data (including but not limited to data used for analysis, stored data, and displayed data) etc.), are all information and data authorized by the user or fully authorized by all parties.

In an embodiment herein, a certificate management testing system is provided, as shown in FIG. 1 , including: a database 110 , a transaction device 120 , and a server 130 .

The database 110 stores the pre-configured relationship between the voucher number information to be verified, the service identifier to be verified, and the voucher verification test interface.

Wherein, the voucher number information to be verified includes multiple voucher numbers of various types, and each voucher number can be a full voucher number or a partial voucher number, for example, the voucher number is normally 18 digits, and only some digits can be given in the voucher number information to be verified (for example, the first 6 digits), the other digits can take any value. The certificate number to be verified includes the certificate of the associated user and the certificate of the unassociated user. Among them, the certificate of the associated user refers to the certificate that has been associated and matched with the user, and the business type involved is the business of publicizing the certificate, such as a bank debit card. The business type involved includes but is not limited to transfer, withdrawal, deposit, etc. The user mentioned in this article refers to the person who handles business with the credential provider. Vouchers of unassociated users refer to the vouchers that are still in the institution to which the voucher belongs (such as a bank) and are not associated with the user. Destroy etc. Voucher storage is a process of creating vouchers in the system from scratch. Voucher requisition is the business of applying for vouchers from lower-level organizations to higher-level organizations. Voucher approval is the business of approving vouchers applied by lower-level institutions by higher-level institutions. Voucher submission and voucher requisition are the opposite process, and the outlet initiates the submission business, and the higher-level organization confirms the storage according to the business content. Voucher recycling refers to the business of recycling vouchers that are no longer used. Voucher destruction refers to the business of destroying vouchers.

For the vouchers of unassociated users, the voucher number to be verified is set by the voucher number managed by the preset staff, where the preset staff is the development and maintenance personnel of the voucher management system. For banks, the preset staff is, for example, Teller, credential manager.

For the certificate of the associated user, the certificate number to be verified can be configured in the manner of the subsequent embodiment shown in FIG. 4 .

The service identifier to be verified can be determined according to the updated service and the newly added service, that is, the service identifier of the updated service and the newly added service is set as the service identifier to be verified. As shown in Table 1, the voucher number information to be verified corresponding to each service identifier to be verified may be the same or different, which is not limited herein.

The credential verification test interface in the association relationship is an interface identifier, through which the interface service corresponding to the interface identifier can be invoked. The interface service described in this article has processing logic for processing business requests and processing corresponding to each business The logic is different, which is not limited in this article. Specifically, the following takes the deposit business, withdrawal business and transfer business as examples to illustrate the processing logic of the interface service:

1. Interface service corresponding to deposit business

(1) Restriction check: Check whether the account has account restrictions, and choose whether to terminate the transaction according to the actual situation;

(2) Customer check: Check the basic information of the customer, including whether the customer has been logged out, whether the customer status is normal, etc.;

(3) Basic account check:

1) Account general inspection: whether the account status is normal, whether it is canceled or not, whether it is a non-business account;

2) Verification of private accounts: tellers are not allowed to operate their own accounts;

3) Verification of public accounts: checking the validity period of account attributes, checking the validity period of capital verification accounts, and automatically prompting when temporary accounts expire;

(4) Deposit: Realize the update of the account balance, the update of the teller's tail box, generate the accounting flow and share it with the general ledger system.

2. Interface services corresponding to deposit business

(1) Customer basic check: Check whether the customer has been logged out, whether it is blacklisted, or frozen;

(2) Basic check of account: check of account status (account cancellation, long-term suspension, transfer to non-business, etc.), private customer check;

Teller authority (not allowed to operate their own accounts), check of public account attributes, check of validity period of capital verification account, check of validity period of temporary account account;

(3) Restriction check: check the corresponding customer-level restrictions, attribute-level restrictions, and account-level restrictions of the account respectively;

(4) Bill information check: When there is bill information in the fund transaction process, check the relevant information (bill account relationship, bill issuance date, loss report status, certificate sales status);

(5) The main logic of the current withdrawal event: organize debit flow and cash tail box flow, operation service to update the tail box, deposit service to check the debit account, balance check, etc., update the account balance, and register the flow.

3. Interface service corresponding to transfer business

(1) Internal account transfer transaction check: check whether the two accounts of the transfer transaction are internal accounts;

(2) Bill information check: When there is bill information in the fund transaction process, check the relevant information (bill account relationship, bill issuance date, loss report status, certificate sales status);

(3) Basic customer verification: Check whether the customer has been logged out, whether it is blacklisted, or frozen;

(4) Basic checking of accounts: checking of account status (account cancellation, long-term suspension, transfer to non-business, etc.), checking of private customers;

Teller authority (not allowed to operate their own accounts), check of public account attributes, check of validity period of capital verification account, check of validity period of temporary account account;

(5) Foreign currency transfer check: check whether it is a foreign currency transaction;

(6) Restriction check: check the corresponding customer-level restrictions, attribute-level restrictions, and account-level restrictions of the account respectively;

(7) Holiday check: check whether the trading day is a holiday;

(8) Current account transfer: organize mainstream flow, debit sub-flow, credit sub-flow transactions and charge fees according to the transaction.

Table 1

The database 110 described herein may be a database management system, and may also be a file system.

The transaction device 120 is used to receive service requests. Taking the bank certificate management test system as an example, transaction equipment includes but is not limited to teller terminal equipment (computer equipment, PAD, wearable equipment, etc.), ATM machines and other equipment. Different transaction devices can issue different service requests, and this article does not limit the service requests that can be issued by each transaction device. The business request depends on the business functions provided by the voucher management test system. Still taking the bank voucher management test system as an example, the business functions involved in the business request include but are not limited to prefabricated vouchers, voucher transfer, voucher issuance, voucher account opening, deposit, Bank withdrawals, inter-bank withdrawals, etc., transfers, signing contracts.

A production environment is arranged in the server 130, and the certificate verification test interface service and the certificate verification test normal interface service (that is, the interface service that has been fully put into production at present) are configured. can respond.

The server 130 is used to search for the request service ID and the request voucher number in the service request in the association relationship. If the search fails, then verify the normal interface according to the voucher corresponding to the request service ID, and call the interface service for processing (that is, call the corresponding ID of the request service ID) Voucher verification normal interface service for processing); if the search is successful, call the interface service for processing according to the found out business identifier to be verified and the certificate verification test interface associated with the certificate number to be verified (that is, call the found out to be verified business ID and The certificate verification test interface service associated with the certificate number to be verified shall be processed). Specifically, the server 130 may be a large computer, or a medium or small computer. In order to ensure the validity of the service response, the server 130 described herein may also be a server cluster.

During specific implementation, for the search efficiency of the request service identifier and the request voucher number in the service request, the request service identifier and the request voucher number in the service request are searched in the association relationship, including:

First search for the requested voucher number in the voucher number information to be verified in the association relationship;

If the search for the request voucher number is successful, then search for the request service identifier in the service identifier to be verified associated with the found voucher number to be verified;

If the search for the requested service identifier is successful, it is determined that the search for the requested service identifier and the request voucher number in the service request in the association relationship is successful.

For example, assuming that the requested voucher number is 623132********1002, and the requested service ID is to open an account with a voucher, the requested voucher number is first found in the voucher number information to be verified in Table 1, and then in Table 1 623132********1002 in 623132********1002 is associated with the service ID to be verified, and the voucher account opening is found. From this, it can be determined that the search for the requested business ID and the requested voucher number in the business request in the association relationship is successful.

In this embodiment, by pre-configuring the association relationship between the certificate number information to be verified, the business identifier, and the certificate verification test interface service, it is determined whether the user certificate number in the user service request needs to perform test verification through the association relationship, which can save the gray release environment The construction can improve the efficiency of verification and ensure the stability of the system. Arrange the certificate verification test interface service in the real release environment, and verify the certificate verification test interface service according to the certificate number in the real environment to ensure the comprehensiveness of the verification and reduce the verification error.

In an embodiment of this paper, a credential management testing method is also provided, the method runs in the above-mentioned server 130, before the method runs, pre-configures the association relationship between the credential number information to be verified, the business identifier to be verified, and the credential verification test interface service , specifically, as shown in Figure 2, the test methods include:

Step 210, receiving a service request;

Step 220, search for the requested service identifier and request voucher number in the service request in the association relationship, if the search fails, execute step 230; if the search succeeds, execute step 240;

Step 230, verify the normal interface according to the credential corresponding to the requested business identifier, and call the interface service for processing;

Step 240, call the interface service for processing according to the credential verification test interface associated with the service identifier to be verified and the credential number to be verified.

In this embodiment, through the association relationship, it is determined whether the user certificate number in the user service request needs to be tested and verified, which can save the construction of a gray-scale release environment, and arrange the certificate verification test interface service in the real release environment. According to the certificate number in the real environment Verification credential verification test interface service to ensure the comprehensiveness of verification and reduce verification errors.

In an embodiment herein, the above step 220 includes:

Find the requested voucher number in the voucher number information to be verified in the association relationship;

If the search is successful, search for the request service identifier in the service identifier to be verified associated with the found certificate number to be verified;

If the search is successful, it is determined that the search for the request service identifier and the request voucher number in the service request in the association relationship is successful.

In order to avoid the service request response failure due to the incomplete update business interface service, in an embodiment of this paper, as shown in FIG. Request the certificate corresponding to the service ID to verify the normal interface, and call the interface service for processing.

In this embodiment, when the credential verification test interface service fails to process, it can return to call the normal interface service for processing, and can ensure that the requested credential number in the business request can be verified normally.

In an embodiment of this document, as shown in Figure 4, for the credentials of the associated users, the following methods can be used to determine the voucher number information to be verified:

Step 410, acquiring historical service requests within a predetermined time period.

In this step, the predetermined time period is, for example, the last three months, half a year, etc., and the predetermined time period is not specifically limited herein. Historical service requests include service requests for various services, among which, service requests include request service identification, request voucher number and user information, among which user information includes but not limited to name, age, occupation, ID number, home address, etc.

Step 420, according to historical service requests, screen out users under each service ID and each user profile whose transaction volume is greater than a predetermined value.

This step can eliminate users who infrequently initiate service requests, and retain users who often initiate service requests within a predetermined period of time, that is, active users, thereby ensuring the testing efficiency of interface services.

The user portraits described in this article are used to identify user characteristics, including but not limited to gender, age group, occupation, income range, region, etc. This article does not specifically limit user portraits. The predetermined value can be set according to actual needs.

Step 430, use the voucher number information of users screened out under each service identifier and each user portrait as the voucher number information to be verified for each service identifier.

In this embodiment, the voucher numbers of each business identifier and each user portrait are randomly selected from the existing voucher numbers that have been opened, and the screened voucher numbers are used as the voucher numbers to be verified, which can ensure the comprehensiveness of the verification, and can Ensure that the interface service verification is completed within a certain period of time.

In an embodiment of this paper, in order to improve the dimension and efficiency of business verification, before the implementation of the credential management test method, pre-configure the credential number information to be verified, the business identifier to be verified and the relationship between the credential verification test interface service, and transaction device attribute information. As shown in Figure 5, the test methods include:

Step 510, receiving a service request.

Step 520, search the transaction device attribute information in the business request in the pre-configured transaction device attribute information, if the search fails, execute step 530, and if the search succeeds, execute step 540.

Wherein, the attribute information of the transaction device includes one or more of the transaction device identifier, the location of the transaction device, and the type of the transaction device, wherein the transaction device identifier can be set according to the job number of the person using the transaction device. The transaction devices mentioned in this article include but are not limited to user smart terminals and teller business terminals.

Step 530, verify the normal interface service according to the certificate corresponding to the requested service identifier for processing.

Step 540, search for the requested service identifier and request voucher number in the service request in the association relationship, if the search fails, execute step 530; if the search succeeds, execute step 550.

Step 550, call the interface service for processing according to the certificate verification test interface associated with the service identifier to be verified and the certificate number to be verified.

In this embodiment, the test of the credential verification test interface service is performed by limiting the business requests initiated by some transaction devices, which can ensure the controllability of the test verification and avoid causing bad performance to most users when the test interface service is abnormal.

In the first implementation of this document, the certificate verification normal interface service includes multiple normal sub-interface services, and the certificate verification test interface service includes multiple test sub-interface services. For the normal interface service and the test interface service corresponding to the same service, an association relationship between the normal sub-interface service in the normal interface service and the test sub-interface service in the test interface service is established in advance.

When processing according to the credential verification test interface service, call the corresponding test sub-interface service to perform verification according to the execution sequence of the test sub-interface service in the credential verification test interface service. The relationship calls the normal sub-interface service corresponding to the test sub-interface service and the normal sub-interface service after the normal sub-interface service to perform verification.

In this embodiment, when an exception occurs during the execution of the credential verification test interface service, it can switch to the normal sub-interface service in time to continue execution, thereby improving the speed and accuracy of credential verification.

In an embodiment of this document, after the credential verification test interface service goes online for a period of time, the following process is also performed to complete the test of the test interface service:

(1) Calculate the verification index value of each certificate verification test interface service according to the execution results of each certificate verification test interface service.

Among them, verification indicators include transaction volume, success rate, response time, etc. The transaction volume is the number of times of processing, the success rate is the ratio of the successful verification of the test interface service to the transaction volume, and the response time refers to the execution time of the test interface service.

(2) Determine whether the verification index value of each credential verification test interface service conforms to the preset response index value, if so, use the credential verification test interface service to replace the corresponding credential verification normal interface service, and delete the credential verification test interface from the association relationship Information about the service.

Wherein, each preset response index value can be set according to actual needs, which is not limited in this paper.

Based on the same inventive concept, this document also provides a credential management testing device, as described in the following embodiments. Since the principle of the device to solve the problem is similar to that of the credential management test method, the implementation of the credential management test device can refer to the credential management test method, and the repetition will not be repeated.

Specifically, as shown in Figure 6, the credential management test device includes:

The storage unit 610 is used to pre-configure the relationship between the certificate number information to be verified, the business identifier to be verified and the certificate verification test interface service;

a receiving unit 620, configured to receive a service request;

The verification unit 630 is used to search for the requested service identifier and request voucher number in the service request in the association relationship, if the search fails, then verify the normal interface according to the voucher corresponding to the requested service identifier, and call the interface service for processing; if the search is successful , call the interface service for processing according to the credential verification test interface associated with the service ID to be verified and the credential number to be verified.

Further, as shown in FIG. 7, the storage unit 610 further includes: a first storage module 611 and a second storage module 612, the first storage module 611 is used to store the voucher number information to be verified, and the second storage module 612 is used to store the information to be verified. Verify the association relationship between the certificate number information, the business identifier to be verified, and the certificate verification test interface service.

The verification unit 630 further includes: a checking module 631 and an interface calling module 632, the checking module 631 is used to search the request voucher number in the service request from the first storage module 611, and if the search is successful, then search the service from the second storage module 612 The request service ID and request voucher number in the request. The interface call module 632 is used to call the interface service for processing according to the inspection result of the inspection module 631. Specifically, if the search fails, then verify the normal interface according to the certificate corresponding to the requested business identifier, and call the interface service for processing; Find out the certificate verification test interface associated with the service ID to be verified and the certificate number to be verified, and call the interface service for processing.

In an embodiment of this paper, a remote computer device is also provided. As shown in FIG. 8, a computer device 802 may include one or more processors 804, such as one or more central processing units (CPUs), each A unit can implement one or more hardware threads. The computer device 802 can also include any memory 806, which is used to store any kind of information such as codes, settings, data, computer programs, etc., and when the computer program is run by the processor 804, it can perform the operations described in any of the preceding embodiments. method directive. Non-limiting, for example, the memory 806 may include any one or a combination of the following: any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, and so on. More generally, any memory can use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent a fixed or removable component of computer device 802 . In one instance, when processor 804 executes the associated instructions stored in any memory or combination of memories, computer device 802 may perform any operation of the associated instructions. The computer device 802 also includes one or more drive mechanisms 808 for interfacing with any memory, such as a hard disk drive, an optical disk drive, or the like.

Computer device 802 may also include an input/output module 810 (I/O) for receiving various inputs (via input device 812) and for providing various outputs (via output device 814). One particular output mechanism may include a presentation device 816 and an associated graphical user interface 818 (GUI). In other embodiments, the input/output module 810 (I/O), the input device 812 and the output device 814 may not be included, and it is only used as a computer device in the network. Computer device 802 may also include one or more network interfaces 820 for exchanging data with other devices via one or more communication links 822 . One or more communication buses 824 couple together the components described above.

Communication link 822 can be implemented in any manner, for example, through a local area network, a wide area network (eg, the Internet), a point-to-point connection, etc., or any combination thereof. Communication link 822 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc. governed by any protocol or combination of protocols.

Corresponding to the methods in Figures 2 to 5, the embodiments of this document also provide a computer-readable storage medium, on which a computer program is stored, and the computer program executes the steps of the above-mentioned method when the computer program is run by a processor .

The embodiments herein also provide a computer-readable instruction, wherein when the processor executes the instruction, the program therein causes the processor to execute the methods shown in FIG. 2 to FIG. 5 .

It should be understood that in the various embodiments herein, the sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the implementation of the embodiments herein. process constitutes any qualification.

It should also be understood that in the embodiments herein, the term "and/or" is merely an association relationship describing associated objects, indicating that there may be three relationships. For example, A and/or B may mean that A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this article generally indicates that the contextual objects are an "or" relationship.

Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the relationship between hardware and software Interchangeability. In the above description, the composition and steps of each example have been generally described according to their functions. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. A skilled artisan may implement the described functionality using different methods for each particular application, but such implementation should not be considered beyond the scope of this document.

Those skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiment, and will not be repeated here.

In the several embodiments provided herein, it should be understood that the disclosed systems, devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solutions in the embodiments herein.

In addition, each functional unit in each of the embodiments herein may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution in this article is essentially or part of the contribution to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments herein. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes. .

In this paper, specific examples have been used to illustrate the principles and implementation methods of this paper. The description of the above embodiments is only used to help understand the method and core ideas of this paper; meanwhile, for those of ordinary skill in the art, according to the ideas of this paper , there will be changes in specific implementation methods and application ranges. In summary, the contents of this specification should not be construed as limiting this text.

Claims (9)

1. A credential management test method, characterized in that, pre-configuring the association relationship between the credential number information to be verified, the business identifier to be verified and the credential verification test interface, and arranging the credential verification test interface in the real publishing environment, the credential number is the management asset account, the test methods include: Receive business requests from users; Search the request service identifier and the request certificate number in the service request in the association relationship, if the search fails, then verify the normal interface call interface service according to the certificate corresponding to the request service identifier; if the search is successful, then process according to The credential verification test interface associated with the found business identifier to be verified and the credential number to be verified is processed by invoking the interface service; The process of determining the voucher number information to be verified includes: For unlinked user vouchers, set the voucher number information to be verified according to the voucher number managed by the preset staff; For the credentials of the associated user, set it as follows: Obtain historical service requests within a predetermined time period; According to the historical business request, screen out users whose transaction volume is greater than a predetermined value under each business identifier and each user profile; Use the voucher number information of users screened out under each business identifier and each user portrait as the voucher number information to be verified for each business identifier. 2. The voucher management testing method according to claim 1, wherein searching for the request service identifier and the request voucher number in the service request in the association relationship includes: Searching for the requested voucher number in the voucher number information to be verified in the association relationship; If the search is successful, then search for the requested service identifier in the service identifier to be verified associated with the found certificate number to be verified; If the search is successful, it is determined that the search for the requested service identifier and request voucher number in the service request in the association relationship is successful. 3. The credential management testing method according to claim 1, wherein if the execution result of the credential verification test interface service is failure, then call the interface service for processing according to the credential verification normal interface corresponding to the request service identifier. 4. The voucher management testing method according to claim 1, characterized in that, the transaction device attribute information is also pre-configured; Before searching for the request service identifier and request voucher number in the service request in the association relationship, it also includes: Find the transaction device attribute information in the service request in the pre-configured transaction device attribute information, where the transaction device attribute information includes one or more of the transaction device identification, transaction device attribution, and transaction device type; If the search is successful, then perform the steps of searching for the request service identifier and request voucher number in the service request in the association relationship; If the search fails, the normal interface is verified according to the certificate corresponding to the requested service identifier, and the interface service is invoked for processing. 5. The credential management testing method according to claim 1, wherein the normal interface service of the credential verification includes a plurality of normal sub-interface services, and the credential verification test interface service includes a plurality of test sub-interface services; When processing according to the credential verification test interface service, call the corresponding test sub-interface service to perform verification according to the execution sequence of the test sub-interface service in the credential verification test interface service. When a test sub-interface service fails to verify, call the test The normal sub-interface service corresponding to the sub-interface service and the normal sub-interface service after the normal sub-interface service perform verification. 6. The credential management test method according to claim 1, wherein the test method further comprises: According to the execution result of each credential verification test interface service, calculate the verification index value of each credential verification test interface service; Determine whether the verification index value of each certificate verification test interface service conforms to the preset response index value, if so, use the certificate verification test interface service to replace the corresponding certificate verification normal interface service, and delete the relevant certificate verification test interface service from the association relationship information. 7. A credential management test device, characterized in that, comprising: The storage unit is used to pre-configure the relationship between the voucher number information to be verified, the business identifier to be verified, and the voucher verification test interface, wherein the voucher verification test interface is arranged in a real publishing environment, and the voucher number is an account number for managing assets; a receiving unit, configured to receive a service request sent by a user; A verification unit, configured to search for the requested service identifier and request voucher number in the service request in the association relationship, and if the search fails, verify the normal interface according to the voucher corresponding to the requested service identifier, and call the interface service for processing; If the search is successful, call the interface service for processing according to the certificate verification test interface associated with the business identifier to be verified and the certificate number to be verified; The process of determining the voucher number information to be verified includes: For unlinked user vouchers, set the voucher number information to be verified according to the voucher number managed by the preset staff; For the credentials of the associated user, set it as follows: Obtain historical service requests within a predetermined time period; According to the historical business request, screen out users whose transaction volume is greater than a predetermined value under each business identifier and each user profile; Use the voucher number information of users screened out under each business identifier and each user portrait as the voucher number information to be verified for each business identifier. 8. A computer device, comprising a memory, a processor, and a computer program stored on the memory, wherein, when the computer program is run by the processor, the computer program according to any one of claims 1-6 is executed. Instructions for the method. 9. A computer storage medium, on which a computer program is stored, wherein, when the computer program is run by a processor of a computer device, instructions according to the method according to any one of claims 1-6 are executed.

Images