1 Star 1 Fork 196

redsnower / SAAS-UPMS

forked from LC / SAAS-UPMS 
加入 Gitee
与超过 1200万 开发者一起发现、参与优秀开源项目,私有仓库也完全免费 :)
免费加入
克隆/下载
贡献代码
同步代码
取消
提示: 由于 Git 不支持空文件夾,创建文件夹后会生成空的 .keep 文件
Loading...
README
Apache-2.0

通用用户权限系统

一、介绍

企业级多租户后台权限管理框架,使用前后端分离的方式。后端使用sping cloudeureka作为注册中心,前端使用vue。用nginx做负载均衡和前端运行环境。

实现了成员拥有多种角色、多个组织机构的菜单显示控制和接口的数据权限控制。可以设置只显示一个角色和一个组织机构的权限菜单,并通过切换角色或者切换组织机构来显示对应的页面和数据,也可以设置同时显示拥有的多个角色的权限菜单和数据,并且可以做到对接口的正确数据权限校验。举个例子,成员A拥有角色A和角色B,角色A可以查询修改 组织A和B的权限,角色B可以查询组织B和C的权限,那么成员A在查询列表上就能查询到组织A、B、C的数据,但是只能修改其中组织A和B的数据,无权修改组织C的数据。

权限前端内置实时IM系统,支持多人群聊、单对单好友聊天、好友添加、群组添加、好友消息是否读取等功能。

业务系统前端可以使用iframe的方式进行嵌入,也可以使用权限前端的基础模板进行二次开发,

业务系统后端引用一个upms-client包,并配置一些参数,即可实现接口基本的数据权限控制。

二、软件架构

  1. 后端框架:spring cloudmybatisnetty
  2. 前端框架:vueant-designecharts
  3. 缓存:redis
  4. 数据库:
    • mysql: (需要修改mapper.xml中模糊查询语句才能正常使用)
    • sqlite: (目前正在使用)

三、主要功能:

1 多租户管理

租户属于2B业务,租户之间数据隔离,可以为不同的租户开通不同的2B应用及相关的菜单权限。

TODO: 后期会添加针对租户开通应用及具体菜单的访问量统计功能;添加访问量阈值设定功能;访问量超过阈值,自动进行锁定功能。

注意: 新注册的租户默认开通系统权限管理的应用权限,但是没有开通改应用下菜单的权限,需要在租户管理-应用信息中单独进行开通。还可以在运营后台-配置管理界面,配置默认开通应用及预制角色。

2 多应用管理

应用分为 2B2C和运营三种类型。

2B:针对租户,每个租户各自管理各自的成员,实现了对租户的数据隔离,可以设置预制角色及菜单资源信息。
2C:针对该平台用户,可以设置菜单资源。
运营:针对运营人员,可以设置菜单资源,在运营角色管理页面,可以控制运营人员权限。

菜单分为分类导航、菜单页面、查询按钮、操作类按钮四类,其中查询和操作类按钮会绑定接口信息,用以实现接口级别的权限控制。

预制角色实现了页面及接口访问权限和七级数据权限控制。权限挂接在角色中,通过给组织和人员授权不通的角色,来实现不同的人员权限的控制。

0:可以操作该租户的所有数据
1:可以操作所属机构及下级机构所有数据
2:可以操作所属机构及当前机构所有下级机构数据(感觉这级权限有点脱离需求,虽然实现了)
3:可以操作所属机构的数据
4:可以操作当前机构及下级所有机构数据
5:仅能操作当前机构数据
6:仅能操作用户自己的数据

3 预制角色和自定义角色功能

预制角色在运营后台-应用管理进行创建,自定义角色在租户权限管理后台-角色管理界面进行创建。

预制角色的意义及定位:

1)每个新建立的租户,其超级管理员必须有管理这个租户所有功能的权限,可以通过授予默认预制角色来快速进行授权,该配置可以在运营后台-配置管理页面进行配置。
2)对应人员较少的租户来说,预制角色即可覆盖所有租户成员,方便租户快速掌握使用系统。

