Interface management method and apparatus, electronic device, and storage medium

By verifying account permissions and generating target application forms, the problem of insufficient permission separation in existing API interface management is solved, achieving higher interface management security and data protection.

CN114722425BActive Publication Date: 2026-04-10BEIJING XUEZHITU NETWORK TECH
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
BEIJING XUEZHITU NETWORK TECH
Filing Date
2022-04-01
Publication Date
2026-04-10

AI Technical Summary

Technical Problem

Existing API interface management software cannot guarantee the separation of permissions for different departments and personnel, resulting in insufficient interface security.

Method used

By receiving account information, verifying its permissions, generating the target application form, and sending it to a second account with approval authority, the system achieves permission management for different accounts, thereby improving the security of interface management.

Benefits of technology

This allows different accounts to have different management permissions for API interfaces, improving the security of interface management and data security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114722425B_ABST
    Figure CN114722425B_ABST
Patent Text Reader

Abstract

The application provides an interface management method and device, electronic equipment and a storage medium, and the method comprises the following steps: receiving an application request for applying an operation target interface submitted by a first account, wherein the application request at least carries account information corresponding to the first account; verifying the account information; if the first account has the permission to operate the target interface, generating a target application form based on the account information and interface information corresponding to the target interface; and sending the target application form to a second account. According to the received application request for applying the operation target interface, the account information corresponding to the first account carried in the application request is verified to determine whether the first account has the application permission, if the first account has the application permission, a target application form is generated for the first account, and then the target application form is submitted to the second account with the approval permission, so that different accounts have different management permissions of API interfaces, and the security of interface management is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically, to an interface management method, apparatus, electronic device, and storage medium. Background Technology

[0002] With the continuous advancement of technology, the internet industry is also rapidly developing. API interfaces are an important specification for software development, and effective API interface management will enhance the work efficiency of developers and other users.

[0003] Currently, standard API management software includes Swagger, RAP, and APIDOC. Swagger simplifies API deployment, management, and usage; RAP uses mock functionality to dynamically generate mock data, significantly improving development efficiency; and APIDOC generates web API documentation based on code comments, making maintenance easier. However, different departments within a company should have different API access permissions, and different people should manage different APIs. Existing API management systems cannot guarantee API security. Summary of the Invention

[0004] In order to solve the above-mentioned technical problems, or at least partially solve the above-mentioned technical problems, the present invention provides an interface management method, apparatus, electronic device and storage medium.

[0005] In a first aspect, the present invention provides an interface management method, the method comprising: receiving an application request submitted by a first account for applying to operate a target interface, wherein the application request carries at least account information corresponding to the first account; verifying the account information to verify whether the first account has permission to operate the target interface; if the first account has permission to operate the target interface, generating a target application form based on the account information and interface information corresponding to the target interface; and sending the target application form to a second account, wherein the second account has permission to approve applications to operate the target interface.

[0006] Optionally, before receiving the application request submitted by the first account for applying to operate the target interface, the method further includes: obtaining interface information of the target interface, wherein the interface information includes basic information describing the target interface and attribute information defining the target interface, the attribute information including at least the applicant with the authority to apply to operate the target interface, the approver with the authority to approve the application to operate the target interface, the operation type included in the application operation, and the approval status; and creating an application form for applying to operate the target interface based on the basic information and the attribute information.

[0007] Optionally, the verifying the account information to verify whether the first account has the permission to operate the target interface comprises: obtaining attribute information predefined for the target interface to determine target account information corresponding to an applicant in the attribute information; matching the account information with the target account information; if the account information matches the target account information, determining that the first account has the permission to apply for operating the target interface; otherwise, determining that the first account does not have the permission to apply for operating the target interface.

[0008] Optionally, the application request further carries a target operation type of applying for operating the target interface, and if the first account has the permission to operate the target interface, the target application form is generated based on the account information and interface information corresponding to the target interface, comprising: when it is determined that the first account has the permission to apply for operating the target interface, obtaining basic information and attribute information of the target interface; generating a target application form corresponding to the application request according to the account information, the target operation type, the basic information of the target interface and the attribute information of the target interface.

