WO2025081795A1 - Cloud platform access method and apparatus, electronic device, and storage medium - Google Patents

Abstract

A cloud platform access method and apparatus, an electronic device, and a storage medium, belonging to the technical field of cloud platforms. The cloud platform access method comprises: acquiring an access request of a user for a cloud platform, wherein the access request comprises a target access address; acquiring from a cache an access permission of the user, wherein the access permission comprises a button permission and an interface permission; and when it is determined that access addresses corresponding to the access permission comprise the target access address, allowing the user to access a micro-service corresponding to the target access address.

Description

Cloud platform access method, device, electronic device and storage medium

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is based on the Chinese patent application with application number: 202311363639.1 and application date of October 19, 2023, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby introduced into this application as a reference.

Technical Field

The present application relates to the technical field of cloud platforms, and in particular to a cloud platform access method, device, electronic device and storage medium.

Background Art

By configuring different access rights for different users of the cloud platform, it is possible to control different users' access to different microservices in the cloud platform. In the related art, the access rights configured for users are at the menu level and button level, which cannot guarantee the security of interface functions. In addition, the user's access rights need to be authenticated by each microservice, which increases the resource consumption of microservices and reduces the efficiency of microservice development.

Summary of the invention

The present application provides a cloud platform access method, device, electronic device and storage medium to improve the functional security of cloud platform interfaces, reduce resource consumption of microservices, and improve the development efficiency of microservices.

In a first aspect, an embodiment of the present application provides a cloud platform access method, including:

Obtaining a user's access request to the cloud platform, wherein the access request includes a target access address;

Obtaining the user's access rights from the cache, the access rights including button rights and interface rights;

When it is determined that the access address corresponding to the access permission includes the target access address, the user is allowed to access the microservice corresponding to the target access address.

In the above technical solution, the access rights configured for users are at the minimum granularity interface level to ensure the security of interface functions, realize the security management of cloud platform interfaces, and perform unified authentication and verification of user access rights, thereby reducing the resource consumption of microservices. Microservices only need to focus on the development of their own business functions, thereby improving the development efficiency of microservices.

According to one embodiment of the present application, the method further includes:

When it is determined that the user has successfully logged into the cloud platform, the user's access rights are obtained through the basic system management service and saved in the cache.

Obtain the user's access rights through the basic system management service and save them in the cache so that the business gateway service can access them in the future. After obtaining the user's access request, the user's access rights are directly obtained from the cache for authentication verification, which effectively improves the authentication efficiency of the business gateway service and thus improves the user's access efficiency.

According to an embodiment of the present application, obtaining the user's access rights through the basic system management service and saving the access rights to the cache includes:

Obtaining the user's permission list from a database through the basic system management service, the permission list including directory permissions, menu permissions, button permissions and interface permissions;

The button permissions and interface permissions in the permission list are saved in the cache through the basic system management service.

By dividing permission types into detailed categories, permission management and control are easier.

According to one embodiment of the present application, the method further includes:

The user's permission list is returned to the user through the basic system management service.

According to one embodiment of the present application, the method further includes:

Obtaining a login request from the user for the cloud platform, wherein the login request includes login information;

The login information is verified through the basic system management service, and if the verification passes, it is determined that the user has successfully logged into the cloud platform.

According to one embodiment of the present application, the method further includes:

When it is determined that the user login is invalid, the access rights of the user in the cache are cleared through the basic system management service.

According to one embodiment of the present application, the method further includes:

Obtaining permission configuration information of the user, wherein the permission configuration information includes a role configured for the user and a permission list configured for the role;

The user's permission configuration information can be saved in the database through the basic system management service.

By providing basic management functions as independent services, other microservices only need to focus on their own business function development, thereby improving development efficiency and the timeliness of function release.

According to an embodiment of the present application, obtaining the access rights of the user from the cache includes:

Retrieving the user's access rights from the cache through the business gateway service;