自定义角色意义及定位:

1)每个租户可以自定义专属于自己的角色,用于满足企业自身的个性化权限控制需求。
2)对应人数较多,业务分级较为复杂的租户。

角色分为组织角色组织成员角色

组织角色 给具体的组织机构进行授权,授权后的组织机构下的所有成员都有该角色的权限。

组织成员角色 需要先对组织机构进行授权,然后需要对该组织机构下的具体成员进行授权,只有该组织机构下的具体成员授权了这个角色,才会拥有这个角色的权限。

组织角色是为了进行批量授权,不用每个成员都单独进行授权,加快授权速度。

组织成员角色是为管理人员设置的,例如组织机构的司长、局长、部长、组长之类的,他们的权限需要区别于普通的成员。

注: 有兴趣的可以去看登陆相关的逻辑,在登陆的时候进行用户菜单的生成和接口数据权限的计算,这块是整个系统最复杂的地方。

4 所有应用的接口管理

引用了upms-client包的应用会自动将接口信息进行收集并显示在这,在这可以查看该平台所有应用的所有接口信息。

TODO: 1)各个接口的访问量统计信息展示。2)接口文档。3)接口调试。

5 接口访问统计

现实现,小时-接口访问统计、小时-租户即可访问统计、日-接口访问统计,日-租户访问统计,接口访问量top10,租户访问量top10

TODO: 后期实现IP访问量TOP10、应用内互相调用统计图及对外接口访问统计图。

注: 有兴趣的小伙伴可以仔细看下这个页面的请求信息,这六个统计功能全都是一个后台接口不同的参数实现的。

6 快速实现应用接口的访问控制

后端引入upms-client包,配置文件中设置upms.loginCheck=true,并在controller类上加个注解@UserLoginAnnotation(checkDataPower = true),即可实现接口的自动统计,具体接口访问量的自动统计,在具体的处理方法里使用 ThreadUserUtils.getLoginUser() 即可获取到当前请求用户登陆信息,使用 ThreadUserUtils.getLoginUser().getApiDataPower() 即可获取到用户具体的数据权限,apiDataPower权限规则为

@Data
public class ApiDataPower {
    // 租户id
    private Long tenantId;
    // 成员id
private Long memberId;
    /**
     * 能操作的组织机构列表
     * 为null,可以操作租户下所有组织机构数据
     * 为空, 只能操作当前登陆人的数据,memberId必填
     * 不为空,可以操作列表中组织机构的数据
     */
    private List<Long> orgList;
}

这样做的目的是为了分离业务,各个微服务做各个微服务自己的业务,微服务要使用接口权限校验时,直接引包和配参数就行了,不需要自己实现相关的功能。 ​

当然数据级别的权限是需要根据具体业务具体处理的,我这只是提供了一个方便的方式,在某个具体的是方法里,可以用如下的方式获取具体的数据权限数据进行处理。

    @PostMapping("/getList")
    public NCResult<Pcgl> getList(@RequestBody QueryVO<Pcgl> queryVO) {
        ApiDataPower apiDataPower = ThreadUserUtils.getLoginUser().getApiDataPower();
        return pcglService.getList(queryVO);
    }

四、详细功能介绍

详细功能介绍

五、运行和部署

运行部署

六、结束

写的比较简略,后期会把文档补齐。 最后,水平有限,欢迎交流。

Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

简介

SAAS通用权限管理系统,包含多租户权限管理系统和运营管理系统,在线IM系统,后端spring cloud,前端vue 展开 收起
Java
Apache-2.0
取消

发行版

暂无发行版

贡献者

全部

近期动态

加载更多
不能加载更多了
Java
1
https://gitee.com/lvjianliang/nodecollege-upms.git
git@gitee.com:lvjianliang/nodecollege-upms.git
lvjianliang
nodecollege-upms
SAAS-UPMS
master

搜索帮助