[0009] Optionally, the sending the target application form to a second account comprises: searching, from the attribute information of the target interface, a second account corresponding to an approval party having the permission to approve the application for operating the target interface; sending an approval request carrying the target application form to the second account, so that the second account responds to the approval request and approves the target application form.

[0010] Optionally, after the target application form is sent to the second account, the method further comprises: receiving an approval opinion submitted by the second account, wherein the approval opinion is an approval result formed by the second account approving the target application form; and sending the approval opinion to the first account.

[0011] Optionally, the method further comprises: receiving a query request submitted by a target account, wherein the target account is any one of the first account and the second account, and the query request is used to request to view at least one of the following: an application form historically applied for by the target account, an application form historically approved by the target account, an application form currently to be approved by the target account, and an interface that the target account has the permission to operate; and responding to the query request.

[0012] In a second aspect, the present application provides an interface management device, comprising: a first receiving module configured to receive an application request for applying an operation on a target interface submitted by a first account, wherein the application request carries account information corresponding to the first account; a verifying module configured to verify the account information to verify whether the first account has a permission to operate the target interface; a generating module configured to generate a target application form based on the account information and interface information corresponding to the target interface when the first account has the permission to operate the target interface; and a first sending module configured to send the target application form to a second account, wherein the second account has a permission to approve the application of operating the target interface.

[0013] Optionally, the device further comprises: an obtaining module configured to obtain interface information of the target interface before the first receiving module receives the application request for applying an operation on the target interface submitted by the first account, wherein the interface information comprises basic information for describing the target interface and attribute information for defining the target interface, and the attribute information at least comprises an applicant having a permission to apply an operation on the target interface, an approver having a permission to approve the application of operating the target interface, an operation type included in the application, and an approval state; and a creating module configured to create an application form for applying an operation on the target interface according to the basic information and the attribute information.

[0014] Optionally, the verifying module comprises: a first obtaining unit configured to obtain attribute information predefined for the target interface to determine target account information corresponding to the applicant in the attribute information; a matching unit configured to match the account information with the target account information; and a determining unit configured to determine that the first account has the permission to apply an operation on the target interface when the account information matches the target account information, or otherwise, determine that the first account does not have the permission to apply an operation on the target interface.

[0015] Optionally, the application request further carries a target operation type for applying an operation on the target interface, and the generating module comprises: a second obtaining unit configured to obtain the basic information and the attribute information of the target interface when it is determined that the first account has the permission to apply an operation on the target interface; and a generating unit configured to generate a target application form corresponding to the application request according to the account information, the target operation type, the basic information of the target interface, and the attribute information of the target interface.

[0016] Optionally, the first sending module comprises: a searching unit, configured to search, from the attribute information of the target interface, a second account corresponding to an approval party having the permission to apply for operating the target interface; and a sending unit, configured to send an approval request carrying the target application form to the second account, so that the second account responds to the approval request and approves the target application form.

[0017] Optionally, after the sending module sends the target application form to the second account, the device further comprises: a second receiving module, configured to receive an approval opinion submitted by the second account, wherein the approval opinion is an approval result formed by the second account approving the target application form; and a second sending module, configured to send the approval opinion to the first account.

[0018] Optionally, the device further comprises: a third receiving module, configured to receive a query request submitted by a target account, wherein the target account is any one of the first account and the second account, and the query request is used to request to view at least one of the following: an application form that the target account has historically applied for, an application form that the target account has historically approved, an application form that the target account is currently waiting to approve, and an interface that the target account has the permission to operate; and a responding module, configured to respond to the query request.

[0019] In a third aspect, the present application provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the computer program.

[0020] In a fourth aspect, the present application provides a computer readable storage medium, having a computer program stored thereon, wherein the computer program implements the steps of the above method when executed by a processor.

[0021] The technical scheme of the present application can be applied to the field of cloud service capability based on a system platform.

