通过 Google App Engine 将凭据传递到 Google Reader
如果我使用 Google 帐户登录 App Engine 应用程序,是否有办法将这些凭据从 Web 应用程序传递到另一个 Google Web 应用程序(例如 Reader)?我希望 GAE 应用程序能够使用我的 Google Reader 中的数据,而无需额外的身份验证步骤(因为我已经登录到 GAE 应用程序)。
我尝试过但失败的事情:
查看
google.appengine.api.users.User
类是否有我可以使用的任何内容(没有看到任何对此目的有用的内容)。通过登录 GAE 应用程序获取的 ACSID/SACSID 作为
urlfetch
调用中的 Cookie 传递给 https://www.google.com/reader/api/0/token;不带参数调用https://www.google.com/accounts/ClientLogin/标头,希望可能会发生一些魔法;
使用 ACSID/SACSID 调用 https://www.google.com/accounts/ClientLogin如上所述,希望奇迹会发生;
更新 我并不是试图绕过授权 - 我只是想重用用户已经输入的凭据,而不是使用单独的用户名/密码表单,让他们必须重新输入凭据。
If I'm logged into an App Engine app using a Google Account, is there a way to pass those credentials through to another Google web application (like Reader) from the web app? I want the GAE application to be able to use data from my Google Reader without an additional authentication step (since I'm already logged into the GAE application).
Things I've tried and failed with:
Looked at whether the
google.appengine.api.users.User
class had anything I could use (didn't see anything useful for this purpose).Passing through the ACSID/SACSID obtained from logging into the GAE application as cookies in the
urlfetch
call to https://www.google.com/reader/api/0/token;Calling https://www.google.com/accounts/ClientLogin with no parameters/headers in the hopes some magic might happen;
Calling https://www.google.com/accounts/ClientLogin with ACSID/SACSID as above in the hopes some magic might happen;
Update I'm not trying to bypass authorisation - I simply want to reuse the credentials that the user has already entered rather than having a separate username/password form where they have to re-enter their credentials.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
不,没有。用户没有明确授权您访问其 Google 阅读器数据,因此您不能。您必须执行单独的 OAuth 授权步骤(仅一次)才能获得他们的许可。
No, there isn't. The user did not explicitly authorize you to access their Google Reader data, so you cannot. You will have to go through a separate OAuth authorization step (once only) to get their permission to do so.