Software resource processing method and device based on Nexus server, equipment and medium

Abstract

The invention discloses a software resource processing method and device based on a Nexus server, equipment and a medium. The method comprises the following steps: acquiring a second resource access request from a unified authentication server; the second resource access request is generated after the unified authentication server successfully authenticates the first resource access request sent by the user side; each of the first resource access request and the second resource access request comprises a current account and a current software resource identifier; according to the current account and the current software resource identifier, determining whether the current software resource belongs to a resource which can be accessed by the current account; determining whether the current software resource has security vulnerabilities or not according to the current software resource identifier; and if the current software resource belongs to the resource which can be accessed by the current account and the current software resource does not have security vulnerabilities, feeding back resource data of the current software resource to the user side. According to the embodiment of the invention, the access process of software resources can be simplified; and the security of software resources is ensured.

Description

Technical Field

[0001] The present invention relates to the field of communication technology and can be applied to the field of financial technology, and in particular to a software resource processing method, device, equipment and medium based on a Nexus server. Background Art

[0002] With the development of computer technology, the demand for unified management of third-party dependency packages and self-developed products within each company is increasing. The current mainstream open source product management platform in the industry is Nexus (software warehouse), which manages third-party dependency packages and self-developed products within the bank through open source Nexus. How to use open source Nexus in the field of financial technology to control all software products in the warehouse is a problem that needs to be solved. Summary of the invention

[0003] The present invention provides a software resource processing method, device, equipment and medium based on a Nexus server to solve the problem of how to use open source Nexus in the field of financial technology to manage and control all software products in a warehouse.

[0004] According to one aspect of the present invention, a method for processing software resources based on a Nexus server is provided, comprising:

[0005] Obtaining a second resource access request from the unified authentication server; wherein the second resource access request is generated after the unified authentication server successfully authenticates the first resource access request sent by the user terminal; and both the first resource access request and the second resource access request include a current account and a current software resource identifier;

[0006] Determining whether the current software resource is a resource accessible to the current account according to the current account and the current software resource identifier;

[0007] Determining whether the current software resource has a security vulnerability according to the current software resource identifier;

[0008] If the current software resource is a resource accessible to the current account and the current software resource does not have a security vulnerability, resource data of the current software resource is fed back to the user terminal.

[0009] According to another aspect of the present invention, there is provided a software resource processing device based on a Nexus server, comprising:

[0010] A request acquisition module, configured to acquire a second resource access request from a unified authentication server, wherein the second resource access request is generated after the unified authentication server successfully authenticates the first resource access request sent by the user terminal; the first resource access request and the second resource access request both include a current account and a current software resource identifier;

[0011] An account authority determination module, used to determine whether the current software resource is a resource accessible to the current account according to the current account and the current software resource identifier;

[0012] A resource vulnerability checking module, used to determine whether the current software resource has a security vulnerability according to the current software resource identifier;

[0013] The resource feedback module is used to feedback resource data of the current software resource to the user terminal if the current software resource is a resource accessible to the current account and the current software resource does not have a security vulnerability.

[0014] According to another aspect of the present invention, a computer program product is provided, including a computer program, wherein when the computer program is executed by a processor, the method for processing software resources based on a Nexus server according to any embodiment of the present invention is implemented.

[0015] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0016] At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the software resource processing method based on the Nexus server described in any embodiment of the present invention.

[0017] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the software resource processing method based on the Nexus server described in any embodiment of the present invention when executed.

[0018] According to another aspect of the present invention, a computer program product is provided, comprising a computer program / instruction, wherein when the computer program / instruction is executed by a processor, the method for processing software resources based on a Nexus server as described in any embodiment of the present invention is implemented.

[0019] The embodiment of the present invention performs user authority authentication through a unified authentication server. The second resource access request is generated after the unified authentication server successfully authenticates the first resource access request sent by the user terminal. The login authentication of the Nexus server is unified with the user authority authentication within the enterprise. The user only needs to log in once to securely access the Nexus server within the enterprise, without having to repeatedly enter the user name and password when accessing the Nexus server, thereby improving work efficiency and reducing login barriers caused by forgotten or incorrect password input. By feeding back the resource data of the current software resource to the user terminal when the current software resource belongs to a resource accessible to the current account and the current software resource does not have a security vulnerability, different software resource access permissions are set for different accounts, thereby ensuring the security of the software resources and ensuring that the software resources fed back to the user terminal do not have security vulnerabilities, effectively preventing the use of open source software resources or non-compliant resources with high-risk vulnerabilities within the enterprise from bringing potential security risks to the enterprise.