[0022] The interface management method provided by the embodiments of the present application verifies the account information corresponding to the first account carried in the application request according to the received application request for applying for operating the target interface to determine whether the first account has the application permission, generates a target application form for the first account if the first account has the application permission, and then submits the target application form to a second account having the approval permission, thereby realizing the management permission of different accounts for different API interfaces and improving the security of interface management. BRIEF DESCRIPTION OF DRAWINGS

[0023] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0024] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0025] Figure 1 A flowchart illustrating an interface management method provided in an embodiment of the present invention;

[0026] Figure 2 This is a schematic diagram of an application interface provided in an embodiment of the present invention;

[0027] Figure 3 An application diagram illustrating an approval interface provided in an embodiment of the present invention;

[0028] Figure 4 This is a schematic diagram of the structure of an interface management device provided in an embodiment of the present invention;

[0029] Figure 5 This is a schematic diagram of the structure of a computer device provided in an embodiment of the present invention. Detailed Implementation

[0030] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0031] Firstly, the present invention provides an interface management method that can be applied in an interface management system. Figure 1 This is a flowchart illustrating an interface management method provided in an embodiment of the present invention, as shown below. Figure 1 As shown, the method includes the following steps:

[0032] Step S102: Receive an application request submitted by the first account for applying to operate the target interface, wherein the application request carries at least the account information corresponding to the first account;

[0033] Optionally, the target interface in the embodiment can be an API interface (full name: Application Programming Interface, that is, application programming interface).

[0034] The interface management method provided by the application is executed by an interface management device, which can be a terminal device, a server or other hardware device, or software installed on a hardware device.

[0035] The server can be a standalone server or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content distribution networks (CDN), and basic cloud computing services such as big data and artificial intelligence platforms. The embodiments of the application can acquire and process related data based on artificial intelligence technology. Artificial intelligence (AI) is the use of digital computers or computer-controlled machines to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use knowledge to obtain the best results.

[0036] In specific implementation, the execution subject of the embodiment of the application can also be an API interface approval management system. A certain employee in a certain department of a company can be indicated by the first account to log in to the API interface approval management system. The account information corresponding to the first account can be the department and position information of the employee.

[0037] Further, before the step S102, the method further includes: obtaining interface information of the target interface, wherein the interface information includes basic information for describing the target interface and attribute information for defining the target interface, and the attribute information at least includes an applicant with a permission to apply for operating the target interface, an approval party with a permission to approve the application for operating the target interface, an operation type included in the application, and an approval state; and creating an application form for applying for operating the target interface according to the basic information and the attribute information.

[0038] In the embodiment, the basic information of the target interface at least includes a basic path of the interface, an access type, description information, a service party to which the interface belongs (such as a service address, a person in charge, and a department to which the person in charge belongs), and the like. According to user requirements, attribute information of the interface can be defined for the target interface, such as a single number for identifying approval, an operation type, an approval state (such as a state to be approved, an approved state, and the like), an application name for identifying a single, a department to which an application initiator belongs, an application reason, an approval party, an approval opinion, and an approval state.

[0039] The operation type of the application operation target interface includes at least online application, offline application, use application, release application, query application, query approval, approval, etc. The service address is a service address provided by a service party, for example, a service is provided by an abc website, and the service address can be http: / / www.abc.com. The access type is, for example, a use acquisition function get(). The person in charge mainly determines who to approve the single.

[0040] By defining attribute information for the target interface, a target application form is created for the target interface, so that the basic information and the predefined attribute information of the interface are covered in the application form, which is used for subsequent verification of whether the first account has the permission to apply for the operation of the target interface and whether the second account has the approval permission to approve the target application form, thereby strictly limiting the use permission of the target interface and improving the use safety of the API interface.

[0041] Taking the API interface approval management system as an example, an administrator B creates an API interface (i.e. the above target interface) in the API interface approval management system. The administrator B is the person in charge of the API interface, and the service is provided by the department where B is located. If a user A needs to apply for the online, offline, etc. operation of the API interface, A submits an online or offline application form of the API interface in the API interface approval management system, which is transferred to B. B logs in the API interface approval management system and can see the approval request, then performs approval, and the process ends. A and B can see the single in the system, and others cannot see it. The single is only related to the two persons, thereby improving the use safety of the API interface.