The allowing the user to access the microservice corresponding to the target access address when it is determined that the access address corresponding to the access permission has the target access address includes:

The business gateway service determines whether the access address corresponding to the access permission contains the target access address, and if it is determined that the access address corresponding to the access permission contains the target access address, the user is allowed to access the microservice corresponding to the target access address.

The business gateway service obtains the user's access rights from the cache for authentication and verification, effectively improving the business gateway The authentication efficiency of the service is improved, thereby improving the access efficiency of users.

In a second aspect, an embodiment of the present application proposes a cloud platform access device, including:

A first acquisition module is used to acquire a user's access request to the cloud platform, wherein the access request includes a target access address;

A second acquisition module is used to acquire the user's access rights from the cache, where the access rights include button rights and interface rights;

A determination module is used to determine whether the access address corresponding to the access permission contains the target access address, and if it is determined that the access address corresponding to the access permission contains the target access address, allow the user to access the microservice corresponding to the target access address.

In the above technical solution, the access rights configured for users are at the minimum granularity interface level to ensure the security of interface functions, realize the security management of cloud platform interfaces, and perform unified authentication and verification of user access rights, thereby reducing the resource consumption of microservices. Microservices only need to focus on the development of their own business functions, thereby improving the development efficiency of microservices.

In a third aspect, an embodiment of the present application proposes an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the cloud platform access method as described in the first aspect is implemented.

In the above technical solution, the access rights configured for users are at the minimum granularity interface level to ensure the security of interface functions, realize the security management of cloud platform interfaces, and perform unified authentication and verification of user access rights, thereby reducing the resource consumption of microservices. Microservices only need to focus on the development of their own business functions, thereby improving the development efficiency of microservices.

In a fourth aspect, an embodiment of the present application proposes a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the cloud platform access method described in the first aspect is implemented.

In the above technical solution, the access rights configured for users are at the minimum granularity interface level to ensure the security of interface functions, realize the security management of cloud platform interfaces, and perform unified authentication and verification of user access rights, thereby reducing the resource consumption of microservices. Microservices only need to focus on the development of their own business functions, thereby improving the development efficiency of microservices.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

FIG1 is a flow chart of a cloud platform access method provided in some embodiments of the present application;

FIG2 is a schematic diagram of a cloud platform architecture in a cloud platform access method provided in some embodiments of the present application;

FIG. 3 is a diagram of the basic system management data model relationship in the cloud platform access method provided in some embodiments of the present application picture;

FIG4 is a schematic diagram of the structure of a cloud platform access device provided in some embodiments of the present application;

FIG5 is a schematic diagram of the structure of an electronic device provided in some embodiments of the present application.

DETAILED DESCRIPTION

The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.

The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and/or" in the specification and claims represents at least one of the connected objects, and the character "/" generally indicates that the objects associated with each other are in an "or" relationship.

In the era of cloud computing, a large number of resources are managed uniformly through cloud platforms, and microservices are provided to the outside world through interfaces. To facilitate management, different access rights are configured for different users of the cloud platform, and different users can be controlled to access different microservices in the cloud platform.

In the related art, the access rights configured for users are at the menu level and button level, and the cloud platform interfaces are not securely managed. When a user obtains the address of an interface, even if the user does not have access rights to the interface, the user can access the microservice corresponding to the interface based on the address of the interface, resulting in the inability to ensure the functional security of the interface. In addition, when a user accesses a microservice corresponding to an interface, the microservice is required to authenticate and verify the user's access rights by itself to determine whether the user is allowed to access the microservice. This authentication method results in a large resource consumption of microservices, and microservices not only need to focus on the development of their own business functions, but also need to authenticate the user's access rights, reducing the development efficiency of microservices.

In order to solve the above problems, this application proposes a cloud platform access method, which configures the minimum granularity interface level access rights for users. Even if the user obtains the address of the interface, the user cannot access the microservice corresponding to the interface if the user does not have the access rights to the interface, thereby ensuring the functional security of the interface and realizing the security management and control of the cloud platform interface. In addition, the user's access rights are uniformly authenticated and verified, and each microservice does not need to perform authentication processing, which reduces the resource consumption of microservices, and microservices only need to focus on the development of their own business functions, improving the development efficiency of microservices.