[0020] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0022] Figure 1 is a first flow chart of a software resource processing method based on a Nexus server provided in an embodiment of the present invention;

[0023] Figure 2 is a second flow chart of a software resource processing method based on a Nexus server provided in an embodiment of the present invention;

[0024] Figure 3 It is a structural schematic diagram of a software resource processing device based on a Nexus server provided in an embodiment of the present invention;

[0025] Figure 4 It is a schematic diagram of the structure of an electronic device implementing an embodiment of the present invention. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0027] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0028] Figure 1 This is the first flow chart of a method for processing software resources based on a Nexus server provided by an embodiment of the present invention. This embodiment is applicable to the case where software resources are processed based on a Nexus server through a bank unified authentication server. The method can be executed by a software resource processing device based on a Nexus server. The device can be implemented in the form of hardware and / or software. The device can be configured in an electronic device with corresponding data processing capabilities, such as a Nexus server. Figure 1 As shown, the method includes:

[0029] S110: Obtain a second resource access request from the unified authentication server.

[0030] The second resource access request is generated after the unified authentication server successfully authenticates the first resource access request sent by the user terminal; the first resource access request and the second resource access request both include the current account and the current software resource identifier.

[0031] Nexus is a powerful open source artifact repository manager that supports multiple repository types, provides comprehensive version control and access control functions, and can be integrated with other tools and systems. Whether it is a software development team, an internal enterprise repository, or an open source community, Nexus can be used to better manage and distribute software packages. As a centralized repository, Nexus provides functions such as storage, management, version control, access control, building, and deployment, which greatly simplifies the maintenance of internal repositories and access to external repositories. The unified authentication server is the user authentication system of the enterprise. It is a centralized identity authentication platform that integrates the authentication requirements of multiple business systems and implements a single sign-on function. Users only need to log in once to access all authorized business systems without repeatedly entering usernames and passwords, which improves work efficiency and reduces login barriers caused by forgotten or incorrect passwords.

[0032] Specifically, the user terminal initiates a first resource access request to the unified authentication server, and the unified authentication server performs permission authentication on the account in the first resource access request to determine whether the current account is a legitimate account within the enterprise. After the unified authentication server successfully authenticates the first resource access request sent by the user terminal, it generates a second resource access request, and accesses the software resources in the Nexus server through the second resource access request. Both the first resource access request and the second resource access request include the current account and the current software resource identifier, and the current software resource identifier is used to indicate the software resource that the current account wishes to access.

[0033] S120: Determine, according to the current account and the current software resource identifier, whether the current software resource is a resource accessible to the current account.

[0034] S130: Determine whether the current software resource has a security vulnerability according to the current software resource identifier.

[0035] Optionally, set levels for accounts, and set different software resource access permissions for different account levels. Determine whether the current software resource is a resource accessible to the current account based on the current account and the current software resource identifier. Determine whether the current software resource has a security vulnerability based on the current software resource identifier. Before each candidate software resource is uploaded to the Nexus server, multiple attack tests are required to determine whether the candidate software resource has a security vulnerability, and the historical attack records of each candidate software resource are queried in the Nexus server based on the software resource identifier.

[0036] S140: If the current software resource is a resource accessible to the current account and the current software resource does not have a security vulnerability, then the resource data of the current software resource is fed back to the user terminal.

[0037] If the current software resource belongs to the scope that the current account has access rights to, and the software resource has been confirmed to have no vulnerabilities through security checks, then the Nexus server sends the resource data of the software resource to the user end.

[0038] The embodiment of the present invention performs user authority authentication through a unified authentication server. The second resource access request is generated after the unified authentication server successfully authenticates the first resource access request sent by the user terminal. The login authentication of the Nexus server is unified with the user authority authentication within the enterprise. The user only needs to log in once to securely access the Nexus server within the enterprise, without having to repeatedly enter the user name and password when accessing the Nexus server, thereby improving work efficiency and reducing login barriers caused by forgotten or incorrect password input. By feeding back the resource data of the current software resource to the user terminal when the current software resource belongs to a resource accessible to the current account and the current software resource does not have a security vulnerability, different software resource access permissions are set for different accounts, thereby ensuring the security of the software resources and ensuring that the software resources fed back to the user terminal do not have security vulnerabilities, effectively preventing the use of open source software resources or non-compliant resources with high-risk vulnerabilities within the enterprise from bringing potential security risks to the enterprise.