[0042] In step S104, the account information is verified to verify whether the first account has the permission to operate the target interface.

[0043] According to the above embodiment, the above step S104 includes: obtaining the predefined attribute information of the target interface to determine the target account information corresponding to the application party in the attribute information; matching the account information with the target account information; if the account information matches the target account information, it is determined that the first account has the permission to apply for the operation of the target interface; otherwise, it is determined that the first account does not have the permission to apply for the operation of the target interface.

[0044] For example, the API interface is bound with a department or a team of a company in advance to set the application permission or the approval permission for the API interface. This is a good solution compared to the existing interface management platform which lacks the permission system for the use limitation of the API interface.

[0045] In this embodiment, the account information of the first account is obtained, and the account information is matched with predefined attribute information based on the pre-defined binding between the target interface and the department. For example, taking the API interface approval management system as an example, applicant A submits an application to launch interface C on the API interface approval management system. The API interface approval management system reads the application department B from the attribute information pre-defined for interface C. Department B includes 3 applicants. If applicant A is one of the applicants in department B, then applicant A is confirmed to have the authority to apply for the launch of interface C; otherwise, applicant A does not have the authority to apply for the launch of interface C.

[0046] Step S106: If the first account has the permission to operate the target interface, generate a target application form based on the account information and the interface information corresponding to the target interface;

[0047] In specific implementation, step S106 includes: when it is determined that the first account has the permission to apply for operation of the target interface, obtaining the basic information and attribute information of the target interface; generating a target application form corresponding to the application request based on the account information, target operation type, basic information of the target interface and attribute information of the target interface.

[0048] In one example of this embodiment, taking an API interface approval management system as an example, creating an API interface in the API interface approval management system requires obtaining the API interface's attribute information and basic information. Once the applicant has application permissions, the attribute information of the interface reveals the approver of the target interface for the approval application operation. Then, a target application form is generated containing the applicant's account information, the target operation type, the basic information of the API interface, and the attribute information of the API interface. For example, Figure 2 This is a schematic diagram of an application interface provided in an embodiment of the present invention.

[0049] Step S108: Send the target application form to the second account, where the second account has the permission to approve the application through the target interface.

[0050] The interface management method provided by this invention verifies the account information corresponding to the first account carried in the application request to apply for operation of the target interface to determine whether the first account has the application permission. If the first account has the application permission, a target application form is generated for the first account and then submitted to the second account with the approval permission. This realizes that different accounts have different API interface management permissions and improves the security of interface management.

[0051] Optionally, the step S108 comprises: searching, from the attribute information of the target interface, a second account corresponding to an approval party having the right to approve the operation target interface of the application; and sending an approval request carrying the target application form to the second account, so that the second account responds to the approval request and approves the target application form. The approval party in the embodiment is obtained from the attribute information of the target interface; the second account will receive the approval request and the target application form after logging in the API interface approval management system, and then respond to the approval request.

[0052] Optionally, after sending the target application form to the second account, the method further comprises: receiving an approval opinion submitted by the second account, wherein the approval opinion is an approval result formed by the second account approving the target application form; and sending the approval opinion to the first account. In the embodiment, the second account forms the approval opinion based on the target application form after completing the approval operation and feeds back to the first account, for example, Figure 3 An application diagram of the approval interface is provided in the embodiment of the application.

[0053] Through the definition of the application approval attribute, the embodiment of the application classifies the API interface use scenarios more conveniently and comprehensively and intuitively, and reduces the security problem in use. The query part can better and more intuitively display the API interface bound by the individual, protects the use security of the API interface, and promotes the development of data security.

[0054] In an optional embodiment of the application, the method further comprises: receiving a query request submitted by a target account, wherein the target account is any one of the first account and the second account, and the query request is used to request to view at least one of the following: an application form historically applied by the target account, an application form historically approved by the target account, an application form currently to be approved by the target account, and an interface having the right to be operated by the target account; and responding to the query request.

