Ruby 和 Rails 与 Omniauth - 谷歌和 openid 错误
我正在使用omniauth 0.1.5 和rails 2.3.8，并成功实现了Twitter 和Facebook 身份验证。然而，Openid 给我带来了一些问题，即以下问题：
警告：向 https://www.google.com/accounts/o8/.well-known/host-meta?hd=www.google.com 无需验证服务器证书;未指定 CA 路径。 SQL（0.1ms）设置名称'utf8' SQL (0.1ms) 设置 SQL_AUTO_IS_NULL=0 执行 https://www.google.com/accounts/o8/id 的发现 发现https://www.google.com/accounts/o8/id的用户身份域名 www.google.com 缓存读取：__GAPPS_OPENID__www.google.com 执行 ID https://www.google.com/accounts/o8/id：提取 https:// /www.google.com/accounts/o8/.well-known/host-meta?hd=www.google.com：连接被拒绝 - connect(2)
这是环境中的调用。rb ：使用OmniAuth::Strategies::OpenID、OpenID::Store::Filesystem.new('/tmp')、:name => '谷歌'，：标识符=> 'https://www.google.com/accounts/o8/id'
我位于代理后面，所以我认为这可能会发挥作用，但错误消息有点模糊。另外，我已经在其他地方设置了代理。
有什么想法吗？
一如既往，干杯。
树懒型
I'm using omniauth 0.1.5 with rails 2.3.8 and have managed to implement both Twitter and Facebook authentication. Openid, however, is giving me some issues, namely the following:
WARNING: making https request to https://www.google.com/accounts/o8/.well-known/host-meta?hd=www.google.com without verifying server certificate; no CA path was specified.
SQL (0.1ms) SET NAMES 'utf8'
SQL (0.1ms) SET SQL_AUTO_IS_NULL=0
Performing discovery for https://www.google.com/accounts/o8/id
Discovering user identity https://www.google.com/accounts/o8/id for domain www.google.com
Cache read: __GAPPS_OPENID__www.google.com
Unexpected exception performing discovery for id https://www.google.com/accounts/o8/id: Error fetching https://www.google.com/accounts/o8/.well-known/host-meta?hd=www.google.com: Connection refused - connect(2)
This is the call in the environment.rb : use OmniAuth::Strategies::OpenID, OpenID::Store::Filesystem.new('/tmp'), :name => 'google', :identifier => 'https://www.google.com/accounts/o8/id'
I am behind a proxy, so I think that may have a part to play but the error message is a little vague. Also, I have set the proxy elsewhere.
Any ideas?
As always, cheers.
Slothistype
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这是一个代理问题，已通过正确设置 http 代理环境解决。
This was a proxy issue and was solved with setting the http proxy env correctly.