使用 BCS 使用多个可能的帐户检索数据
我们需要使用 BCS 连接到一个第三方应用程序，以在 SharePoint 2010 Intranet 中显示信息。第三方应用程序公开了我们可以使用的 Web 服务来获取信息。但是，它只允许每组凭据同时进行 5 个会话。在生产环境中可能会出现问题，其中 60 个用户可能会同时连接，因此我们需要来自第三方应用程序的 12 组凭据，因为我们将使用应用程序中预先确定的凭据进行连接，而不是使用用户身份。 我正在考虑可能遵循的身份验证方法。一种选择是编写一个 Windows 应用程序，将每 5 个用户映射到 BCS 内第三方应用程序的一组凭据。这样，每当用户尝试连接时，我们都确信他们不会被踢出，因为他们只与其他 4 个人共享凭据。但与此同时，我们必须映射未来将添加到我们公司的每个用户。 第二个选择是保持动态。当用户尝试连接时，我们检查哪组凭据打开的会话少于五个，然后使用它。虽然这似乎需要较少的未来维护，但我不确定它是否可行。 关于我应该如何进行有什么建议吗？ 谢谢。
We have a third party application we need to connect to using BCS to display info in our SharePoint 2010 Intranet. The third party application exposes web services we can consume to get the information. However, it only allows 5 simultaneous sessions for each set of credentials. The problem might arise on production where 60 users might connect simultaneously so we would need 12 sets of credentials from the third party application since we will connect with pre-determined credentials from the app, and not with the user identity.
I am considering the possible authentication approaches to follow. One option is to write a Windows application that will take each 5 users and map them to one set of credentials from the third party app within BCS. This way, whenever a user is attempting to connect, we are sure they will not be kicked out since they share the credentials with only 4 other people. But at the same time, we have to map each user that will be added to our company in the future.
The second option would be to keep it dynamic. When the user is attempting to connect, we check to see which set of credentials has less than five sessions open and then use that. While this seems to require less future maintenance, I am not sure it is feasible.
Any suggestions about how I should proceed?
Thank you.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
撇开许可问题不谈，仅考虑技术问题，我会将 BCS 连接到 Web 服务或 .net 代码，并让它管理连接池。尽管要解决帐户问题，但这似乎是一个糟糕的解决方法。
Licensing issues aside, looking just at the technical issue, I would connect the BCS to a web service or .net code and let it manage the connection pooling. This seems to be a poor work around though to get passed account issues.