[0055] The embodiment realizes the query function of the API interface. Taking the API interface approval management system as an example, the service party can quickly query which people are using the API interface through the API interface approval management system; the application party can query the interface historically applied by himself or the interface to be approved by himself through the API interface approval management system; or the approver can query the interface historically approved by himself or the interface to be approved by himself.

[0056] For example, an API for creating a query is eg: access type is get, access address is / get / selectApp, and the complete path is spliced as: http: / / www.baidu.com / get / selectApp, and curl-s-X GET 'http: / / www.baidu.com / get / selectApp' can be called.

[0057] Through the above implementation steps, the definition of the application approval attribute, the application of the API interface, the approval of the API interface, the API interface query function, the API interface is connected with the user's personal information, the use of the API interface needs to be approved by the user, which strictly limits the use of the API interface, and the user of the API interface can be quickly queried, which greatly improves the security of the use of the API interface, and further improves the data security.

[0058] The following examples further describe the embodiments of the application:

[0059] The API interface approval management system is the execution subject, including the following contents:

[0060] (1) Create API interface: API interface basic information includes basic path, access type, description information, and belongs to service party (attributes include service address, responsible person, and responsible person department), so as to provide various API interfaces on the API interface approval management system.

[0061] (2) Define API interface attribute information in the application approval management: application number is used to identify the approval number, application type is used to identify the operation type of the single, application name is used to identify the single name, application department is used to identify the initiator of the single, service name is used to identify the service category to which the API interface belongs, and application reason, approval person, approval opinion, approval state, etc., so as to provide various permissions such as approval, approval, query, etc. for various API on the API interface approval management system.

[0062] (3) API interface application online: the service party creates an application online form, selects the API interface, fills in the application reason, and submits the application.

[0063] (4) API interface application offline: the service party creates an application offline form, selects the published API interface, fills in the application reason, and submits the application.

[0064] (5) API interface application use: the application party selects the published API interface, creates an application use form, fills in the application reason, and submits the application.

[0065] (6) API interface application release: the application party selects the API interface that has been applied to use, creates a form of application release, fills in the application reason, and submits the application.

[0066] (7) Query my application: click my application in the application management to show all API interfaces bound to the person.

[0067] (8) Query my approval: click my approval in the application management to show all API interfaces bound to the person.

[0068] (9) Approval: select the API interface, select agree or disagree, add the approval opinion, and submit the approval.

[0069] The complete API interface approval management system provided by the above embodiments realizes the online and offline application and approval of the API interface, the use and release application and approval of the API interface, and provides a viewing function, binds the API interface with departments and personnel, so as to limit the operation process and the use range.

[0070] In a second aspect, based on the interface management method provided in the above various embodiments, based on the same inventive concept, in the present embodiment, an interface management device is further provided, which is used to realize the above embodiments and preferred embodiments, and the description has been made. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware is also possible and is contemplated.

[0071] Figure 4 is a structural block diagram of an interface management device provided according to an embodiment of the application, as shown in Figure 4 The device includes: a first receiving module 40, configured to receive an application request for applying an operation target interface submitted by a first account, wherein the application request carries at least account information corresponding to the first account; a verification module 42 connected to the first receiving module 40, configured to verify the account information to verify whether the first account has the permission to operate the target interface; a generation module 44 connected to the verification module 42, configured to generate a target application form based on the account information and interface information corresponding to the target interface when the first account has the permission to operate the target interface; and a first sending module 46 connected to the generation module 44, configured to send the target application form to a second account, wherein the second account has the permission to approve the application of the operation target interface.

[0072] Optionally, the apparatus further comprises: an obtaining module, configured to obtain interface information of the target interface before the first receiving module 40 receives the application request for applying for the operation target interface submitted by the first account, wherein the interface information comprises basic information for describing the target interface and attribute information for defining the target interface, and the attribute information at least comprises an applicant having the right to apply for the operation of the target interface, an approver having the right to approve the application for the operation of the target interface, an operation type included in the application for the operation, and an approval state; and a creating module, configured to create an application form for applying for the operation target interface according to the basic information and the attribute information.