The following describes the cloud platform access method, device, electronic device and storage medium of the embodiments of the present application with reference to the accompanying drawings.

FIG1 is a flow chart of a cloud platform access method according to an embodiment of the present application.

As shown in FIG. 1 , the cloud platform access method provided in the embodiment of the present application includes steps 110 to 130 .

Step 110: Obtain the user's access request to the cloud platform, where the access request includes a target access address.

The cloud platform has a front end and a back end. The front end of the cloud platform can be a browser end or a web page end, as shown in Figure 2, and the front end of the cloud platform can be provided with a business management system. The back end of the cloud platform can provide various resources, as shown in Figure 2, and the back end of the cloud platform is provided with a cloud platform microservice cluster, which can provide business gateway services and various internal microservices.

Users can interact with the front end of the cloud platform. Users can perform business operations on the front end, and the front end can respond to the user's operations, determine the microservice corresponding to the business operated by the user, and generate an access request for the microservice. The front end sends the access request to the back end, and the business gateway service of the back end first obtains the access request in order to perform unified authentication and verification of the user's access rights.

The access request includes a target access address, which is the access address of the microservice that the user wants to access. The access address can be a URL (uniform resource locator).

In some embodiments, the access request may further include a user identifier. The user identifier may be used to represent the identity information of the user, for example, the user identifier may be a user account. Through the user identifier, the access request may be matched with the user.

It should be noted that the business gateway service can simultaneously obtain access requests from multiple users for the same microservice, and can also simultaneously obtain access requests from multiple users for different microservices.

Step 120: Obtain the user's access rights from the cache, where the access rights include button rights and interface rights.

The user's access rights are pre-saved in the cache. After obtaining the user's access rights, the user's access rights are directly obtained from the cache for authentication verification.

According to some embodiments of the present application, obtaining the user's access rights from the cache in step 120 includes:

The user's access permissions are retrieved from the cache through the business gateway service.

After obtaining the user's access request, the business gateway service can call the user's access rights in the cache. The user's access rights in the cache include button rights and interface rights, that is, the user's access rights are used to indicate the button addresses and interface addresses that the user is allowed to access, and the button addresses and interface addresses are the user's access addresses.

It should be noted that the interfaces corresponding to the backend microservices are displayed on the front end in the form of buttons and interfaces. By configuring the user's access rights as button permissions and interface permissions, the configuration of the minimum granularity interface level permissions is achieved.

In some embodiments, the user identifier and access rights can be stored in a cache accordingly. After obtaining an access request, the business gateway service obtains the access rights corresponding to the user identifier from the cache based on the user identifier in the access request. The access rights corresponding to the user identifier are the user's access rights.

Step 130: When it is determined that the access address corresponding to the access permission has the target access address, the user is allowed to access the microservice corresponding to the target access address.

The access address corresponding to the access permission is the button address and interface address that the user is allowed to access. By comparing the access address corresponding to the access permission with the target access address, it can be determined whether the user is allowed to access the target access address. The corresponding microservice is accessed.

According to some embodiments of the present application, in step 130, when it is determined that the access address corresponding to the access permission has the target access address, allowing the user to access the microservice corresponding to the target access address includes:

The business gateway service is used to determine whether the access address corresponding to the access permission has the target access address, and if it is determined that the access address corresponding to the access permission has the target access address, the user is allowed to access the microservice corresponding to the target access address.

The business gateway service detects whether the access address corresponding to the user's access rights contains the target access address. If so, it indicates that the user has access rights to the target access address, and the user is allowed to access the microservice corresponding to the target access address. If not, it indicates that the user does not have access rights to the target access address, and the user is not allowed to access the microservice corresponding to the target access address.

