blocks|key|2544456|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2544457|我可以使用用户名和密码创建一个名为User的表，并根据用户类型ID显示一个表单或另一个表单。|blockquote|2544458|2544459|2544460|听起来对我来说是个合理的方法。记住破解密码。|2544461|我还会将表单中的公共控件组件化，这样您就可以重用公共部分。|2544462|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|L|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|M|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|N|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|O|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|P|7|@]|8|@]|9|$]]|$1|H|3|I|4|5|6|Q|7|@]|8|@]|9|$]]|$1|J|3|-4|4|5|6|R|7|@]|8|@]|9|$]]]|K|$]]

<blockquote>
 I could create a table called Users
 with username and password and
 according to the usertype ID show a
 form, or another form.
</blockquote>

Sounds like a reasonable way to go to me. Just remember to hash the passwords.

I would also componentize the common controls in the forms, so you can reuse the common parts.

blocks|key|1219989|text|如果您使用的是Visual，我将只使用内置的成员资格提供程序。它会自动处理你的数据库和所有的事情。没必要重新发明轮子。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1219990|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you are using Visual Studio, I would just use the built in Membership providers. That would take care of your database and everything automatically. No need to reinvent the wheel.

blocks|key|2500544|text|即使是我也不能认为自己“经验丰富”，我会给出我的答案，因为我正面临同样的问题在这几周。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2500545|我将定义一个权限掩码，以标识允许的操作，将其关联到角色组，然后将用户与组关联。更完整的是权限掩码，组定义中允许更多的粒度。|2500546|通过这种方式，可以为多个用户定义一个权限定义，这比使用每个用户类型的基础定义角色要好，因为权限掩码可以修改和扩展。|2500547|可以采用更复杂的方案，允许每个用户的权限覆盖组权限，或层次结构权限掩码，以便定义能够管理组权限的主管用户。这些模型的应用取决于所需的可伸缩性和系统的用户数。|2500548|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Even I cannot consider myself "seasoned", I would give my answer since I'm facing the same problem in these weeks.

I would define a permission mask in order to identify allowed operations, associate it to role groups, and then associate users to the groups. More complete is the permission mask, more granularity is allowed in the group definition.

In this way there is one permission definition for multiple users, which is better than define the role using a per-user type basis, since the permission mask can be modified and extended.

More complex schemes could be possible, which could allow per-user permission overriding group permission, or hierarchy permission masks in order to define supervisor users able to manage group permissions.
The application of these models depends by the required scalability and by the number of users of the system.

blocks|key|2500618|text|虽然我倾向于ASP.NET，但我还是建议您查看本文：https://web.archive.org/web/20211020202857/http://www.4guysfromrolla.com/articles/120705-1.aspx|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2500619|您可以使用内置的成员资格和角色对象(即使在桌面应用程序中)来定义您自己的特权模式。使用此特性可以消除为用户(和角色)表创建自己的数据库条目的麻烦，同时还可以为您处理密码哈希(导致更安全的应用程序)。|2500620|最后，您可能需要阅读的官方MSDN文章：|2500621|关于“成员”：http://msdn.microsoft.com/en-us/library/yh26yfzy.aspx|2500622|关于“角色”：http://msdn.microsoft.com/en-us/library/ff647401.aspx|2500623|entityMap|0|LINK|mutability|MUTABLE|url|https://web.archive.org/web/20211020202857/http://www.4guysfromrolla.com/articles/120705-1.aspx|1|http://msdn.microsoft.com/en-us/library/yh26yfzy.aspx|2|http://msdn.microsoft.com/en-us/library/ff647401.aspx^0|Q|2N|0|0|0|0|7|1H|1|0|7|1H|2|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@$A|14|B|15|1|16]]|C|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@$A|18|B|19|1|1A]]|C|$]]|$1|L|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]|T|$5|O|P|Q|C|$R|U]]|V|$5|O|P|Q|C|$R|W]]]]

Although orientated towards ASP.NET, I'd thoroughly recommend checking out this article: <a href="https://web.archive.org/web/20211020202857/http://www.4guysfromrolla.com/articles/120705-1.aspx" rel="nofollow noreferrer">https://web.archive.org/web/20211020202857/http://www.4guysfromrolla.com/articles/120705-1.aspx</a>

You can use the in-built Membership and Roles objects (even in a desktop application) to define your own schemas of privilege. Using this feature takes the hassle out of creating your own database entries for the Users (and Roles) tables, while also handling password hashing for you (leading to more secure applications).

Lastly, official MSDN articles you might want to read:

On "Membership": <a href="http://msdn.microsoft.com/en-us/library/yh26yfzy.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/yh26yfzy.aspx</a>

On "Roles": <a href="http://msdn.microsoft.com/en-us/library/ff647401.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/ff647401.aspx</a>

blocks|key|1220741|text|如果它只是一个简单的应用程序，不要使用宇宙飞船横过马路。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1220742|创建以下DB模式：|1220743|用户：用户名和散列密码|offset|length|style|BOLD|1220744|：RoleName，RoleID，RoleStrength(int)|1220745|RolesMembership：包含用户and和roleid以允许未来多个成员身份的Rolemembership表。|1220746|在设置角色时，给它们一个数字权重。ie:管理员=+1000，超级用户=+500，客人=+10。这样，在您的表单中，您可以说，如果用户级别在500或以上，设置完整视图，否则，只查看或不访问。|1220747|更好的方法是使用安全类(例如IsPowerUser或IsAdmin+)将其抽象出来。|1220748|它简单，可读性和可重用性。|1220749|entityMap^0|0|0|0|2|0|0|0|F|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@$F|Y|G|Z|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|11|8|@$F|12|G|13|H|I]]|9|@]|A|$]]|$1|N|3|O|5|6|7|14|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|15|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|16|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|U|$]]

If it's just a simple application, don't use a spaceship to cross the road.

Create the following DB schema:

Users : username and hashed password

Roles : RoleName, RoleID, RoleStrength(int)

RolesMembership : Rolemembership table that contains userid and roleid to allow for future multiple membership. 

When setting up roles, give them a numeric weight. ie: Admins = 1000, Power-users = 500, guests = 10. This way, on your forms, you can say, if user level is 500 or above, set full view, otherwise, view only or no access.

Better yet, abstract it out with a security class with methods like IsPowerUser, or IsAdmin.

It's simple, readable and reusable.

I'm going to make a small application for a business that will be used locally for scanning, and storing documents in a database located on the local machine or on a machine located in the same LAN.

I could create a table called Users with username and password and according to the usertype ID show a form, or another form. But I'm more interested in the recommended approach by seasoned programmers.

Any advice?

Edit: I'm looking for something that will be secure enough, but also extensible enough.

What is the recommended way to handle different user roles in a C# application?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我将为将用于本地扫描的业务创建一个小型应用程序，并将文档存储在位于本地计算机或位于同一LAN中的计算机上的数据库中。我可以用用户名和密码创建一个名为User的表，并根据usertype ID显示一个表单或另一个表单。但我对经验丰富的程序员推荐的方法更感兴趣。有什么建议吗？编辑：，我在寻找一些足够安全，但也足够可扩展的东...

问在C#应用程序中处理不同用户角色的推荐方法是什么？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在C#应用程序中处理不同用户角色的推荐方法是什么？EN