[0073] Optionally, the verifying module 42 comprises: a first obtaining unit, configured to obtain the attribute information predefined for the target interface to determine target account information corresponding to the applicant in the attribute information; a matching unit, configured to match the account information with the target information; and a determining unit, configured to determine that the first account has the right to apply for the operation of the target interface when the account information matches the target account information, and otherwise, determine that the first account does not have the right to apply for the operation of the target interface.

[0074] Optionally, the application request at least further carries a target operation type of the application for the operation of the target interface, and the generating module 44 comprises: a second obtaining unit, configured to obtain the basic information and the attribute information of the target interface when it is determined that the first account has the right to apply for the operation of the target interface; and a generating unit, configured to generate a target application form corresponding to the application request according to the account information, the target operation type, the basic information of the target interface, and the attribute information of the target interface.

[0075] Optionally, the first sending module 46 comprises: a searching unit, configured to search, from the attribute information of the target interface, a second account corresponding to an approver having the right to approve the application for the operation of the target interface; and a sending unit, configured to send an approval request carrying the target application form to the second account, so that the second account responds to the approval request and approves the target application form.

[0076] Optionally, after the first sending module sends the target application form to the second account, the apparatus further comprises: a second receiving module, configured to receive an approval opinion submitted by the second account, wherein the approval opinion is an approval result formed by the second account approving the target application form; and a second sending module, configured to send the approval opinion to the first account.

[0077] Optionally, the apparatus further comprises: a third receiving module, configured to receive a query request submitted by a target account, wherein the target account is any one of the first account and the second account, and the query request is used to request to view at least one of the following: an application form historically applied for by the target account, an application form historically approved by the target account, an application form currently to be approved by the target account, and an interface having the right to be operated by the target account; and a responding module, configured to respond to the query request.

[0078] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0079] Thirdly, embodiments of the present invention provide a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the interface management method provided in the first aspect.

[0080] Figure 5 An internal structural diagram of a computer device in one embodiment is shown. Figure 5 As shown, the computer device includes a processor, memory, network interface, input device, and display screen connected via a system bus. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and may also store computer programs. When executed by the processor, these programs enable the processor to implement interface management methods. The internal memory may also store computer programs, which, when executed by the processor, enable the processor to perform interface management methods. The display screen can be an LCD screen or an e-ink screen. The input device can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the computer device's casing, or an external keyboard, touchpad, or mouse.

[0081] Those skilled in the art will understand that Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present invention and does not constitute a limitation on the computer device to which the present invention is applied. A specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0082] In one embodiment, the interface management device provided by the present invention can be implemented as a computer program, and the computer program can be implemented in the form of, for example, Figure 5 It runs on the computer device shown. The computer device's memory can store the various program modules that make up the translation device, for example, Figure 4 The diagram shows a first receiving module 40, a verification module 42, a generation module 44, and a first sending module 46. The computer program comprised of these modules causes the processor to execute the steps of the interface management methods of the various embodiments of the present invention described in this specification.

[0083] For example, Figure 5The computer device shown can be used as follows Figure 4 The first receiving module 40 in the interface management device shown receives an application request submitted by a first account for applying to operate the target interface. The application request carries at least the account information corresponding to the first API interface account. The computer device can verify the API interface account information through the verification module 42 to verify whether the first API interface account has the permission to operate the target API interface. The computer device can generate a target application form based on the API interface account information and the interface information corresponding to the target API interface when the first API interface account has the permission to operate the target API interface. The computer device can send the target API interface application form to a second account through the first sending module 46, wherein the second API interface account has the permission to approve applications to operate the target API interface.

[0084] It is understood that the explanations, examples, and beneficial effects of the computer device provided in the embodiments of the present invention can be referred to the corresponding parts of the first aspect, and will not be repeated here.

[0085] Fourthly, embodiments of the present invention provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the interface management method provided in the first aspect.