[0039] In an optional implementation, the second resource access request is generated after the unified authentication server retrieves a successful authentication record of the current account from the cache data; or, the second resource access request is generated after the unified authentication server fails to retrieve a successful authentication record of the current account from the cache data and the current account and the first password carried in the first resource access request are successfully authenticated.

[0040] Specifically, if the unified authentication server finds the authentication success record of the current account from the cache data, a second resource access request is generated. If the unified authentication server does not find the authentication success record of the current account from the cache data, the unified authentication server generates a second resource access request after successfully authenticating the current account and the first password carried in the first resource access request. After the unified authentication server confirms that the current account authentication is successful, a second resource access request can be generated to access the Nexus server without repeatedly entering the username and password, which improves work efficiency and reduces login barriers caused by forgotten or incorrect password input.

[0041] Optionally, if the cache data includes an authentication failure record of the current account, the first resource access request is rejected; wherein the validity period of the authentication success record is a first time period, the validity period of the authentication failure record is a second time period, and the first time period is greater than the second time period.

[0042] Specifically, if the current account authentication is successful, the authentication success record of the current account is stored in the cache data, and the cache duration is the first duration. If the current account authentication fails, the authentication failure record of the current account is stored in the cache data, and the cache duration is the second duration. The first duration is greater than the second duration. If the cache data includes the authentication failure record of the current account when the first resource access request is initiated at the user end, the first resource access request is rejected. By storing the authentication result information in the cache data, when multiple batch software resource accesses are performed, the cached authentication results can be directly used for subsequent access requests without the need to perform a complete authentication process each time, thereby speeding up resource access speed and optimizing overall system performance. It can significantly improve access efficiency, reduce the load pressure on the unified authentication server, and reduce network overhead and delays caused by repeated authentication.

[0043] Figure 2 1 is a second flow chart of a method for processing software resources based on a Nexus server provided by an embodiment of the present invention. This embodiment is optimized and improved on the basis of the above embodiment. Figure 2 As shown, the method includes:

[0044] S210: Obtain a second resource access request from the unified authentication server.

[0045] The second resource access request is generated after the unified authentication server successfully authenticates the first resource access request sent by the user terminal; the first resource access request and the second resource access request both include the current account and the current software resource identifier.

[0046] S220. Query the current account level to which the current account belongs according to the current account.

[0047] S230: Query the associated current dynamic authorization data according to the current account level and the current software resource identifier.

[0048] Add fine-grained access control to the access account of the Nexus server, set the account level to which each account belongs, and different account levels correspond to different software resource access rights to control the access to software resources at different account levels. Software resource identification is used to distinguish different software resources. The access rights and access times of each software resource are set for each account level through the software resource identification. Software resources can be dynamically authorized, including dynamically adjusting the number of times software resources can be accessed. Through dynamic authorization of software resources, changes in business needs can be responded to in real time, and the access rights of accounts at each account level to software resources can be flexibly adjusted. The flexibility and response speed of business operations are improved. Security is enhanced, and the risk of unauthorized access and data leakage is reduced through refined permission management. Dynamic authorization helps optimize resource allocation, avoid unnecessary resource waste, and improve overall operational efficiency.

[0049] The current account level to which the current account belongs is queried according to the current account, and the current dynamic authorization data associated with the current account level and the current software resource identifier is queried, wherein the current dynamic authorization data includes the number of access times and historical access records.

[0050] S240: Determine whether the current software resource is a resource accessible to the current account according to the number of access times and the historical access record.

[0051] Based on the access rights, access counts and historical access records of the software resource corresponding to the current software resource identifier of the current account at the account level of the current account, determine whether the current account has access rights to the current software resource and whether the historical access counts have reached the accessible counts of the current software resource, thereby determining whether the current software resource is a resource accessible to the current account. If the current account has access rights to the current software resource and the historical access counts of the current account to the current software resource are less than the accessible counts of the current software resource, then the current software resource is a resource accessible to the current account.

[0052] S250: Determine whether the current software resource has a security vulnerability according to the current software resource identifier.

[0053] Before uploading each candidate software resource to the Nexus server, multiple attack tests are required to determine whether the candidate software resource has security vulnerabilities. Through the bank's internal interface, the historical attack records of the software resource are queried based on the software resource identifier.

