Application store configuration and access method, system, equipment and medium

Abstract

The invention provides an application store configuration and access method, system and device and a medium, and belongs to the technical field of computers. The method comprises the following steps: configuring an application access interface to access various application types and automatically adapt to different fields required to be filled; configuring authentication information required by third-party authentication according to requirements; constructing a user role hierarchical management system, dividing a permission set according to user roles, and providing a user role editing function; classified application information is displayed in an application store, a complete application process including an applicant, an approval state and expiration time is recorded, and the functions of condition query, batch approval and approval result configuration are provided; and generating a user authorization token based on the approval result, verifying token validity and permission matching during access, and recording audit information. By designing uniform and flexible application access interfaces and processes, a layered authority management system based on SaaS users is constructed, and the operation efficiency of application stores is effectively improved.

Description

Technical Field

[0001] The present invention belongs to the field of computer technology, and more specifically, relates to an application store configuration and access method, system, device, and medium. Background Art

[0002] With the acceleration of enterprise digital transformation and the popularization of the SaaS (Software as a Service) model, the importance of the application store as an important platform for application resource management and distribution has become increasingly prominent. However, in traditional application store technical solutions, there are still the following technical defects, which are difficult to meet the efficient, secure, and compliant requirements in complex scenarios: 1. Low application access efficiency, insufficient scalability and compatibility. When traditional application stores access multiple types of applications, they need to manually configure independent access interfaces and required fields for different applications, lacking a unified automated adaptation mechanism. For example, fields such as the name, code, and authentication method (such as OAuth, SAML) of each application need to be configured one by one, resulting in a long and error-prone access process. When the application type or authentication protocol is updated, the configuration needs to be adjusted repeatedly, severely restricting the scalability and compatibility of the application store and unable to meet the needs of rapid iteration and diverse application access.

[0003] 2. Coarse-grained user permission management, prominent security risks. Traditional permission models usually adopt a single role division (such as only distinguishing between administrators and ordinary users), and permission allocation is mostly based on coarse-grained menu or function point control, lacking fine-grained data permissions and dynamic role management. In the SaaS scenario, different user roles (such as financial auditors, market analysts) have significantly different functional and data access requirements for the same application, while traditional solutions are difficult to achieve flexible combination and hierarchical management of permissions. In addition, permission changes rely on manual operations, which are prone to security problems such as unauthorized access due to configuration errors.

[0004] 3. The application application and authorization processes are fragmented, lacking full-process control. The application approval process of traditional application stores relies on offline communication or scattered system modules, lacking a complete online process record and status tracking. For example, users need to submit applications through emails or forms, and approvers need to manually process a large number of applications, and cannot perform batch operations or configure approval results. At the same time, the authorization verification mechanism is single, only relying on static tokens or simple permission checks, without combining real-time auditing and dynamic permission matching, resulting in lagging access control and being difficult to handle scenarios such as permission changes or expiration, seriously affecting the user experience and system security. Summary of the Invention

[0005] Aiming at the above problems, the purpose of the present invention is to provide an application store configuration and access method, system, device, and medium. By designing a unified and flexible application access interface and process, and constructing a hierarchical permission management system based on SaaS users, the operation efficiency of the application store is effectively improved.

[0006] To achieve the above object, the present invention is realized through the following technical solutions: In a first aspect, an embodiment of the present application provides an application store configuration and access method, including: Configure an application access interface to access multiple application types and automatically adapt to different required fields; Configure the authentication information required for third-party authentication according to requirements; Build a hierarchical user role management system, divide permission sets according to user roles, and provide a user role editing function; Display classified application information in the application store, record the complete application process including the applicant, approval status, and expiration time, and provide conditional query, batch approval, and approval result configuration functions; Generate a user authorization token based on the approval result, verify the token validity and permission matching during access, and record audit information.

