有密码和无密码的 asp.net 会员用户
我正在尝试找到一种方法来处理 Intranet 系统的两种类型的用户。有登录的用户，也有未登录的用户。我需要将两种类型的用户存储在成员资格数据库中。有人对这个问题有通用的解决方案吗？
这是一个活动预订系统。 AD 中的用户将看到该应用程序。我们需要将操作系统名称以及 AD 中的一些其他属性存储在我们的会员数据库中。使用 Request.ServerVariables() 捕获操作系统名称。我们需要存储这些“请求者”详细信息以及有关正在预订的活动的其他详细信息。除了这些用户之外，还有实际登录系统的用户。我希望将两种类型的用户存储在会员资格数据库中，以便在检索事件时，也将从会员资格数据库中检索用户详细信息
I am trying to find a way to handle two types of users for an intranet system. There are users who login and there are those who do not. I need to store both types of users in the membership db. Does anyone have a common solution to this problem?
This is for an event booking system. The users who are in AD will see the app. We need to store the O/S Name along with a few other attributes from AD in our membership db. The O/S Name gets captured using the Request.ServerVariables(). We need to store those "requester" details along with other details about the event that is being booked.. In addition to those users, there are users that actually log into the system. I was hoping to store both types of users in the membership db, so that when an event is retrieved, the user details will get retrieved from the membership db as wel
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
如果您可以使用“集成 Windows 身份验证”，您就可以访问有关连接到您的系统的用户的一些信息。
因此，您可以在一般情况下使用此信息，而无需登录。
如果用户想要更多访问权限，他可以使用特殊的用户名/密码登录该站点。
If you can use 'Integrated Windows Authentication' you have access to some information about the user connecting to your system.
Therefore you could use this information for the general case, without the login.
If a user then want's more access, he can logon to the site with a special username/pwd.
成员资格数据库通常会限制一组用户对 Intranet 站点上特定应用程序的访问。只有那些在 Active Directory 中作为网络用户的人才能首先看到 Intranet。并且只有在其会员系统中被授予应用程序权限的网络用户的子集才能看到该链接和/或能够获得一个角色或另一个角色的访问权限。您能否更具体地说明您想要实现的目标？ :-)
A membership DB would typically restrict access to a set of users for a particular application on an Intranet site. Only those who are in Active Directory as network users would even see the Intranet in the first place. And only a subset of those network users who have been granted privileges for your application in its membership system would see the link and/or be able to gain access in one role or another. Can you be a little more specific with respect to what you are trying to achieve? :-)