When the user is allowed to access the microservice corresponding to the target access address, the business gateway service forwards the user's access request to the microservice corresponding to the target access address, so that the user can access the microservice corresponding to the target access address.

The embodiment of the present application configures the minimum granularity interface level permissions to the user, ensures the functional security of the cloud platform interface, and allows the cloud platform interface to be provided to the front-end business management system under security control. In addition, the user's access rights are uniformly authenticated and verified through the business gateway service, without the need for each microservice to authenticate the user's access rights, which reduces the microservice security and access control control, reduces the resource consumption of microservices, and microservices only need to focus on their own business function development, improve the development efficiency of microservices, and improve the timeliness of function release.

According to some embodiments of the present application, the cloud platform access method further includes:

When it is determined that the user has successfully logged in to the cloud platform, the user's access rights are obtained through the basic system management service and saved in the cache.

The user's access rights are pre-configured and stored. Before the user performs business operations on the front end, the user needs to log in to the business management system on the front end to log in to the cloud platform. When it is determined that the user has successfully logged in to the cloud platform, the basic system management service obtains the pre-stored user's access rights and stores the user's access rights in the cache. The cache can be a redis cache.

The basic system management service is a microservice in the backend of the cloud platform. This embodiment uses the basic system management service as an independent service to provide functions such as permission management, so that other microservices do not need to pay attention to permission management issues, thereby improving the development efficiency of other microservices. In addition, after obtaining the user's access rights, the basic system management service saves the user's access rights to the cache, so that the business gateway service can directly obtain the user's access rights from the cache for authentication verification after obtaining the user's access request, effectively improving the authentication efficiency of the business gateway service, and thus improving the user's access efficiency.

According to some embodiments of the present application, the step of obtaining the user's access rights through the basic system management service and saving them in the cache includes:

Obtain the user's permission list from the database through the basic system management service. The permission list includes directory permissions, menu permissions, button permissions, and interface permissions.

The button permissions and interface permissions in the permission list are saved to the cache through the basic system management service.

The user's permission list is pre-stored in the database. When it is determined that the user has successfully logged into the cloud platform, the basic system management service obtains the user's permission list from the database. The permission list includes multiple types of permissions configured for the user, namely directory permissions, menu permissions, button permissions, and interface permissions. Among them, directory permissions are configured as the routing path of the directory, menu permissions are configured as the routing path of the menu, button permissions are configured as the address of the button, and interface permissions are configured as the address of the interface.

After obtaining the user's permission list, the basic system management service saves the button permissions and interface permissions in the permission list into the cache. Among them, the button permissions and interface permissions are the user's access permissions.

This embodiment divides the permission types into detailed categories, making it easier to manage and control permissions.

In some embodiments, the database pre-stores the correspondence between users and roles, and the correspondence between roles and permission lists. The basic system management service can determine the user's role based on the correspondence between users and roles, and can determine the user's permission list based on the correspondence between roles and permission lists.

Among them, roles can be pre-configured for users, and different users can have different roles. For example, a user's role can be a common user or an administrator, and of course other roles can be defined, and each role has a corresponding permission list. Permission lists can be pre-configured for roles, and different roles can have different permission lists.

According to some embodiments of the present application, the cloud platform access method further includes:

The user's list of permissions is returned to the user through the underlying system management service.

After obtaining the user's permission list, the basic system management service can return the user's permission list to the business gateway service, and the business gateway service forwards the user's permission list to the front end. The front end can display the corresponding permissions to the user based on the user's permission list. For example, the front end displays the menus and buttons that the user has permissions to so that the user can operate the menus and buttons on the front end.

According to some embodiments of the present application, the cloud platform access method further includes:

Obtain the user's login request for the cloud platform, which includes login information;

The login information is verified through the basic system management service, and if the verification passes, it is determined that the user has successfully logged into the cloud platform.