[0007] In an optional implementation manner, the configuring the application access interface to access multiple application types and automatically adapt to different required fields includes: Configure an application access interface, obtain application information through the application access interface, and access the application; When performing an application access operation, automatically identify the application type according to the application information, and adapt the required fields according to the application type fields; The application information includes: application name, encoding, type, clientId, clientSecret.

[0008] In an optional implementation manner, the configuring the authentication information required for third-party authentication according to requirements includes: When the application has a third-party authentication requirement, set the authorization type, token validity period, and third-party login callback address on the preset authentication page; Perform an authorization operation on the service and interface, and set the expiration time of the authorization.

[0009] In an optional implementation manner, the building a hierarchical user role management system, dividing permission sets according to user roles, and providing a user role editing function includes: By building a hierarchical user role management system, divide the roles of users in the SaaS system into administrators, ordinary users, and specific business roles; Set corresponding permission sets for users according to user roles; the permission sets include menu permissions, function permissions, and data permissions; Perform operations such as adding, editing, deleting, and batch authorizing user roles according to role management requirements; Group manage user roles, and classify user roles with the same business requirements into one user group.

[0010] In an optional implementation, the method of displaying categorized application information in the application store, recording application process information, and providing conditional query, batch approval, and approval result configuration functions includes: Generate an application display interface in the application store, and display application information under different categories through the application display interface; When a user initiates an application request, obtain the application request information sent by the user and record it in the application request list; the application request information includes: application name, applicant, applicant unit, application time, approver, approval time, expiration time, and approval status; Obtain the application query requirement in real time, and perform fuzzy query according to the corresponding application name and code to locate the required application and related information; Obtain the application request in real time, generate a details page, display the information of the applied application in the details page, start the approval process according to the information of the applied application, perform batch approval of the application, and generate an approval result.

[0011] In an optional implementation, the method of generating a user authorization token based on the approval result, verifying the token validity and permission matching during access, and recording audit information includes: After the approval result is approval passed, automatically generate the corresponding authorization token according to the user's role and permission information; When a user accesses an application, verify the validity and permission matching of the authorization token according to the expiration time and permission information of the authorization token; If the current time is before the expiration time of the authorization token, the authorization token is valid, and provide application resources for the user; If the current time is after the expiration time of the authorization token, or the permission information does not match, reject the user's access and return the corresponding error information to the user.

[0012] In an optional implementation, the method of generating a user authorization token based on the approval result, verifying the token validity and permission matching during access, and recording audit information further includes: Audit the user access information in real time, and generate and record the audit information; The audit information includes: application name, application code, visitor name, visitor IP, and access time.

[0013] In a second aspect, an application store configuration and access system provided by an embodiment of the present application includes: An application access module, configured to configure an application access interface to access multiple application types and automatically adapt to different required fields; An authentication configuration module for configuring authentication information required for third-party authentication according to requirements; A user role hierarchical management module for constructing a user role hierarchical management system, dividing permission sets according to user roles, and providing a user role editing function; An application application module for displaying categorized application information in an application store, recording a complete application process including the applicant, approval status, and expiration time, and providing conditional query, batch approval, and approval result configuration functions; An authorization access module for generating a user authorization token based on the approval result, verifying the token validity and permission matching during access, and recording audit information.

[0014] Thirdly, an embodiment of the present application further provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the steps of the application store configuration and access method described in any one of the above are implemented.

[0015] Fourthly, an embodiment of the present application further provides a storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the application store configuration and access method described in any one of the above are implemented.

[0016] From the above technical solutions, it can be seen that the present invention has the following advantages: In the application store configuration and access method provided by the present application, by constructing an automated application access interface, rapid adaptation and unified management of multiple types of applications are achieved, significantly enhancing the scalability and compatibility of the application store; based on a hierarchical role model, fine-grained permission configuration and dynamic management are realized, effectively meeting the differentiated access requirements in the SaaS scenario and strengthening security control; integrating a full-process electronic application approval and batch processing mechanism, combined with intelligent token verification and real-time audit tracking, not only optimizes the user experience, but also realizes full-life-cycle security and compliance management through permission matching verification and access behavior recording, forming a set of efficient, flexible, and controllable application store configuration and access solutions.

