无需用户干预的Flickr API认证 [英] flickr api authentication without user intervention

查看:170
本文介绍了无需用户干预的Flickr API认证的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我想用我自己的凭据才刚刚抓住一个频繁的基础上,从有一些数据编程查询Flickr的API。看来,Flickr的API现在利于OAuth的。
我的问题是:我应该怎么没有认证只是为自己的用户干预的API?是否有可能更多?

I would like to programmatically query the Flickr API using my own credentials only just to grab some data from there on a frequent basis. It appears that the Flickr API is favouring OAuth now. My question is: how should I authenticate the API without user intervention just for myself? Is it possible any more?

推荐答案

一旦你收到的oauth_token(访问令牌),你可以用它为多个后续API调用。您应该能够坚持令牌在数据存储(我没有这样做我自己),甚至在您的应用程序重新启动使用。当然,你仍然需要写code,以获得访问令牌的第一次。

Once you have received an oauth_token (Access Token), you can use it for multiple subsequent API calls. You should be able to persist the token in a data store (I haven't done this myself) and use it even after your application restarts. Of course, you still need to write the code to get the Access Token the first time.

如果您的应用程序已经使用旧的认证API codeD,它看起来像有一次通话,你可以得到一个新的风格的访问令牌。请参见 http://www.flickr.com/services/api/auth。 oauth.html#过渡

If your application is already coded using the old authentication API, it looks like there is a one-time call that you can make to get a new-style Access Token. See http://www.flickr.com/services/api/auth.oauth.html#transition

即使你没有codeD应用,你也许可以使用API​​浏览器对于任何来电要求身份验证(的 flickr.activity.userComments 的,例如)收获的api_sig和AUTH_TOKEN。

Even if you don't have a coded application, you might be able to use the API Explorer for any of the calls that requires authentication (flickr.activity.userComments, for example) to harvest an api_sig and auth_token.

这篇关于无需用户干预的Flickr API认证的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