CN109784090A - A kind of method and system for realizing multi-tenant control based on cloud messaging service - Google Patents
A kind of method and system for realizing multi-tenant control based on cloud messaging service Download PDFInfo
- Publication number
- CN109784090A CN109784090A CN201811606646.9A CN201811606646A CN109784090A CN 109784090 A CN109784090 A CN 109784090A CN 201811606646 A CN201811606646 A CN 201811606646A CN 109784090 A CN109784090 A CN 109784090A
- Authority
- CN
- China
- Prior art keywords
- tenant
- permission
- user
- messaging service
- role
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a kind of method and system that multi-tenant control is realized based on cloud messaging service, belong to field of computer technology, the technical problem to be solved in the present invention is that the isolation every discrete data of application environment how is realized using cloud messaging service platform, technical solution are as follows: a method of multi-tenant control is realized based on cloud messaging service, this method is the physical layer interface that console provided in such a way that WEB is visual and called cloud messaging service CMSP, tenant's registration and examination & approval are completed using the physical layer interface of cloud messaging service CMSP, tenant's authorization, user's authorization and transfer of the Topic under tenant, realize the management of multi-tenant, ensure that each tenant's general character part can be shared, the part of individual character is safely isolated；Meanwhile different tenants is distinguished by URL, after tenant registers examination & approval, cloud messaging service CMSP resource and permission are distributed for tenant.2. one kind realizes multi-tenant control system based on cloud messaging service, which includes console, authentication center and cloud messaging service module.
Description
Technical field
It is specifically a kind of that multi-tenant control is realized based on cloud messaging service the present invention relates to field of computer technology
Method and system.
Background technique
Nowadays, we enter big data, cloud era.In cloud era, sharing and being isolated for resource is essential.
CMSP (cloud messaging service platform) is a kind of cloud era high-performance middleware, supports news release and subscribes to, more Topic is supported to manage
Reason etc..Product of the CMSP as cloud era, how using cloud messaging service platform realize application environment every discrete data
Isolation be current technical problem urgently to be solved.
The patent document of Patent No. CN108200125A discloses a kind of cloud messaging service platform and its installation method, dress
It sets, system, this method comprises: console determines first server and at least one second server in server cluster；It will
First default installation kit is transferred to first server, and according to the installation kit in first server installation load equilibrium node,
And the configuration parameter of production load balancing node；It is performed both by for a second server: the second default installation kit is transferred to
Current second server, and cloud message service node is installed on current second server according to the installation kit, and according to negative
Carry the configuration parameter of the configuration parameter production cloud message service node of balanced node.But the technical solution cannot utilize cloud message
The isolation every discrete data of service platform realization application environment.
Summary of the invention
Technical assignment of the invention is to provide a kind of method and system that multi-tenant control is realized based on cloud messaging service, comes
Solve the problems, such as the isolation every discrete data for how utilizing cloud messaging service platform to realize application environment.
Technical assignment of the invention is realized in the following manner, a kind of to realize multi-tenant control based on cloud messaging service
Method, this method are the physical layer interfaces that console provided in such a way that WEB is visual and called cloud messaging service CMSP, utilize cloud
The physical layer interface of messaging service CMSP is completed tenant's registration and is turned under tenant with examination & approval, tenant's authorization, user's authorization and Topic
It allows, realizes the management of multi-tenant, ensure that each tenant's general character part can be shared, the part of individual character is safely isolated, and is realized
Application environment and resource shared and it is isolated；Meanwhile different tenants is distinguished by URL, after tenant registers examination & approval, for tenant point
With cloud messaging service CMSP resource and permission；It is specific as follows:
S1, installation authentication center and console；
S2, cloud messaging service CMSP component is installed by console；
S3, tenant are registered by the WEB visual page of console；
After S4, administrator's examination & approval, permission is distributed for tenant；
S5, tenant carry out register according to the permission that administrator distributes.
Preferably, the tenant has role, the role of tenant is specifically divided into administrator role (adminRole), rents
Family role (tenantRole) and user role (userRole)；
Wherein, the tenant of administrator role is manager tenant, is owned by administrator role by the user that manager creates；
The tenant of tenant role is common tenant, is owned by user role by all users of tenant role's application for registration；
User is created by tenant.
Preferably, the permission is divided into CMSP user right, Topic permission and queue permission；
Wherein, CMSP user right includes creation user right, deletes user right, updates user right permission；
Topic permission is divided into creation theme permission, updates theme permission, monitor theme permission, deletes theme permission；If renting
Family perhaps user be endowed creation Topic permission tenant or user can create the Topic of oneself and oneself can be gathered around
Some Topic's puts message (PutMq), takes message (GetMq) and pre-reads the correspondence user that message authority is given under same tenant；
Queue permission, which is divided into, puts message authority, takes message authority and pre-reads message authority.
More preferably, tenant is registered by the WEB visual page of console in the step S3, specific as follows:
After S301, user have filled in information, apply to administrator；
S302, administrator are confirmed whether to give tenant's permission according to the information of application:
If 1., administrator give the tenant permission for creating user, show that tenant can create the user, and be tenant
Distribution CMSP user right, Topic permission and queue permission simultaneously assign the operation corresponding permission of cloud messaging service GMSP；
If 2., administrator do not give the tenant create user permission, show that tenant cannot create user.
More preferably, in the step S4 after administrator's examination & approval, permission is distributed for tenant, specific as follows:
S401, tenant access corresponding URL according to tenant's name；
After S402, authentication center are according to tenant's name, password authentification success, tenant is the cloud message that may have access to administrator's distribution
Service Source；
S403, when tenant have creation user right when, tenant can create oneself user or by the permission of oneself,
The resource possessed is given to corresponding user.
More preferably, the permission progress register that tenant distributes according to administrator in the step S5, specific as follows:
When S501, user log in, corresponding URL is accessed according to affiliated tenant's name；
After S502, authentication center are according to user name, password authentification success, user is that may have access to the corresponding cloud that tenant assigns to disappear
Cease Service Source and permission.
One kind realizing that multi-tenant control system, the system include based on cloud messaging service,
Console realizes tenant's registration of cloud messaging service with WEB visual means for installing cloud messaging service module
With the transfer of examination & approval, tenant's authorization, user's authorization and Topic under tenant；
Authentication center, for verifying whether tenant logins successfully according to username and password；
Cloud messaging service module, for tenant register with examine, role and authority distribution, tenant's authorization, user's authorization and
Transfer of the Topic under tenant.
Preferably, the role be specifically divided into administrator role (adminRole), tenant role (tenantRole) and
User role (userRole)；
Wherein, the tenant of administrator role is manager tenant, is owned by administrator role by the user that manager creates；
The tenant of tenant role is common tenant, is owned by user role by all users of tenant role's application for registration；
User is created by tenant.
Preferably, the permission is divided into CMSP user right, Topic permission and queue permission；
Wherein, CMSP user right includes creation user right, deletes user right, updates user right permission；
Topic permission is divided into creation theme permission, updates theme permission, monitor theme permission, deletes theme permission；If renting
Family perhaps user be endowed creation Topic permission tenant or user can create the Topic of oneself and oneself can be gathered around
Some Topic's puts message (PutMq), takes message (GetMq) and pre-reads the correspondence user that message authority is given under same tenant；
Queue permission, which is divided into, puts message authority, takes message authority and pre-reads message authority.
Of the invention realizes that the method and system of multi-tenant control have the advantage that based on cloud messaging service
(1), the present invention access when different tenants is distinguished by URL, all tenants after authentication center authenticates,
The resource of cloud messaging service can be accessed, all cloud messaging service resources are allocated and are isolated with tenant, user；
(2), money is realized in the operations such as the present invention can examine tenant by console, resource allocation, permission assign
The isolation in source；
(3), tenant can manage oneself resource and user according to oneself permission, realize and realized based on cloud messaging service
The isolation of environment and resource.
Detailed description of the invention
The following further describes the present invention with reference to the drawings.
Attached drawing 1 is the method flow block diagram that multi-tenant control is realized based on cloud messaging service；
Attached drawing 2 is tenant's register interface schematic diagram；
Attached drawing 3 is that tenant examines interface schematic diagram；
Attached drawing 4 is the structural block diagram that multi-tenant control system is realized based on cloud messaging service,
Specific embodiment
Cloud messaging service is based on to one kind of the invention referring to Figure of description and specific embodiment and realizes multi-tenant control
Method and system be described in detail below.
Embodiment 1:
Of the invention realizes that method this method of multi-tenant control is that console is visual with WEB based on cloud messaging service
Mode provides and calls the physical layer interface of cloud messaging service CMSP, completes tenant using the physical layer interface of cloud messaging service CMSP and infuses
Transfer of the volume with examination & approval, tenant's authorization, user's authorization and Topic under tenant, realizes the management of multi-tenant, ensures each tenant
General character part can be shared, and the part of individual character is safely isolated, and realized the shared of application environment and resource and be isolated；Meanwhile
Different tenants is distinguished by URL, after tenant registers examination & approval, distributes cloud messaging service CMSP resource and permission for tenant；It is such as attached
It is specific as follows shown in Fig. 1:
S1, installation authentication center and console；
S2, cloud messaging service CMSP component is installed by console；
S3, tenant are registered by the WEB visual page of console, as shown in Fig. 2；It is specific as follows:
After S301, user have filled in information, apply to administrator；
S302, administrator are confirmed whether to give tenant's permission according to the information of application:
If 1., administrator give the tenant permission for creating user, show that tenant can create the user, and be tenant
Distribution CMSP user right, Topic permission and queue permission simultaneously assign the operation corresponding permission of cloud messaging service GMSP；
If 2., administrator do not give the tenant create user permission, show that tenant cannot create user.
After S4, administrator's examination & approval, permission is distributed for tenant；It is specific as follows:
S401, tenant access corresponding URL according to tenant's name；
After S402, authentication center are according to tenant's name, password authentification success, tenant is the cloud message that may have access to administrator's distribution
Service Source；
S403, when tenant have creation user right when, tenant can create oneself user or by the permission of oneself,
The resource possessed is given to corresponding user.
S5, tenant carry out register according to the permission that administrator distributes, as shown in Fig. 3；It is specific as follows:
When S501, user log in, corresponding URL is accessed according to affiliated tenant's name；
After S502, authentication center are according to user name, password authentification success, user is that may have access to the corresponding cloud that tenant assigns to disappear
Cease Service Source and permission.
Tenant has role, and the role of tenant is specifically divided into administrator role (adminRole), tenant role
(tenantRole) and user role (userRole)；Wherein, the tenant of administrator role is manager tenant, is created by manager
The user built is owned by administrator role；The tenant of tenant role is common tenant, useful by the institute of tenant role's application for registration
Family is owned by user role；User is created by tenant.
Permission is divided into CMSP user right, Topic permission and queue permission；Wherein, CMSP user right includes that creation is used
Family permission deletes user right, updates user right permission；Topic permission be divided into creation theme permission, update theme permission,
Monitor theme permission deletes theme permission；If perhaps user is endowed creation Topic permission tenant or user's energy to tenant
Enough create the Topic of oneself and being capable of putting one's own Topic message (PutMq), take message (GetMq) and pre-read and disappear
Breath permission is given to the correspondence user under same tenant；Queue permission, which is divided into, puts message authority, takes message authority and pre-reads message authority.
Embodiment 2:
Of the invention realizes that multi-tenant control system, the system include based on cloud messaging service,
Console realizes tenant's registration of cloud messaging service with WEB visual means for installing cloud messaging service module
With the transfer of examination & approval, tenant's authorization, user's authorization and Topic under tenant；
Authentication center, for verifying whether tenant logins successfully according to username and password；
Cloud messaging service module, for tenant register with examine, role and authority distribution, tenant's authorization, user's authorization and
Transfer of the Topic under tenant.
Role is specifically divided into administrator role (adminRole), tenant role (tenantRole) and user role
(userRole)；Wherein, the tenant of administrator role is manager tenant, is owned by administrator angle by the user that manager creates
Color；The tenant of tenant role is common tenant, is owned by user role by all users of tenant role's application for registration；User by
Tenant's creation.
Permission is divided into CMSP user right, Topic permission and queue permission；Wherein, CMSP user right includes that creation is used
Family permission deletes user right, updates user right permission；Topic permission be divided into creation theme permission, update theme permission,
Monitor theme permission deletes theme permission；If perhaps user is endowed creation Topic permission tenant or user's energy to tenant
Enough create the Topic of oneself and being capable of putting one's own Topic message (PutMq), take message (GetMq) and pre-read and disappear
Breath permission is given to the correspondence user under same tenant；Queue permission, which is divided into, puts message authority, takes message authority and pre-reads message authority.
Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention., rather than its limitations；To the greatest extent
Pipe present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that: its according to
So be possible to modify the technical solutions described in the foregoing embodiments, or to some or all of the technical features into
Row equivalent replacement；And these are modified or replaceed, various embodiments of the present invention technology that it does not separate the essence of the corresponding technical solution
The range of scheme.
Claims (9)
1. a kind of method for realizing multi-tenant control based on cloud messaging service, which is characterized in that this method is that console can with WEB
Mode depending on changing provides and calls the physical layer interface of cloud messaging service CMSP, is completed using the physical layer interface of cloud messaging service CMSP
Transfer of tenant's registration with examination & approval, tenant's authorization, user's authorization and Topic under tenant, realizes the management of multi-tenant, ensures each
A tenant's general character part can be shared, and the part of individual character is safely isolated, and realized the shared of application environment and resource and be isolated；
Meanwhile different tenants is distinguished by URL, after tenant registers examination & approval, cloud messaging service CMSP resource and permission are distributed for tenant；
It is specific as follows:
S1, installation authentication center and console；
S2, cloud messaging service CMSP component is installed by console；
S3, tenant are registered by the WEB visual page of console；
After S4, administrator's examination & approval, permission is distributed for tenant；
S5, tenant carry out register according to the permission that administrator distributes.
2. the method according to claim 1 for realizing multi-tenant control based on cloud messaging service, which is characterized in that the rent
Family has role, and the role of tenant is specifically divided into administrator role, tenant role and user role；
Wherein, the tenant of administrator role is manager tenant, is owned by administrator role by the user that manager creates；
The tenant of tenant role is common tenant, is owned by user role by all users of tenant role's application for registration；
User is created by tenant.
3. the method according to claim 1 or 2 for realizing multi-tenant control based on cloud messaging service, which is characterized in that institute
It states permission and is divided into CMSP user right, Topic permission and queue permission；
Wherein, CMSP user right includes creation user right, deletes user right, updates user right permission；
Topic permission is divided into creation theme permission, updates theme permission, monitor theme permission, deletes theme permission；If tenant or
Person user is endowed creation Topic permission, and tenant or user can create the Topic of oneself and can will be one's own
Topic's puts message (PutMq), takes message (GetMq) and pre-reads the correspondence user that message authority is given under same tenant；
Queue permission, which is divided into, puts message authority, takes message authority and pre-reads message authority.
4. the method according to claim 3 for realizing multi-tenant control based on cloud messaging service, which is characterized in that the step
Tenant is registered by the WEB visual page of console in rapid S3, specific as follows:
After S301, user have filled in information, apply to administrator；
S302, administrator are confirmed whether to give tenant's permission according to the information of application:
If 1., administrator give the tenant permission for creating user, show that tenant can create the user, and distribute for tenant
CMSP user right, Topic permission and queue permission simultaneously assign the operation corresponding permission of cloud messaging service GMSP；
If 2., administrator do not give the tenant create user permission, show that tenant cannot create user.
5. the method according to claim 4 for realizing multi-tenant control based on cloud messaging service, which is characterized in that the step
In rapid S4 after administrator's examination & approval, permission is distributed for tenant, specific as follows:
S401, tenant access corresponding URL according to tenant's name；
After S402, authentication center are according to tenant's name, password authentification success, tenant is the cloud messaging service that may have access to administrator's distribution
Resource；
S403, when tenant have creation user right when, tenant can create the user of oneself or by the permission of oneself, possess
Resource be given to corresponding user.
6. the method according to claim 5 for realizing multi-tenant control based on cloud messaging service, which is characterized in that the step
Tenant carries out register according to the permission that administrator distributes in rapid S5, specific as follows:
When S501, user log in, corresponding URL is accessed according to affiliated tenant's name；
After S502, authentication center are according to user name, password authentification success, user is the corresponding cloud message clothes that may have access to tenant and assign
Resource of being engaged in and permission.
7. one kind realizes multi-tenant control system based on cloud messaging service, which is characterized in that the system includes,
Console is realized tenant's registration of cloud messaging service with WEB visual means and is examined for installing cloud messaging service module
It criticizes, the transfer of tenant's authorization, user's authorization and Topic under tenant；
Authentication center, for verifying whether tenant logins successfully according to username and password；
Cloud messaging service module is registered and examination & approval, role and authority distribution, tenant's authorization, user's authorization and Topic for tenant
Transfer under tenant.
8. according to claim 7 realize multi-tenant control system based on cloud messaging service, which is characterized in that the role
It is specifically divided into administrator role, tenant role and user role；
Wherein, the tenant of administrator role is manager tenant, is owned by administrator role by the user that manager creates；
The tenant of tenant role is common tenant, is owned by user role by all users of tenant role's application for registration；
User is created by tenant.
9. according to claim 7 or 8 realize multi-tenant control system based on cloud messaging service, which is characterized in that described
Permission is divided into CMSP user right, Topic permission and queue permission；
Wherein, CMSP user right includes creation user right, deletes user right, updates user right permission；
Topic permission is divided into creation theme permission, updates theme permission, monitor theme permission, deletes theme permission；If tenant or
Person user is endowed creation Topic permission, and tenant or user can create the Topic of oneself and can will be one's own
Topic's puts message (PutMq), takes message (GetMq) and pre-reads the correspondence user that message authority is given under same tenant；
Queue permission, which is divided into, puts message authority, takes message authority and pre-reads message authority.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811606646.9A CN109784090A (en) | 2018-12-27 | 2018-12-27 | A kind of method and system for realizing multi-tenant control based on cloud messaging service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811606646.9A CN109784090A (en) | 2018-12-27 | 2018-12-27 | A kind of method and system for realizing multi-tenant control based on cloud messaging service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109784090A true CN109784090A (en) | 2019-05-21 |
Family
ID=66497760
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811606646.9A Pending CN109784090A (en) | 2018-12-27 | 2018-12-27 | A kind of method and system for realizing multi-tenant control based on cloud messaging service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109784090A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110661813A (en) * | 2019-10-11 | 2020-01-07 | 浪潮软件股份有限公司 | CMSP-based identity authentication implementation method for RESTful service of object storage |
| CN110827127A (en) * | 2019-11-12 | 2020-02-21 | 河北建投水务投资有限公司 | Multi-tenant management system |
| CN110881039A (en) * | 2019-11-27 | 2020-03-13 | 杭州安恒信息技术股份有限公司 | Cloud security management system |
| CN111428256A (en) * | 2020-03-30 | 2020-07-17 | 北京东方金信科技有限公司 | Big data platform multi-tenant management system |
| CN112019543A (en) * | 2020-08-27 | 2020-12-01 | 四川长虹电器股份有限公司 | Multi-tenant permission system based on BRAC model |
| CN112311804A (en) * | 2020-11-06 | 2021-02-02 | 东北大学 | Multi-tenant service resource dynamic access authorization and authentication system and method |
| CN112788149A (en) * | 2021-01-22 | 2021-05-11 | 浪潮云信息技术股份公司 | Method and system for rapidly distributing software in distributed cloud |
| CN114827275A (en) * | 2022-04-15 | 2022-07-29 | 星环信息科技(上海)股份有限公司 | Management platform of federated tenants and resource management method of federated tenants |
| CN115396511A (en) * | 2022-08-24 | 2022-11-25 | 数字浙江技术运营有限公司 | Multi-tenant process engine creating and applying method and system |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102333115A (en) * | 2011-09-01 | 2012-01-25 | 杭州湾云计算技术有限公司 | Method and device for transforming existing Web application into SaaS multi-tenant application |
| CN102708316A (en) * | 2012-04-19 | 2012-10-03 | 北京华胜天成科技股份有限公司 | Method for isolating data in multi-tenant architecture |
| CN104123616A (en) * | 2014-07-25 | 2014-10-29 | 南京邮电大学 | Cloud computing system towards multiple tenants |
| CN104270349A (en) * | 2014-09-17 | 2015-01-07 | 广州中国科学院软件应用技术研究所 | Isolation method and device for cloud computing multi-tenant application |
| CN108200125A (en) * | 2017-12-15 | 2018-06-22 | 浪潮软件集团有限公司 | Cloud message service platform and installation method, device and system thereof |
| CN108881369A (en) * | 2018-04-24 | 2018-11-23 | 中国科学院信息工程研究所 | A kind of method for interchanging data and cloud message-oriented middleware system of the cloud message-oriented middleware based on data-oriented content |
| CN108920494A (en) * | 2018-05-21 | 2018-11-30 | 深圳市彬讯科技有限公司 | Isolation access method, server-side and the storage medium of multi-tenant database |
| CN109005218A (en) * | 2018-07-12 | 2018-12-14 | 浪潮软件集团有限公司 | Method and device for cross-gatekeeper ordered data transmission of cloud message service platform |
-
2018
- 2018-12-27 CN CN201811606646.9A patent/CN109784090A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102333115A (en) * | 2011-09-01 | 2012-01-25 | 杭州湾云计算技术有限公司 | Method and device for transforming existing Web application into SaaS multi-tenant application |
| CN102708316A (en) * | 2012-04-19 | 2012-10-03 | 北京华胜天成科技股份有限公司 | Method for isolating data in multi-tenant architecture |
| CN104123616A (en) * | 2014-07-25 | 2014-10-29 | 南京邮电大学 | Cloud computing system towards multiple tenants |
| CN104270349A (en) * | 2014-09-17 | 2015-01-07 | 广州中国科学院软件应用技术研究所 | Isolation method and device for cloud computing multi-tenant application |
| CN108200125A (en) * | 2017-12-15 | 2018-06-22 | 浪潮软件集团有限公司 | Cloud message service platform and installation method, device and system thereof |
| CN108881369A (en) * | 2018-04-24 | 2018-11-23 | 中国科学院信息工程研究所 | A kind of method for interchanging data and cloud message-oriented middleware system of the cloud message-oriented middleware based on data-oriented content |
| CN108920494A (en) * | 2018-05-21 | 2018-11-30 | 深圳市彬讯科技有限公司 | Isolation access method, server-side and the storage medium of multi-tenant database |
| CN109005218A (en) * | 2018-07-12 | 2018-12-14 | 浪潮软件集团有限公司 | Method and device for cross-gatekeeper ordered data transmission of cloud message service platform |
Non-Patent Citations (2)
| Title |
|---|
| CSDN博客: ""消息中间件选型分析——从Kafka与RabbitMQ的对比来看全局"", 《HTTPS://BLOG.CSDN.NET/U013256816/ARTICLE/DETAILS/79838428》 * |
| 知乎用户: ""云消息服务平台CMSP V1.5.0产品白皮书"", 《HTTPS://ZHUANLAN.ZHIHU.COM/P/45158210》 * |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110661813A (en) * | 2019-10-11 | 2020-01-07 | 浪潮软件股份有限公司 | CMSP-based identity authentication implementation method for RESTful service of object storage |
| CN110827127A (en) * | 2019-11-12 | 2020-02-21 | 河北建投水务投资有限公司 | Multi-tenant management system |
| CN110881039A (en) * | 2019-11-27 | 2020-03-13 | 杭州安恒信息技术股份有限公司 | Cloud security management system |
| CN110881039B (en) * | 2019-11-27 | 2022-06-21 | 杭州安恒信息技术股份有限公司 | Cloud security management system |
| CN111428256A (en) * | 2020-03-30 | 2020-07-17 | 北京东方金信科技有限公司 | Big data platform multi-tenant management system |
| CN111428256B (en) * | 2020-03-30 | 2023-05-05 | 北京东方金信科技股份有限公司 | Multi-tenant management system of big data platform |
| CN112019543A (en) * | 2020-08-27 | 2020-12-01 | 四川长虹电器股份有限公司 | Multi-tenant permission system based on BRAC model |
| CN112311804A (en) * | 2020-11-06 | 2021-02-02 | 东北大学 | Multi-tenant service resource dynamic access authorization and authentication system and method |
| CN112788149A (en) * | 2021-01-22 | 2021-05-11 | 浪潮云信息技术股份公司 | Method and system for rapidly distributing software in distributed cloud |
| CN114827275A (en) * | 2022-04-15 | 2022-07-29 | 星环信息科技(上海)股份有限公司 | Management platform of federated tenants and resource management method of federated tenants |
| CN114827275B (en) * | 2022-04-15 | 2024-03-22 | 星环信息科技(上海)股份有限公司 | Management platform of federal tenant and resource management method of federal tenant |
| CN115396511A (en) * | 2022-08-24 | 2022-11-25 | 数字浙江技术运营有限公司 | Multi-tenant process engine creating and applying method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109784090A (en) | A kind of method and system for realizing multi-tenant control based on cloud messaging service | |
| US20220224726A1 (en) | Distribution and Management of Services in Virtual Environments | |
| US11295246B2 (en) | Portable network interfaces for authentication and license enforcement | |
| CN102291452B (en) | Virtual machine management method, cloud management server and cloud system based on cloud strategy | |
| US9307017B2 (en) | Member-oriented hybrid cloud operating system architecture and communication method thereof | |
| CN102571698B (en) | Access authority control method, system and device for virtual machine | |
| CN109474632B (en) | Method, apparatus, system, and medium for authenticating and managing rights of user | |
| CN111556047B (en) | Deployment method of security service in private cloud environment | |
| WO2017143975A1 (en) | Access control method and platform | |
| CN106411857B (en) | A kind of private clound GIS service access control method based on virtual isolation mech isolation test | |
| CN108512935A (en) | data service system, method, server and computer readable storage medium | |
| CN111404753B (en) | Flat network configuration method, computer equipment and storage medium | |
| CN107949829A (en) | The virtualization apparatus management service on more session platforms | |
| CN101222497A (en) | System and method for virtualized resource configuration | |
| US10237252B2 (en) | Automatic creation and management of credentials in a distributed environment | |
| CN109413080B (en) | Cross-domain dynamic authority control method and system | |
| CN105871880B (en) | Across tenant access control method based on trust model under a kind of cloud environment | |
| EP4136558A1 (en) | Keyless authentication scheme of computing services | |
| CN103020501B (en) | Access control method and access control device of user data | |
| CN106681789A (en) | Method and device for flexible authorization of network function | |
| CN107659450A (en) | Distribution method, distributor and the storage medium of big data cluster resource | |
| CN110881039B (en) | Cloud security management system | |
| JP4843499B2 (en) | Control program, control method, and control apparatus | |
| US20130263213A1 (en) | Techniques for identity and policy based routing | |
| CN110414213A (en) | A kind of method and device to rights management in operation management system based on keycloak |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190521 |