[0017] The present application supports the rapid access of multiple application types by automatically configuring the application access interface, and intelligently identifies the type and dynamically adapts the required fields based on the application information. This mechanism significantly reduces the workload and error rate of manual configuration, while enhancing the compatibility of the application store with heterogeneous applications. Administrators do not need to repeatedly develop adaptation logic for different applications, greatly shortening the new application online cycle and improving the platform's support ability for diverse application ecosystems.

[0018] This application constructs a user role hierarchical management system based on SaaS, divides permissions into three dimensions: menu, function, and data, and supports dynamic allocation of permission sets according to roles. Through the grouping association function, user roles with the same business requirements can be grouped into a unified user group to achieve batch permission management. Compared with the traditional permission model, this solution can precisely control the access scope of users to specific functions or data, avoid unauthorized operations, reduce the complexity of permission allocation, and effectively improve the overall security and compliance of the system.

[0019] This application integrates a full-process electronic approval mechanism in the application store, supporting conditional query, batch approval, and approval result configuration functions. Users can view the application status (such as in approval, approved, rejected) and expiration time in real time. Administrators can quickly process a large number of applications through batch operations, reducing the cumbersome steps of manual review one by one. In addition, the system automatically records the complete application process information (including applicant, approver, time node, etc.), forming a traceable approval chain, improving process transparency and audit capabilities, and reducing management costs.

[0020] This application optimizes the application application and authorization access process, simplifies the operation steps, improves the efficiency of users to obtain and use applications, enhances the user experience, and helps improve user satisfaction and loyalty to the application store.

[0021] This application generates a dynamic authorization token based on the approval result and verifies the token validity (including expiration time, permission matching) in real time when the user accesses. If the token is invalid or the permission does not match, the system automatically rejects the access and returns an error message to ensure that users can only access resources within their permission scope. Compared with static permission control, this solution can flexibly handle permission change scenarios (such as role adjustment, temporary authorization), and at the same time records access behaviors (including application name, visitor IP, time, etc.) through audit logs, providing data support for security event tracing.

[0022] This application adopts a modular design, and each functional module (such as application access, permission management, approval flow, access control) can be independently extended and cooperate with each other. For example, when adding a new authentication protocol or permission type, there is no need to reconstruct the entire system, only the corresponding module needs to be adjusted. In addition, automated processes (such as batch approval, audit record generation) reduce manual intervention, reduce the complexity of operation and maintenance, enable the system to more efficiently handle business growth and security challenges, and provide sustainable technical support for the long-term development of enterprises. Brief Description of the Drawings

[0023] To more clearly illustrate the technical solution of the present invention, the following will briefly introduce the accompanying drawings required for the description. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other accompanying drawings can be obtained based on these drawings.

[0024] Figure 1 It is a schematic flowchart of the application store configuration and access method provided by this application.

[0025] Figure 2 It is a schematic structural diagram of the application store configuration and access system provided by this application.

[0026] Figure 3 It is a schematic structural diagram of the electronic device provided by this application. Specific Embodiments

[0027] In the following, the specific steps of the application store configuration and access method will be described in detail, and various embodiments of the present disclosure will be described more comprehensively. The present disclosure can have various embodiments, and adjustments and changes can be made therein. However, it should be understood that there is no intention to limit the various embodiments of the present disclosure to the specific embodiments disclosed herein, but the present disclosure should be understood to cover all adjustments, equivalents, and / or alternative solutions falling within the spirit and scope of the various embodiments of the present disclosure.

[0028] To facilitate a clear description of the technical solution of the embodiments of this application, the following briefly introduces some terms and technologies involved in the embodiments of this application: SaaS (Software as a Service): Software as a Service, which is a model of providing software services through the Internet. In this model, users do not need to install software locally, but access application programs on cloud servers through a browser.

