使用 Sharepoint 2010 用户配置文件存储面向公众的网站的用户信息

发布于 2024-09-11 10:47:26 字数 207 浏览 4 评论 0原文

我们计划使用 Sharepoint 2010 作为我们正在构建的网站的 CMS。该网站还将具有登录功能;我的老板建议我们使用 Sharepoint 的用户配置文件功能来存储该网站的用户信息(用户名、密码、联系信息等)。这比在某处使用标准列表或数据库表更好吗?我正在研究这可能如何运作;但这里有人尝试过类似的事情吗?有什么关于它的轶事可以分享吗?非常感谢任何建设性的意见。

谢谢, 坦率

We're planning to use Sharepoint 2010 as a CMS for a website we're building. This site will also have login functionality; and my boss suggested we use Sharepoint's user profile features to store user info (username, password, contact info, etc.) for the site. How is this better then say using a standard list or a database table somewhere? I'm looking into how this could possibly work; but has anyone here tried something similar? Any anecdotes about it you could share? Any constructive input is greatly appreciated.

Thanks,
Frank

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

若无相欠,怎会相见 2024-09-18 10:47:26

你问的是轶事。我有一个轶事。

不久前,我试图建立一个 Sharepoint 服务器,将用户的个人页面公开到整个互联网上。我们希望允许经过身份验证的访问,但不要求它;也就是说,普通用户将具有只读访问权限,并且还能够将 InfoPath 表单数据提交到为接收结果而创建的 Sharepoint 库。因此,用户可以使用 Infopath 网络表单发布公共信息并创建公共调查。

当我公开访问时,我遇到了一些问题。即使我使用超级管理员帐户登录,文档库首选项页面上的“未经身份验证的用户”选项也是灰色的。

最后,我必须进行一些 URL 黑客攻击才能完成这项工作。我必须将用于访问首选项页面的 URL 中的“DOC”更改为“DOCLIST”(不完全是这样,而是类似的内容),然后“所有人”选项变得可用。换句话说,实际上没有正式的方式来完成我想做的事情。

整件事让我对面向 Internet 的网站的 Sharepoint 感到非常不愉快。另请参阅 这个。 Sharepoint 实际上是专为 Intranet 使用而设计的。另一个缺点是,它比普通 CMSen 更加需要更多资源。在没有单个用户的情况下,完整的 Sharepoint 安装可能会阻塞相当强大的虚拟机。我无法评论它的可扩展性,因为我从未进行过大规模部署,但我可以说索引服务对 CPU 的占用相当大。

在我看来,LDAP 是存储用户信息的更好方法;如果您使用 Sharepoint,您可能已经拥有 AD 基础设施。无论如何,AD 将用户配置文件信息存储在 LDAP 中 - 您在“Active Directory 用户和计算机”中看到的只是一个美化的 LDAP 浏览器。

You asked for anecdotes. I have an anecdote.

A while back, I was trying to set up a Sharepoint server that exposed users' personal pages to the Internet at large. We wanted to allow authenticated access, but not to require it; that is to say, normal users would have read-only access and additionally the ability to submit InfoPath form data to Sharepoint libraries created to receive the results. The users could thus post public information and create public surveys using Infopath web forms.

When I went to make access public, I ran into a few problems. The "unauthenticated users" option on the preferences page of the document library was greyed out, even when I was logged in with a super-admin account.

In the end, I had to do a little bit of URL hacking to make this work. I had to change "DOC" to "DOCLIST" in the URL I used to access the preferences page (not that exactly, but something like that) and then the "everyone" option became available. In other words, there was actually no official way to do what I was trying to do.

The whole thing left a really sour taste in my mouth about Sharepoint for Internet-facing sites. See also things like this. Sharepoint is really designed for Intranet use only. As an additional downside, it is much more resource-hungry than normal CMSen. A full Sharepoint install can, without a single user, choke a pretty powerful virtual machine. I can't comment on its scalability as I've never done a really large rollout, but I can say that the indexing service is pretty heavy on the CPU.

Seems to me that LDAP would be a better way to store information on users; if you're using Sharepoint, you've probably already got an AD infrastructure. AD stores user profile info in LDAP anyhow - what you see in "Active Directory Users and Computers" is just a glorified LDAP browser.

国粹 2024-09-18 10:47:26

以下是我最初的想法:

PRO:合并来自外部来源(例如广告)的信息,与“其他”用户信息一起存储,以便使用相同的方式显示,是“容易”的。

缺点:我还没有遇到过提供用户个人资料存储的亚马逊物流会员提供商。

Here is my initial toughts:

PRO: It's "easy" to merge infomation from outer sources like your AD, to be stored with the "other" user information in order to be displayed using the same means.

CON: I haven't come across a FBA Membership provider for User Profile Store.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文