The user can log in at the front end, for example, the user enters the user account and password at the front end. The front end responds to the user's login operation and generates a login request, which includes login information. The login information can be the information entered by the user at the front end, such as the user account and password. The front end sends the login request to the back end, and the business gateway service at the back end first obtains the login request. It should be noted that for the user's login request, the business gateway service does not need to authenticate the user's access rights, and directly forwards the login request to the basic system management service.

The basic system management service can verify the login information in the login request, and after the verification, return a token (such as a token) to the business gateway service. The business gateway forwards the token to the front end to indicate that the user has successfully logged into the cloud platform.

This embodiment uses the basic system management service as an independent service to provide login management and other functions, so that other microservices do not need to pay attention to login management issues, thereby improving the development efficiency of other microservices.

In some embodiments, the login request may also include a user identifier. The user's pre-configured permission list is stored in the database of the basic system management service in correspondence with the user identifier. After obtaining the login request and determining that the user has successfully logged into the cloud platform, the basic system management service may obtain the permission list corresponding to the user identifier from the database, i.e., the user's permission list, and store the user's access rights (i.e., button permissions and interface permissions in the permission list) in correspondence with the user identifier in the cache.

According to some embodiments of the present application, the cloud platform access method further includes:

When it is determined that the user login is invalid, the user's access permissions in the cache are cleared through the basic system management service.

The basic system management service can set a login interval. If the user has not logged in for a long time, that is, the user's login is determined to be invalid, and the basic system management service clears the user's access rights in the cache.

If the user login is determined to be invalid, if the user logs in to the cloud platform again, the user needs to log in again on the front end, such as re-entering the user account and password. After re-confirming that the user has successfully logged in to the cloud platform, the basic system management service re-acquires the user's access rights and saves them to the cache.

According to some embodiments of the present application, the cloud platform access method further includes:

Get the user's permission configuration information, which includes the role configured for the user and the permission list configured for the role;

The user's permission configuration information can be saved in the database through the basic system management service.

User roles can include common users and administrators. The permissions configured for roles such as administrators and common users can be different. For example, administrators have business function usage and management permissions, while common users only have business function usage permissions.

As shown in Figure 2, the front-end business management system may include functions such as user account management, role management, authority management, and operation record management. Among them, user account management is used to manage user account information, role management is used to manage user roles and other information, authority management is used to manage information such as permissions corresponding to roles, and operation record management is used to record user access to microservices.

The user account management, role management, permission management and operation record management functions of the front-end business management system can be provided by the back-end basic system management service. The basic system management service can generate a management system configuration page and display the management system configuration page to the administrator on the front-end so that the administrator can Configure corresponding permissions for ordinary users.

For example, the administrator creates a user account, creates a role, and configures permissions on the management system configuration page, then grants permissions to the role, and then grants the role to the user's account to generate the user's permission configuration information. The front end sends the user's permission configuration information to the business gateway service, and the business gateway service forwards the user's permission configuration information to the basic system management service. The basic system management service stores the user's permission configuration information in the database in the form of a basic system management data model.

The basic system management data model relationship diagram is shown in Figure 3. The defined data model includes a user account table, a role table, a user role relationship table, a permission table, and a role permission relationship table. The user account table may include information such as the user's account, email address, and mobile phone number. The role table may include information such as role code, role name, and role type (such as administrator, ordinary user). The permission table may include information such as permission code, permission name, front-end routing, routing path, and permission type. Permission types include directories, menus, buttons, and interfaces.

The user role relationship table includes a role table ID and a user account table ID. The user account table ID is the identifier of the user account table, and the user account table ID can associate the user account table with the user role relationship table. The role table ID is the identifier of the role table, and the role table ID can associate the role table with the user role relationship table. Through the user role relationship table, the user account table can be associated with the role table. The role permission relationship table includes a role table ID and a permission table ID. The role table ID is the identifier of the role table, and the role table ID can associate the role table with the role permission relationship table. The permission table ID is the identifier of the permission table, and the permission table ID can associate the permission table with the role permission relationship table. Through the role permission relationship table, the role table can be associated with the permission table.