[0029] Application store: A platform for centralized management and distribution of various applications, where users can browse, apply for, install, and manage various applications.

[0030] Hierarchical permission division: According to the different roles, usage scenarios, and requirements of SaaS users, user permissions are divided into different levels to achieve refined permission management.

[0031] Authorized access process: A series of operation steps and verification processes for accessing application resources after a user applies for an application and obtains authorization.

[0032] In the following, the term "comprising" or "may comprise" which may be used in various embodiments of the present disclosure indicates the presence of the disclosed functions, operations or elements, and does not limit the addition of one or more functions, operations or elements. Further, as used in various embodiments of the present disclosure, the terms "comprising", "having" and their cognates are only intended to denote a specific feature, number, step, operation, element, component or combination of the foregoing items, and should not be construed as precluding the existence or addition of one or more other features, numbers, steps, operations, elements, components or combinations of the foregoing items first.

[0033] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0034] Please refer to Figure 1 The following is a flowchart of a method for configuring and accessing an application store in a specific embodiment. The method includes: S1: Configure an application access interface to access multiple application types and automatically adapt to different required fields.

[0035] In the specific implementation, a simple and clear operation interface is first configured. This application access interface can support the access of multiple application types during the application access process. When an application is accessed, the application information filled in by the user is obtained, including the application name, code, type, clientId, clientSecret, etc., to ensure the uniqueness and identifiability of each application in the system.

[0036] During the application access operation, different required fields are automatically adapted according to the application type. For example, some specific types of applications require additional configuration information.

[0037] Exemplarily, in the application access phase, multi-type application access is achieved by configuring a simple operation interface. This interface dynamically identifies the application type (such as Web applications, mobile applications, or API services) and automatically adjusts the display logic of required fields: for example, when accessing an application that needs to call a third-party service, the interface will additionally display the "service authorization scope" field; while for ordinary applications, only basic information (such as application name, encoding, clientId / clientSecret, etc.) needs to be filled in. To ensure the uniqueness of the application, the global uniqueness rule of the application encoding is verified, and the application unique identifier (UUID) is generated in the background. In addition, dynamic form technology is used to achieve field adaptation. For example, by presetting a rule engine to judge the configuration templates of different application types, the corresponding field forms are automatically loaded, thereby reducing manual intervention and lowering the configuration error rate.

[0038] S2: Configure the authentication information required for third-party authentication according to requirements.

[0039] In the specific implementation manner, for applications that require third-party authentication, a dedicated authentication page is used. On this page, information such as authorization type, token validity period, and third-party login callback address is set, and authorization operations can be performed on services and interfaces. At the same time, the expiration time of the authorization is set to achieve precise control of the application functions.

[0040] Exemplarily, for applications that require third-party authentication, an independent authentication configuration page is provided. Users can set the authorization type (such as the authorization code mode or client mode of OAuth 2.0), token validity period (accurate to the minute level), and callback address on this page. For example, when configuring WeChat login, the AppID and AppSecret of the WeChat open platform need to be entered, and the authorization scope (such as obtaining user basic information) is specified. The system completes service authorization by calling the authentication interface of the third-party platform and records the authorization status and expiration time. In addition, interface-level permission control is supported: specific API interfaces to be opened (such as "user information query interface" or "payment interface") are selected on the authorization page, and the system will generate the corresponding permission list and bind it to the token to ensure that the third-party application can only access the authorized interfaces.

[0041] S3: Build a hierarchical management system for user roles, divide permission sets according to user roles, and provide a user role editing function.

[0042] In the specific implementation manner, first, a complete user role management system is built. According to the roles and responsibilities of users in the SaaS-based system, users are divided into different levels, such as including administrators, ordinary users, specific business roles, etc.

