Windows 窗体中的角色和权限
我想将我们当前的 Windows 窗体安全性更新为更加灵活的东西。
目前，我们的用户表中有一个名为“Access_Level”的列，该字段保存一个 int 值（1 到 4），然后用于确定用户对应用程序某些区域的访问权限。
当系统很小时，这工作得很好，但现在系统正在快速增长，所以我认为现在是更新用户访问权限并可能引入角色的好时机。
总体而言，该系统已在多家商店使用，并且拥有大量用户。 每家商店都提供多种不同的服务，但并非所有商店都提供全部/相同的服务。
用户需要能够访问适用于他们登录的商店的服务。 一些用户还需要能够访问特定服务的“管理”功能。
然后，我们拥有一些更高级别的访问权限，其中包括 IT 支持、高级经理和审计员。
任何人都可以建议（或链接到）一种灵活、简单的方式来引入这一点，这种方式允许我们管理访问权限，而不必总是更新应用程序代码。
谢谢。
I am wanting to update our current windows forms security to something a lot more flexible.
At the moment we have a single column in thew users table which is named 'Access_Level', this field holds an int value (1 to 4) which is then use to determine users access to certain areas of the application.
This worked fine when the system was small, but the system is growing rapidly now so I think it is a good time to update the user access and possibly introduce roles.
As a basic overview, the system is used in a number of shops and has a large number of users.
Each shop provides a number of different services, but not all shop provide all/the same as eachother.
Users need to be able to access the services applicable to the store they are logged in at.
Some users also need to be able to access 'admin' features for particular services.
We then have some higher level access which includes IT Support, Senior Managers and Auditors.
Can anyone suggest (or link to) a flexible, simple way of introducing this, in a way which will allow us to manage access permissions without always having to update the application code.
Thank you.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
请参阅Windows 窗体中的 SSO 的解决方案
“当用户登录时，您还可以存储在用户表中用户正在使用的 PC 的一些唯一 ID（例如 PC 名称、IP 地址等）每次在某些 PC 上启动支持 SSO 的 C# 应用程序时，它都可以首先在 DB 中检查是否有该 ID。存在 PC ID在用户表中（在登录用户的记录中）如果是，则可以跳过登录表单，例如将找到的用户名显示为当前用户名。
您可以设置 SSO 的粒度。例如，如果用户表中存储了子网地址，则该子网中的 PC 用户只需登录一次。如果存储了当前 Windows 用户的 GUID，则登录。退出 Windows 并以其他用户身份登录将需要另一个用户登录系统。”
See the solution for SSO in Windows Forms
"When a user logs in, you can also store in the Users table some unique ID of the PC (e.g. PC name, IP address, ...), on which the user is working. Every time an SSO-capable C# app starts on some PC, it can check in DB first whether the ID of the PC is present in the Users table (in the record of a logged-in user). If yes, then it can skip the login form, and e.g. show the name of the user it found as the current one.
You can set the granularity of the SSO to any level you want. For example, if a subnet address is stored in the Users table, then the users of the PCs in this subnet have to log-in only once. If the GUID of the current Windows user is stored, then logging out of Windows and logging in as a different user will require another log-in to the system."