This embodiment configures user permissions by configuring permissions for roles and users, thereby improving the flexibility of user permission configuration. The basic system management service provides basic management functions as an independent service, so that other microservices only need to focus on their own business function development, improve development efficiency, and improve the timeliness of function release.

The cloud platform access method provided in the embodiment of the present application can be executed by a cloud platform access device. In the embodiment of the present application, the cloud platform access device executing the cloud platform access method is taken as an example to illustrate the cloud platform access device provided in the embodiment of the present application.

The embodiment of the present application also provides a cloud platform access device.

As shown in FIG. 4 , the cloud platform access device includes: a first acquisition module 10 , a second acquisition module 20 and a determination module 30 .

A first acquisition module 10 is used to acquire a user's access request to the cloud platform, wherein the access request includes a target access address;

A second acquisition module 20, used to acquire the user's access rights from the cache, the access rights including button rights and interface rights;

The determination module 30 is used to determine whether the access address corresponding to the access permission contains the target access address. The access address is determined, and when it is determined that the access address corresponding to the access permission has the target access address, the user is allowed to access the microservice corresponding to the target access address.

The access rights configured for users in the embodiment of the present application are at the minimum granularity interface level, which ensures the security of interface functions, realizes the security management and control of cloud platform interfaces, and performs unified authentication and verification on user access rights, thereby reducing the resource consumption of microservices. Microservices only need to focus on the development of their own business functions, thereby improving the development efficiency of microservices.

In some embodiments, the second acquisition module 20 is further used to call the user's access rights from the cache through the business gateway service;

The determination module 30 is also used to determine through the business gateway service whether the access address corresponding to the access permission contains the target access address, and when it is determined that the access address corresponding to the access permission contains the target access address, allow the user to access the microservice corresponding to the target access address.

This embodiment obtains the user's access rights from the cache through the business gateway service for authentication verification, which effectively improves the authentication efficiency of the business gateway service and further improves the user's access efficiency.

In some embodiments, the cloud platform access device further includes a third acquisition module, and the third acquisition module is used to:

When it is determined that the user has successfully logged into the cloud platform, the user's access rights are obtained through the basic system management service and saved in the cache.

This embodiment obtains the user's access rights through the basic system management service and saves them in the cache, so that the business gateway service can directly obtain the user's access rights from the cache for authentication verification after obtaining the user's access request, effectively improving the authentication efficiency of the business gateway service and thereby improving the user's access efficiency.

In some embodiments, the third acquisition module is further used to:

Obtaining the user's permission list from a database through the basic system management service, the permission list including directory permissions, menu permissions, button permissions and interface permissions;

The button permissions and interface permissions in the permission list are saved in the cache through the basic system management service.

This embodiment makes it easier to manage and control permissions by dividing permission types in detail.

In some embodiments, the cloud platform access device further includes a return module, and the return module is used to:

The user's permission list is returned to the user through the basic system management service.

In some embodiments, the cloud platform access device further includes a fourth acquisition module, and the fourth acquisition module is used to:

Obtaining a login request from the user for the cloud platform, wherein the login request includes login information;

The login information is verified through the basic system management service, and if the verification passes, it is determined that the user has successfully logged into the cloud platform.

In some embodiments, the cloud platform access device further includes a clearing module, and the clearing module is used to:

In the case where it is determined that the user login is invalid, the basic system management service is used to manage all the items in the cache. Clear the access rights of the user.

In some embodiments, the cloud platform access device further includes a fifth acquisition module, and the fifth acquisition module is used to:

Obtaining permission configuration information of the user, wherein the permission configuration information includes a role configured for the user and a permission list configured for the role;

The user's permission configuration information can be saved in the database through the basic system management service.

This embodiment provides basic management functions by using basic system management services as independent services, so that other microservices only need to focus on their own business function development, improve development efficiency, and improve function release timeliness.