[0043] Then, for each level, set corresponding permission sets for users, covering menu permissions, function permissions, data permissions, etc. For example, administrators have all operation permissions for all applications, while ordinary users can only access authorized applications and functions, and specific business roles are granted specific permissions according to their business needs.

[0044] At the same time, in the preset role management module, operations such as adding, editing, deleting, and batch authorization of roles are supported. At the same time, it also supports the management method based on role groups, grouping user roles with the same business needs into one group, realizing centralized authorization and management of users within the group, and greatly improving the efficiency of permission management.

[0045] For example, the user role management system is implemented through a hierarchical permission model. First, predefined role levels (such as super administrator → tenant administrator → department administrator → ordinary user) are defined, and each level is associated with a permission set. For example, a super administrator can manage applications of all tenants, while a tenant administrator can only manage applications within their own tenant. The permission set is configured through a "permission tree" structure, covering menu permissions (such as "application management menu visible"), function permissions (such as "delete application button operable"), and data permissions (such as "can only view applications created by this department"). The role group management function allows multiple roles (such as "financial approver" and "procurement approver") to be grouped into an "approval group", and by batch authorizing within the group (such as one-click granting of "approval process access permission"), the efficiency of permission allocation is significantly improved. At the same time, a role inheritance mechanism is supported, and sub-roles automatically inherit the basic permissions of the parent role.

[0046] S4: Display classified application information in the application store, record the complete application process including the applicant, approval status, and expiration time, and provide functions such as conditional query, batch approval, and approval result configuration.

[0047] In the specific implementation, first generate an application display interface in the application store, and display application information under different classifications through the application display interface, including content such as application name, code, category, link, etc.

[0048] When a user initiates an application request, obtain the application information sent by the user and record it in the application request list; the application information includes: application name, applicant, applicant unit, application time, approver, approval time, expiration time, and approval status.

[0049] At the same time, the conditional query function is supported. Users can perform fuzzy queries based on the application name and code to quickly locate the required applications. Specifically, obtain the application query requirements in real time, and perform fuzzy queries according to the corresponding application name and code to locate the required applications and related information.

[0050] In addition, the application requests are obtained in real time, a detail page is generated, the information of the applied application is displayed on the detail page, and the approval process is started according to the information of the applied application for batch approval of the application, and the approval result is generated. By way of example, the approval process provides two operation options of passing and rejecting, and the expiration time of the application can be flexibly set when the approval is passed. In addition, the batch approval and detail viewing functions are also supported. The approver can view the detailed information of the applied application on the detail page and then make an accurate approval operation.

[0051] By way of example, the application store interface uses classification labels (such as "office tools" and "data analysis") and a card layout to display application information. Users can quickly locate the target through fuzzy queries by name or code (such as entering "analysis" to retrieve all applications containing this keyword). When the user submits an application, the system automatically records metadata such as the applicant's unit and application time and binds it to the approval process. The approver can view the detailed description, permission requirements and historical approval records of the application on the detail page and select to pass (supporting custom expiration time, such as "authorized to use for 30 days") or reject (reason for rejection needs to be filled in). For batch applications (such as applying for 10 similar applications at the same time), the system provides a "batch pass" option and supports batch setting of expiration time according to a template. The approval result is synchronized to the application list in real time and the applicant is notified by message.

[0052] S5: Generate a user authorization token based on the approval result, verify the validity of the token and the permission matching during access, and record audit information.

[0053] In the specific implementation manner, when the application applied by the user passes the approval, a corresponding authorization token is automatically generated according to the user's role and permission information. Judging from the system's architecture and operation logic, when the user accesses the application, the validity of the authorization token will be strictly verified, including key information such as the expiration time of the token and whether the user's permissions match.

[0054] If the token is valid, the user can successfully access the application resources; if the token is invalid or the permissions are insufficient, the system will reject the access and prompt the user with the corresponding error information in a timely manner. Specifically, if the current time is before the expiration time of the authorization token, the authorization token is valid and the application resources are provided to the user; if the current time is after the expiration time of the authorization token, or the permission information does not match, the user access will be rejected and the corresponding error information will be returned to the user.

