BizTalk Server 2009 对 Ruby on Rails 网站的基本身份验证
我有一个 Rails 网站，允许经过身份验证的客户端将 XML 发布到特定 URL。在此特定实例中，post 请求来自 BizTalk 2009 服务器。 Rails 不断响应 401 Unauthorized，我不知道为什么。
Rails 端的身份验证由 Restful Authentication 通过 HTTP basic auth 处理。我已经测试使用curl 和相关客户端的凭据将XML 发布到生产站点，并且看起来工作正常。 BizTalk 服务器的所有者和我已验证凭据和 URL。
BizTalk 处理基本身份验证的方式有什么特别之处吗？或者 Rails 或 Restful Auth 有什么奇怪的地方吗？有什么想法吗？ Rails 端的 Web 服务器是带有 Passenger 3 的 Nginx。
I have a Rails website that allows an authenticated client to post XML to a specific URL. In this particular instance, the post request is coming from a BizTalk 2009 server. Rails keeps responding with 401 Unauthorized and I'm not sure why.
The authentication on the Rails side is handled by Restful Authentication via HTTP basic auth. I have tested posting XML to the production site using curl and the credentials of the client in question and it appears to work fine. The owner of the BizTalk server and I have verified the credentials and the URL.
Is there something particular about the way BizTalk handles its basic authentication? Or is there something weird with Rails or Restful Auth? Any ideas? The web server on the Rails side is Nginx with Passenger 3.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您使用什么凭据进行身份验证？它必须是发送请求的 BizTalk 服务帐户的帐户。您使用什么适配器？
What credentials are you using to authenticate? It would need to be that of the BizTalk service account that is sending the request. What adapter are you using?
不幸的是，问题没有被发现。我必须修改身份验证代码来处理 Internet Explorer 中的身份验证问题（请参阅 http://rails_security.lighthouseapp.com/projects/15332/tickets/5-using-http-basic-authentication-with-ie-not-working) 。 BizTalk 可能也会有同样的问题，但我无法验证。
BizTalk 服务器的所有者也可能更新了用于联系我们服务的凭据，但我再次无法验证。
由于我们有更大的鱼要炸，所以我们不值得去追查确切的问题，因为现在一切都工作正常。当然，这可能会改变，我会更深入地挖掘，也许会更新这个线程。
Unfortunately, the problem went away undetected. I had to modify the auth code to deal with authentication problems in Internet Explorer (see http://rails_security.lighthouseapp.com/projects/15332/tickets/5-using-http-basic-authentication-with-ie-not-working). It's possible that BizTalk would have the same problem, but I can't verify.
It's also possible that the owner of the BizTalk server updated the credentials used to contact our service, but again I can't verify.
As we have bigger fish to fry, it's not worth it to us to track down the exact issue since all is working fine now. Of course that could change and I'll dig deeper and perhaps update this thread.