使用 FBA 的 SharePoint 组\角色
我正在运行一个 FBA Web 应用程序，有 2 个网站集。 目前，我在一个网站集中有一个 SharePoint 组，我想向另一网站集中的该组分配权限。 由于SharePoint组是网站范围的，我想使用FBA角色..
有什么关于如何做到这一点的说法，或者这是否是推荐的方式？
谢谢。
I'm running an FBA web app, having 2 Site collections.
Currently I have a SharePoint group in one site collection, and I would like to assign permission to that group in the other site collection.
Since SharePoint groups are site scoped, I thought using FBA roles..
Any words on how to do this, or if this it the recommended way?
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
无论网站集的数量或身份验证方法如何，我都喜欢 SharePoint 组内的 AD 组或 FBA 角色。它只是更干净，并减少了网站未来的维护量。
一旦 FBA MembershipProvider 开始工作（无论是 AspNetSqlMembershipProvider 还是自定义的），困难的部分就完成了。相比之下，添加角色支持很容易。
有许多让角色发挥作用的示例：此处，此处，此处，此处，以及此处。
我要强调的一点是，除了在configuration/system.web/roleManager/providers下的web.config中注册RoleProvider之外，还要确保将其添加到configuration/SharePoint/PeoplePickerWildcards中：
本节中的条目是SharePoint将要执行的内容用于在将 FBA 角色添加到 SharePoint 组时验证 FBA 角色。
I am a fan of AD groups or FBA roles inside of SharePoint groups regardless of the number of site collections or authentication method. It is just cleaner and cuts down the amount of maintenance for the site going forward.
Once you have an FBA MembershipProvider working (whether AspNetSqlMembershipProvider or custom), the hard part is done. Adding role support is easy by contrast.
There are many examples of getting roles to work: here, here, here, here, and here.
The point I would emphasize is in addition to registering your RoleProvider in the web.config under configuration/system.web/roleManager/providers, be sure to also add it to configuration/SharePoint/PeoplePickerWildcards:
The entries in this section are what SharePoint will use to verify the FBA role when you add it into a SharePoint group.
即使您使用 FBA，这些组仍将处于站点范围内。不幸的是，您将需要创建要在两个网站集上使用的组并处理每个网站集的权限。
Even if you use FBA, the groups will still be site scoped. You will need to create the groups you want to use on both site collections and deal with the permissions on each site collection unfortunately.