[0055] At the same time, this method also has the function of recording user access audit information. Specifically, the user access information is audited in real time, and the audit information is generated and recorded; the audit information includes: application name, application code, visitor name, visitor IP and access time.

[0056] Exemplarily, an authorization token in JWT format is generated based on the approval result, and the token embeds user role identification, permission list, and expiration timestamp. When a user accesses the application, the gateway service decrypts the token with the public key, verifies the validity of its signature and expiration time, and compares the user's current role permissions with the permission list in the token. For example, if a user's permissions are downgraded by an administrator (such as from "edit permission" to "read-only permission"), even if the token has not expired, the access request will still be rejected. The audit module records complete access logs, including the visitor's IP (for detecting abnormal logins), access time (accurate to milliseconds), and operation traces (such as "called the / userinfo interface"). The log data is stored in an independent audit database and supports export by application code or time range to meet the requirements of compliance reviews.

[0057] In this embodiment, a design and development method for a SaaS-based application store is disclosed, aiming to solve problems such as multi-application access management, fine-grained SaaS user permission division, and optimization of the application application and authorization access process. By constructing an application access module, rapid access and management of multiple applications are achieved; a hierarchical division mechanism based on SaaS users is adopted to ensure that different user roles obtain appropriate permissions; an efficient application application and authorization access process is designed to improve the convenience and security of users in obtaining and using applications. This method can effectively improve the operation efficiency of the application store, enhance the user experience, and has broad application prospects.

[0058] As Figure 2 shown, the following is an embodiment of an application store configuration and access system provided by the present disclosure. This system belongs to the same inventive concept as the application store configuration and access methods of the above embodiments. Details not described in detail in the embodiment of the application store configuration and access system can refer to the embodiments of the above application store configuration and access methods.

[0059] An application store configuration and access system includes: an application access module, an authentication configuration module, a user role hierarchical management module, an application application module, and an authorization access module.

[0060] The application access module is used to configure an application access interface to access multiple application types and automatically adapt to different required fields; The authentication configuration module is used to configure the authentication information required for third-party authentication according to requirements.

[0061] The user role hierarchical management module is used to construct a user role hierarchical management system, divide permission sets according to user roles, and provide a user role editing function.

[0062] An application application module is used to display classified application information in an application store, record a complete application process including the applicant, approval status, and expiration time, and provide functions such as conditional query, batch approval, and approval result configuration.

[0063] An authorization access module is used to generate a user authorization token based on the approval result, verify the token validity and permission matching during access, and record audit information.

[0064] The application store configuration and access system provided by this embodiment significantly improves the access efficiency and compatibility of the application store, the refinement and security of permission control, the transparency and efficiency of the approval process, the dynamics and security of access control through functions such as an automated application access interface, a hierarchical role permission management system, a full-process electronic approval mechanism, dynamic authorization token verification, and real-time audit records. At the same time, it optimizes the system scalability and operation and maintenance costs, providing comprehensive technical support for building an efficient, secure, and scalable digital service platform.

[0065] Figure 3 A schematic diagram of the hardware structure of an electronic device for implementing various embodiments of the present invention.

[0066] The application store configuration and access method provided by the embodiments of this application can be applied to an electronic device. Those skilled in the art can understand that the electronic device structure involved in the embodiments of the present invention does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements. In the embodiments of the present invention, the electronic device includes, but is not limited to, a laptop computer, a desktop computer, a workbench, a personal digital assistant, a server, a blade server, a mainframe computer, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as a personal digital processor, a cellular phone, a smart phone, a wearable device, 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 embodiments of this application described herein and / or required.