[0054] Optionally, determining whether the current software resource has a security vulnerability based on the current software resource identifier includes: determining whether the current software resource has a security vulnerability based on the current software resource identifier and historical attack records of each candidate software resource. Specifically, determining the historical attack record of the current software resource from the historical attack records of each candidate software resource based on the current software resource identifier. If there is no record of successful attack in the historical attack record of the current software resource, then the current software resource does not have a security vulnerability.

[0055] S260: If the current software resource is a resource accessible to the current account and the current software resource does not have a security vulnerability, then the resource data of the current software resource is fed back to the user terminal.

[0056] In an optional implementation, it also includes: generating and updating a resource processing record according to the IP address of the user terminal, the current account, the request time of the second resource access request, and the current software resource identifier. The resource processing record of the second resource access request is recorded in the database or log of the Nexus server, including the IP address of the user terminal, the current account, the request time of the second resource access request, the requested software resource identifier, the software resource name and version number, etc., to provide a powerful audit tracking capability for the system administrator, ensure the traceability of the software resource access process, and protect the security of software resources.

[0057] The embodiment of the present invention performs user authority authentication through a unified authentication server. The second resource access request is generated after the unified authentication server successfully authenticates the first resource access request sent by the user terminal. The login authentication of the Nexus server is unified with the user authority authentication within the enterprise. The user only needs to log in once to securely access the Nexus server within the enterprise, and there is no need to repeatedly enter the user name and password when accessing the Nexus server, which improves work efficiency and reduces login barriers caused by forgotten or incorrect password input. Through dynamic authorization of software resources, it is possible to respond to changes in business needs in real time and flexibly adjust the access rights of accounts at various account levels to software resources. The flexibility and response speed of business operations are improved. Security is enhanced, and the risk of unauthorized access and data leakage is reduced through refined authority management. Dynamic authorization helps to optimize resource allocation, avoid unnecessary waste of resources, and improve overall operational efficiency. It ensures that the software resources fed back to the user terminal do not have security vulnerabilities, and effectively prevents the use of open source software resources or non-compliant resources with high-risk vulnerabilities within the enterprise from bringing potential security risks to the enterprise.

[0058] Figure 3 FIG. 1 is a schematic diagram of a software resource processing device based on a Nexus server provided by an embodiment of the present invention. Figure 3 As shown, the device comprises:

[0059] The request acquisition module 310 is used to acquire a second resource access request from the unified authentication server, wherein the second resource access request is generated after the unified authentication server successfully authenticates the first resource access request sent by the user terminal; the first resource access request and the second resource access request both include a current account and a current software resource identifier;

[0060] An account authority determination module 320 is used to determine whether the current software resource is a resource accessible to the current account according to the current account and the current software resource identifier;

[0061] A resource vulnerability checking module 330, configured to determine whether the current software resource has a security vulnerability according to the current software resource identifier;

[0062] The resource feedback module 340 is used to feedback resource data of the current software resource to the user terminal if the current software resource is a resource accessible to the current account and the current software resource does not have a security vulnerability.

[0063] The Nexus server-based software resource processing device provided in the embodiment of the present invention can execute the Nexus server-based software resource processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0064] Optionally, the resource vulnerability checking module is specifically used to determine whether the current software resource has a security vulnerability based on the current software resource identifier and historical attack records of each candidate software resource.

[0065] Optionally, the account authority judgment module is specifically used to query the current account level to which the current account belongs according to the current account; query the associated current dynamic authorization data according to the current account level and the current software resource identifier; wherein the current dynamic authorization data includes the number of access times and historical access records; and determine whether the current software resource belongs to the resources accessible to the current account according to the number of access times and the historical access records.

[0066] Optionally, it also includes a resource processing record module, which is used to generate and update a resource processing record according to the IP address of the user terminal, the current account, the request time of the second resource access request and the current software resource identifier.

[0067] Optionally, the second resource access request is generated after the unified authentication server queries the authentication success record of the current account from the cache data; or, the second resource access request is generated after the unified authentication server fails to query the authentication success record of the current account from the cache data, and the authentication of the current account and the first password carried in the first resource access request is successful.

[0068] Optionally, the request acquisition module is also used to: if the cache data includes an authentication failure record of the current account, reject the first resource access request; wherein the validity period of the authentication success record is a first time period, the validity period of the authentication failure record is a second time period, and the first time period is greater than the second time period.

[0069] The Nexus server-based software resource processing device further described can also execute the Nexus server-based software resource processing method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0070] According to an embodiment of the present invention, the present invention also provides an electronic device, a readable storage medium and a computer program product.