[0086] It is understood that the explanations, examples, and beneficial effects of the computer-readable storage medium provided in the embodiments of the present invention can be referred to the corresponding parts of the first aspect, and will not be repeated here.

[0087] It is understood that any references to memory, storage, database, or other media used in the embodiments provided by this invention may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0088] It has to be noted that, in the present document, relational terms are intended only to convey a possible relationship between elements or

[0089] The foregoing is considered as illustrative only of the principles of the application. Numerous modifications and changes will readily occur to those skilled in the art, which modifications and changes are to be understood as intended to be encompassed by the general scope of the application. Accordingly, the application is not to be limited to the above described or illustrated embodiments, but is intended to encompass all embodiments consistent with the principles of the application.

Claims

1. An interface management method, characterized in that, The method includes: Obtain the interface information of the target interface, wherein the interface information includes basic information describing the target interface and attribute information defining the target interface, and the attribute information includes at least the applicant with the permission to apply for operation of the target interface, the approver with the permission to approve the application to operate the target interface, the operation type included in the application operation, and the approval status. Create an application form for requesting operation of the target interface based on the basic information and the attribute information; Receive a request submitted by a first account for requesting to operate the target interface, wherein the request carries at least the account information corresponding to the first account; The account information is verified to determine whether the first account has permission to operate the target interface. If the first account has permission to operate the target interface, a target application form is generated based on the account information and the interface information corresponding to the target interface; The target application form is sent to a second account, which has the authority to approve the application for operation of the target interface.

2. The method according to claim 1, characterized in that, The step of verifying the account information to verify whether the first account has permission to operate the target interface includes: Obtain predefined attribute information for the target interface to determine the target account information corresponding to the applicant in the attribute information; Match the account information with the target account information; If the account information matches the target account information, it is determined that the first account has the permission to apply for operation of the target interface; otherwise, it is determined that the first account does not have the permission to apply for operation of the target interface.

3. The method according to claim 1, characterized in that, The application request also carries at least the target operation type for requesting to operate the target interface. If the first account has permission to operate the target interface, a target application form is generated based on the account information and the interface information corresponding to the target interface, including: When it is determined that the first account has the permission to apply for operation of the target interface, the basic information and attribute information of the target interface are obtained; Based on the account information, the target operation type, the basic information of the target interface, and the attribute information of the target interface, a target application form corresponding to the application request is generated.

4. The method according to claim 1, characterized in that, Sending the target application form to the second account includes: From the attribute information of the target interface, find the second account corresponding to the approver who has the authority to approve the application to operate the target interface; Send an approval request carrying the target application form to the second account, so that the second account responds to the approval request and approves the target application form.

5. The method according to claim 1, characterized in that, After sending the target application form to the second account, the method further includes: Receive approval comments submitted by the second account, wherein the approval comments are the approval results generated by the second account approving the target application form; The approval comments will be sent to the first account.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Receive a query request submitted by a target account, wherein the target account is either the first account or the second account, and the query request is used to request to view at least one of the following: application forms previously submitted by the target account, application forms previously approved by the target account, application forms currently pending approval by the target account, and interfaces that the target account has permission to access. Respond to the query request.

7. An interface management device, characterized in that, The device includes: The acquisition module is used to acquire interface information of the target interface. The interface information includes basic information describing the target interface and attribute information defining the target interface. The attribute information includes at least the applicant with the authority to apply for operation of the target interface, the approver with the authority to approve the application for operation of the target interface, the operation type included in the application, and the approval status. A creation module is used to create an application form for applying to operate the target interface based on the basic information and the attribute information; The first receiving module is configured to receive a request submitted by a first account for applying to operate the target interface, wherein the request carries at least the account information corresponding to the first account; The verification module is used to verify the account information to verify whether the first account has the permission to operate the target interface; The generation module is used to generate a target application form based on the account information and the interface information corresponding to the target interface when the first account has the permission to operate the target interface; The first sending module is used to send the target application form to the second account, wherein the second account has the authority to approve the application operation of the target interface.

8. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Citation Information

Patent Citations

  • Interface permission configuration method and device, equipment and storage medium

    CN112395568A