The cloud platform access device in the embodiment of the present application can be an electronic device, or a component in the electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or a device other than a terminal. Exemplarily, the electronic device can be a server, a network attached storage (NAS) or a personal computer (PC), etc., which is not specifically limited in the embodiment of the present application.

The cloud platform access device in the embodiment of the present application may be a device having an operating system. The operating system may be a Microsoft (Windows) operating system, an Android (Android) operating system, an IOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

The cloud platform access device provided in the embodiment of the present application can implement each process of the cloud platform access method in the method embodiments of Figures 1 to 3, and will not be described again here to avoid repetition.

In some embodiments, as shown in Figure 5, the embodiment of the present application also provides an electronic device 500, including a processor 501, a memory 502, and a computer program stored in the memory 502 and executable on the processor 501. When the program is executed by the processor 501, the various processes of the above-mentioned cloud platform access method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

An embodiment of the present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the cloud platform access method of any of the above-mentioned embodiments are implemented. For the sake of brevity, they are not repeated here.

It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, a disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

Although the embodiments of the present application have been shown and described, those skilled in the art will appreciate that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present application, and that the scope of the present application is defined by the claims and their equivalents.

Claims (11)

A cloud platform access method, characterized by comprising: Obtaining a user's access request to the cloud platform, wherein the access request includes a target access address; Obtaining the user's access rights from the cache, the access rights including button rights and interface rights; When it is determined that the access address corresponding to the access permission includes the target access address, the user is allowed to access the microservice corresponding to the target access address. The cloud platform access method according to claim 1, characterized in that the method further comprises: When it is determined that the user has successfully logged into the cloud platform, the user's access rights are obtained through the basic system management service and saved in the cache. The cloud platform access method according to claim 2, wherein obtaining the user's access rights through the basic system management service and saving them to the cache comprises: Obtaining the user's permission list from a database through the basic system management service, the permission list including directory permissions, menu permissions, button permissions and interface permissions; The button permissions and interface permissions in the permission list are saved in the cache through the basic system management service. The cloud platform access method according to claim 2 or 3, characterized in that the method further comprises: The user's permission list is returned to the user through the basic system management service. The cloud platform access method according to any one of claims 2 to 4, characterized in that the method further comprises: Obtaining a login request from the user for the cloud platform, wherein the login request includes login information; The login information is verified through the basic system management service, and if the verification passes, it is determined that the user has successfully logged into the cloud platform. The cloud platform access method according to any one of claims 2 to 5, characterized in that the method further comprises: When it is determined that the user login is invalid, the access rights of the user in the cache are cleared through the basic system management service. The cloud platform access method according to claim 3, characterized in that the method further comprises: Obtaining permission configuration information of the user, wherein the permission configuration information includes a role configured for the user and a permission list configured for the role; The user's permission configuration information can be saved in the database through the basic system management service. The cloud platform access method according to any one of claims 1 to 7, characterized in that obtaining the user's access rights from the cache comprises: Retrieving the user's access rights from the cache through the business gateway service; The allowing the user to access the microservice corresponding to the target access address when it is determined that the access address corresponding to the access permission has the target access address includes: The business gateway service determines whether the access address corresponding to the access permission contains the target access address, and if it is determined that the access address corresponding to the access permission contains the target access address, the user is allowed to access the microservice corresponding to the target access address. A cloud platform access device, characterized by comprising: A first acquisition module is used to acquire a user's access request to the cloud platform, wherein the access request includes a target access address; A second acquisition module is used to acquire the user's access rights from the cache, where the access rights include button rights and interface rights; A determination module is used to determine whether the access address corresponding to the access permission contains the target access address, and if it is determined that the access address corresponding to the access permission contains the target access address, allow the user to access the microservice corresponding to the target access address. An electronic device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the cloud platform access method as described in any one of claims 1 to 8 is implemented. A computer-readable storage medium having a computer program stored thereon, characterized in that when the computer program is executed by a processor, the cloud platform access method according to any one of claims 1-8 is implemented.