[0071] Figure 4 A schematic diagram of the structure of an electronic device 40 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0072] like Figure 4As shown, the electronic device 40 includes at least one processor 41, and a memory connected to the at least one processor 41, such as a read-only memory (ROM) 42, a random access memory (RAM) 43, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 41 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 42 or the computer program loaded from the storage unit 48 to the random access memory (RAM) 43. In the RAM 43, various programs and data required for the operation of the electronic device 40 can also be stored. The processor 41, the ROM 42, and the RAM 43 are connected to each other through a bus 44. An input / output (I / O) interface 45 is also connected to the bus 44.

[0073] A number of components in the electronic device 40 are connected to the I / O interface 45, including: an input unit 46, such as a keyboard, a mouse, etc.; an output unit 47, such as various types of displays, speakers, etc.; a storage unit 48, such as a disk, an optical disk, etc.; and a communication unit 49, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 49 allows the electronic device 40 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0074] The processor 41 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 41 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 41 executes the various methods and processes described above, such as the software resource processing method based on the Nexus server.

[0075] In some embodiments, the software resource processing method based on the Nexus server can be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 48. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 40 via the ROM 42 and / or the communication unit 49. When the computer program is loaded into the RAM 43 and executed by the processor 41, one or more steps of the software resource processing method based on the Nexus server described above can be performed. Alternatively, in other embodiments, the processor 41 can be configured to execute the software resource processing method based on the Nexus server in any other appropriate manner (for example, by means of firmware).

[0076] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0077] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0078] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0079] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0080] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0081] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0082] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0083] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A software resource processing method based on Nexus server, characterized in that: Executed by the Nexus server, the method includes: Obtaining a second resource access request from the unified authentication server; wherein the second resource access request is generated after the unified authentication server successfully authenticates the first resource access request sent by the user terminal; and both the first resource access request and the second resource access request include a current account and a current software resource identifier; Determining whether the current software resource is a resource accessible to the current account according to the current account and the current software resource identifier; Determining whether the current software resource has a security vulnerability according to the current software resource identifier; If the current software resource is a resource accessible to the current account and the current software resource does not have a security vulnerability, resource data of the current software resource is fed back to the user terminal.

2. The method according to claim 1, characterized in that The determining, according to the current software resource identifier, whether the current software resource has a security vulnerability includes: According to the current software resource identifier and the historical attack records of each candidate software resource, it is determined whether the current software resource has a security vulnerability.

3. The method according to claim 1, characterized in that The determining, according to the current account and the current software resource identifier, whether the current software resource belongs to a resource accessible to the current account includes: Querying the current account level to which the current account belongs according to the current account; Querying the associated current dynamic authorization data according to the current account level and the current software resource identifier; wherein the current dynamic authorization data includes the number of access times and historical access records; According to the accessible times and the historical access records, it is determined whether the current software resource belongs to the resources accessible to the current account.

4. The method according to claim 1, characterized in that: Also includes: A resource processing record is generated and updated according to the IP address of the user terminal, the current account, the request time of the second resource access request and the current software resource identifier.

5. The method according to claim 1, characterized in that The second resource access request is generated after the unified authentication server queries the authentication success record of the current account from the cache data; or, The second resource access request is generated after the unified authentication server fails to find a successful authentication record of the current account from the cache data and the current account and the first password carried in the first resource access request are successfully authenticated.

6. The method according to claim 5, characterized in that If the cache data includes an authentication failure record of the current account, the first resource access request is rejected; wherein the validity period of the authentication success record is a first time period, the validity period of the authentication failure record is a second time period, and the first time period is greater than the second time period.

7. A software resource processing device based on Nexus server, characterized in that: The device comprises: A request acquisition module, configured to acquire a second resource access request from a unified authentication server, wherein the second resource access request is generated after the unified authentication server successfully authenticates the first resource access request sent by the user terminal; the first resource access request and the second resource access request both include a current account and a current software resource identifier; An account authority determination module, used to determine whether the current software resource is a resource accessible to the current account according to the current account and the current software resource identifier; A resource vulnerability checking module, used to determine whether the current software resource has a security vulnerability according to the current software resource identifier; The resource feedback module is used to feedback resource data of the current software resource to the user terminal if the current software resource is a resource accessible to the current account and the current software resource does not have a security vulnerability.

8. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively coupled to the at least one processor; The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the software resource processing method based on the Nexus server described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the software resource processing method based on a Nexus server according to any one of claims 1 to 6 when executed.

10. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the computer program implements the software resource processing method based on the Nexus server according to any one of claims 1 to 6.

Images