[0067] The electronic device may include a processor, an external memory interface, an internal memory, a universal serial bus (USB) interface, a charging management module, a power management module, a battery, a wireless communication module, an audio module, a speaker, a microphone, a sensor module, a key, a camera, a display screen, and a SIM card interface, etc.

[0068] The processor may include one or more processing units. For example, the processor may include a central processing unit (CPU), an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors.

[0069] Among them, the processor may be the nerve center and command center of the electronic device. The controller can generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching and executing instructions.

[0070] A memory may also be provided in the processor for storing instructions and data. In some embodiments, the memory in the processor is a cache memory. This memory can save the instructions or data that the processor has just used or recycled. If the processor needs to use the instruction or data again, it can directly call it from this memory. This avoids repeated accesses, reduces the waiting time of the processor, and thus improves the system efficiency.

[0071] The external memory interface can be used to connect an external memory card, such as a MicroSD card, to expand the storage capacity of the electronic device. The external memory card communicates with the processor through the external memory interface to implement the data storage function. For example, files such as music and videos are saved in the external memory card.

[0072] The internal memory can be used to store computer-executable program codes, and the computer-executable program codes include instructions. The processor executes various functional applications and data processing of the electronic device by running the instructions stored in the internal memory. The internal memory may include a program storage area and a data storage area. The internal memory may include a high-speed random access memory and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0073] The wireless communication function of the electronic device can be implemented through an antenna, a wireless communication module, a modem processor, a baseband processor, etc.

[0074] The wireless communication module can provide solutions for wireless communications applied to electronic devices, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite systems (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), etc.

[0075] The electronic device can implement audio functions through an audio module, speakers, receivers, microphones, headphone jacks, application processors, etc.

[0076] The electronic device can implement a shooting function through an ISP, a camera, a video codec, a GPU, a display screen, an application processor, etc.

[0077] The electronic device can implement a display function through a GPU, a display screen, an application processor, etc.

[0078] The GPU is a microprocessor for image processing, connecting the display screen and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor may include one or more GPUs that execute program instructions to generate or change display information.

[0079] The display screen is used to display images, videos, etc. The display screen includes a display panel.

[0080] The above-mentioned electronic device realizes the functions of the application store configuration and access method of the present application by constructing functional modules such as an automated application access interface, a hierarchical role permission management system, a full-process electronic approval mechanism, a dynamic authorization token verification, and a real-time audit record, achieving rapid adaptation and enhanced compatibility of application access, precision and security improvement of permission control, transparency and efficiency optimization of the approval process, dynamic and compliance guarantee of access control, and significant reduction of system scalability and operation and maintenance costs, ultimately achieving the beneficial effect of comprehensively improving the application store configuration and access capabilities and supporting the efficient and secure operation of enterprise digital services.

[0081] In the storage medium provided by the present application, there is a program product capable of realizing the application store configuration and access method.

[0082] The application store configuration and access method includes: Configuring an application access interface to access multiple application types and automatically adapt to different required fields; Configure the authentication information required for third-party authentication according to requirements; Build a hierarchical management system for user roles, divide the permission sets according to user roles, and provide a user role editing function; Display classified application information in the application store, record the complete application process including the applicant, approval status, and expiration time, and provide functions for conditional query, batch approval, and approval result configuration; Generate a user authorization token based on the approval result, verify the validity of the token and the permission matching during access, and record audit information. In some possible implementation manners, the application store configuration and access method of the present disclosure can be implemented in the form of a program product, which includes program code. When the program product runs on a terminal device, the program code is used to cause the terminal device to execute the steps according to various exemplary embodiments of the present disclosure described in the above "Exemplary Method" section of this specification.

[0083] The storage medium of the present disclosure can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples (non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable 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 above.

[0084] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present invention. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for configuring and accessing an application store, characterized in that, Include: Configure the application access interface to access multiple application types and automatically adapt to different required fields; Configure the authentication information required for third-party authentication according to requirements; Build a hierarchical management system for user roles, divide permission sets according to user roles, and provide a user role editing function; Display classified application information in the application store, record the complete application process including the applicant, approval status, and expiration time, and provide conditional query, batch approval, and approval result configuration functions; Generate a user authorization token based on the approval result, verify the token validity and permission matching during access, and record audit information.

2. The application store configuration and access method according to claim 1, wherein The configuration of the application access interface to access multiple application types and automatically adapt to different required fields includes: Configure the application access interface, obtain application information through the application access interface, and access the application; When performing an application access operation, automatically identify the application type according to the application information, and adapt the required fields according to the application type fields; The application information includes: application name, code, type, clientId, clientSecret.

3. The application store configuration and access method according to claim 1, characterized in that, The configuration of the authentication information required for third-party authentication according to requirements includes: When the application has a third-party authentication requirement, set the authorization type, token validity period, and third-party login callback address on the preset authentication page; Perform an authorization operation on the service and interface, and set the expiration time of the authorization.

4. The application store configuration and access method according to claim 1, characterized in that, The construction of the hierarchical management system for user roles, dividing permission sets according to user roles, and providing a user role editing function includes: By building a hierarchical management system for user roles, divide the roles of users in the SaaS system into administrators, ordinary users, and specific business roles; Set corresponding permission sets for users according to their user roles; the permission sets include menu permissions, function permissions, and data permissions; According to the role management requirements, perform operations such as adding, editing, deleting, and batch authorizing user roles; Group and manage user roles, and group user roles with the same business requirements into a user group.

5. The application store configuration and access method according to claim 2, characterized in that, The display of classified application information in the application store, recording application process information, and providing conditional query, batch approval, and approval result configuration functions includes: Generate an application display interface in the application store, and display application information under different classifications through the application display interface; When a user initiates an application request, obtain the application request information sent by the user and record it in the application request list; the application request information includes: application name, applicant, applicant unit, application time, approver, approval time, expiration time, and approval status; Obtain the application query requirements in real time, perform fuzzy queries according to the corresponding application name and code to locate the required application and related information; Obtain application requests in real time, generate a detailed page, display the information of the applied application on the detailed page, start the approval process according to the information of the applied application, perform batch approval of the application, and generate an approval result.

6. The application store configuration and access method according to claim 5, characterized in that The generation of a user authorization token based on the approval result, verifying the token validity and permission matching during access, and recording audit information includes: When the approval result is approval, automatically generate the corresponding authorization token according to the user's role and permission information; When a user accesses the application, verify the validity and permission matching of the authorization token based on the expiration time of the authorization token and the permission information; If the current time is before the expiration time of the authorization token, the authorization token is valid, and provide application resources to the user; If the current time is after the expiration time of the authorization token, or the permission information does not match, reject the user's access and return the corresponding error information to the user.

7. The application store configuration and access method according to claim 6, wherein The generation of the user authorization token based on the approval result, verifying the token validity and permission matching during access, and recording audit information further includes: Audit the user access information in real time, generate and record audit information; The audit information includes: application name, application code, visitor name, visitor IP, and access time.

8. An application store configuration and access system, characterized in that, The system adopts the application store configuration and access method described in any one of claims 1 to 7; The system includes: An application access module, used to configure an application access interface to access multiple application types and automatically adapt to different required fields; An authentication configuration module, used to configure the authentication information required for third-party authentication according to requirements; A user role hierarchical management module, used to build a user role hierarchical management system, divide the permission sets according to the user roles, and provide a user role editing function; An application application module, used to display classified application information in the application store, record the complete application process including the applicant, approval status, and expiration time, and provide functions such as conditional query, batch approval, and approval result configuration; An authorization access module, used to generate a user authorization token based on the approval result, verify the token validity and permission matching during access, and record audit information.

9. An electronic device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the application store configuration and access method described in any one of claims 1 to 7.

10. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the application store configuration and access method described in any one of claims 1 to 7.

Images