|
Someone did come across an issue with the timestamp as I believe you need to use the UTC (or GMT) time, and not local time for the oauth_timestamp. But that usually gives an invalid_timestamp error, so might not be the issue here.
Plus you usually get that error at the request_token stage, not the authorization stage.
Posted 7 months ago.
(permalink)
|
|
Ok, I was using local time. I'll switch to UTC and see if that helps. Thanks.
Posted 7 months ago.
(permalink)
|
|
I'm having the same issue, so if you resolve it could you please let me know.
I've been using System.currentTimeMillis (Java) for the timeStamp, and it usually works, but sometimes I experience the refresh issue that dpup is talking about. Today it seems to be particularly bad, which leads me to believe the problem is on flickr's side. Could it have something to do with how flickr is storing the accesstoken? Why would the timestamp affect the oauth/authorize page anyway? My understanding is the timestamp is needed on the first step to retrieve the requestToken, but not on the second step where you redirect the user to the Service Provider's oauth dialog box (i.e. flickr's oauth/authorize page).
Another observation is that the time it takes before a successful request to the oauth/authorize accepts the requestToken is inconsistent (note: I'm NOT changing the request token on subsequent requests): sometimes a request to the oauth/authorize page works fine on the first request, sometimes I have to wait a few secs after the initial request , sometimes it takes 15 secs, and sometime it takes > 2 mins, so I give up.
Maybe there is some problem with with flickr's data store? Maybe the requests for the 'requestToken' and the request for the oauth/authorize are going to different servers and they aren't in sync. IDK, I'm just throwing ideas out there, maybe I'm screwing something up and unaware of it.
Posted 7 months ago.
(permalink)
|
|
|
Your symptoms are pretty consistent with what I was experiencing.
The only explanation I can think of is if Flickr were using oauth_timestamp to expire the tokens.
Posted 7 months ago.
(permalink)
|
|
|
Were you able to resolve your issue by changing the timestamp to UTC?
Posted 7 months ago.
(permalink)
|
|
|
The timestamp is the number of seconds, so assuming you are taking the integer division of System.currentTimeMillis() then that should work correctly.
It does sound like there might be something slightly askew on the Flickr side.
Posted 7 months ago.
(permalink)
|
|
|
I am taking the integer division of System.currentTimeMillis(), and you're right, this should work.
Dpub said, "Your symptoms are pretty consistent with what I was experiencing." The use of 'was' makes me think that he resolved his issues. I'm curious if he actually did resolved his issue, or at least stopped observing it.
Posted 7 months ago.
(permalink)
|
|
|
Correcting for local timezone doesn't seem to have helped, I thought it had but today the problems have resurfaced.
This is from a node app and I'm using:
Math.floor(date.getTime() / 1000);
Posted 7 months ago.
(permalink)
|
|
|
OK cool, because I would have been confused if that fixed it for you. I'm fairly confident that it's a flickr issue. I'm throwing a Thread.sleep in before the redirect, this is ugly, and I don't like doing it, but it lowers the probability of flickr rejecting the access token. I hope flickr fixes this soon.
Posted 7 months ago.
(permalink)
|
|
|
I don't know how to file a bug with flickr, if you guys do, could you please file a bug? I started another thread and hopefully that will help get a flickr developers attention: www.flickr.com/groups/api/discuss/72157628039392106/
Posted 7 months ago.
(permalink)
|
|
|
Just to say I've played around with adding and subtracting various amounts of minutes to the timestamp. For small values (+/-10 minutes) it still works for me. For larger values (+/-60 minutes) I get timestamp_refused on the original request_token call.
So I don't think this is down to the timestamp unfortunately. Which only seems to leave something on Flickr's side of things.
Posted 7 months ago.
(permalink)
|
|
|
Oh, and consider cross posting your bug to the Flickr API mailing list.
Posted 7 months ago.
(permalink)
|
|
|
Thanks for checking this out as well! I'll cross post to the Flickr API mailing list as you suggested.
Posted 7 months ago.
(permalink)
|
|
I'm not usually the one to write "me, too" posts, but I have also experienced a sporadic failure like that described by dpup. I have been depending on Pablo Fernandez's Scribe library for most of the heavy lifting, so I don't have direct control over timestamps and nonces.
Posted 7 months ago.
(permalink)
|
|
Same here, using UTC.
Earlier it worked fine.
Problems with my app on WP7 Mango using SDK7.1
Posted 7 months ago.
(permalink)
|
|
|
Anyone figured out any reliable work arounds. Things seem to work fine for a while, then start flaking out. It's kind of embarrassing because it looks like an app problem (which it may very well be, but it'd be nice to know what we're all doing wrong).
Posted 7 months ago.
(permalink)
|
|
Hi everyone,
Thanks for all of the reports regarding this issue. It looks like there was a bug on our side that lead to a delay when reading the request token in the authorize step.
We believe the issue to be resolved, but I wanted to see if I could get some feedback. Have you recently encountered this issue? If so, when was the last time you saw it? Are you still getting reports about it?
Thanks so much!
Posted 6 months ago.
(permalink)
|
|
Hi!
Today, updated version of my app (FlickrBucket) rejected by Apple with screenshot what dpup described.
Before that, after first release(2011-12-23), one or two users reported that issue, but, after relaunching app and restarting authorization process from the start solved the problem, while most of other users don't seem to have that issue at all.
I think this issue happens very randomly, and it would be great if I can figure out why.
I googled, to find another recent case:
comments.gmane.org/gmane.comp.web.flickr.api/7696
@jamalfanaian, would you please tell us what you fixed recently? Is it related to oauth_timestamp entirely?
Thanks!!
Posted 5 months ago.
(permalink)
|
|
Hi,
I have been having this issue for two weeks now. I intermittently get "token_rejected" from Flickr after I authorize with their web site. I am sending them the exact access_token they send back to me. It seems like this problem occurs for a while and then starts working fine again.
Here is the URL query sent back from Flickr after authorizing my app:
oauth_token=72157628985635565-1b3d95b5e0bc46e9&oauth_verifier=eeda2b4dec8055db
In Short, Flickr sends me:
oauth_token=72157628985635565-1b3d95b5e0bc46e9
I send them back:
oauth_token=72157628985635565-1b3d95b5e0bc46e9
Then Flickr says my token is rejected. Is this on the Flickr side?
Thanks!!
Originally posted 4 months ago.
(permalink)
Heather92115 edited this topic 4 months ago.
|
|
I haven't seen this issue myself, but I just had a user report that she got the, "Oops! Flickr doesn’t recognise the “oauth_token” this application is trying to use" message when using my site. She went back and tried again and then could get through.
I've adjusted to the UTC time, so I don't think that's it.
I just launched my app and this is the first person to say anything. I'm sharing in case this is still an open issue.
Posted 4 months ago.
(permalink)
|
|
|
Heather: Your issue is different from the one listed in this post. The one here is about the error appearing on the authentication page on Flickr, but you are getting the error when you are calling the access_token URL (if I understand you correctly).
Can you confirm that the oauth_token that Flickr sends back to you is the same as the request token returned by the request_token URL?
Posted 4 months ago.
(permalink)
|
|
|
Hi Sam, thanks for the quick response. I am running into trouble when requesting the access token after receiving control back from Flickr/Yahoo.
I didn't get a failure this morning, so here is a successful login:
Request token: http ://www.flickr.com/services/oauth/request_token?oauth_callback=flckr1%3A%2F%2Foauthlogin&oauth_consumer_key=..... &oauth_nonce=179761436&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1327346122&oauth_version=1.0&oauth_signature=R8hrVli%2FH%2FMKxRNdnLAC%2FOuvqco%3D
Flckr response: oauth_callback_confirmed=true&oauth_token=72157629000915265-9fda2fc3f85b4b16&oauth_token_secret= ......
Request auth for app from Flickr user: http ://www.flickr.com/services/oauth/authorize?oauth_token=72157629000915265-9fda2fc3f85b4b16
Flickr response after app/user auth: flckr1 ://oauthlogin?oauth_token=72157629000915265-9fda2fc3f85b4b16&oauth_verifier=92d09a26ce4aa7df
Access token request: http ://www.flickr.com/services/oauth/access_token?oauth_consumer_key=..... &oauth_nonce=276783183&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1327346132&oauth_token=72157629000915265-9fda2fc3f85b4b16&oauth_verifier=92d09a26ce4aa7df&oauth_version=1.0&oauth_signature=Yu5yAm61awSr9ITqA%2FBW6AllNIs%3D
Access token response: fullname=Heather%20Stevens&oauth_token=72157628865866341-fbc415f68c67449a&oauth_token_secret=...... &user_nsid=59195110%40N02&username=Heather92115
On failed logins, I would get a "token_rejected" response from Flickr when making the access token request. I can confirm that the auth_token received from Flickr stays the same at least in my logs. This seems to happen when I login often to debug my app. Any help would be greatly appreciated.
Originally posted 4 months ago.
(permalink)
Heather92115 edited this topic 4 months ago.
|
|
We had previously been seeing the "does not recognize the 'oauth_token'" error, but that went away a few weeks ago, until today. We've seen it a couple of times, but we're also seeing another larger problem.
Now we are seeing the 401 oauth_problem=token_rejected error at an extremely high rate. Something like 2/3rds of our requests are failing with this.
Clicking refresh on our error page (which includes the oauth data in the URL) succeeds afterward. There is definitely a race on Flickr's side. We might add a sleep(1) to see if this improves the situation.
Posted 4 months ago.
(permalink)
|
|
I wonder if it's worth handling the error and retrying a set number of times?
Posted 4 months ago.
(permalink)
|
|
|
That's the workaround I've done for now; I repeatedly sleep for a few seconds and then retry. Seems to work after 2-3 tries and 3 seconds or so.
Posted 4 months ago.
(permalink)
|
|
|
So, if I understand correctly, if the access token request is rejected due to the token, sleep and then keep trying again until it works?
Posted 4 months ago.
(permalink)
|
|
|
I added a sleep of 1 second with 2 retries. So far the logic hasn't been triggered as the fist access token request has come back good. Hopefully, I won't need the sleeps due to the diminished user exp.
Thanks everyone for your input.
Posted 4 months ago.
(permalink)
|
|
|
According to our logs, we're no longer seeing these errors (even without the workarounds). Thanks!
Posted 4 months ago.
(permalink)
|
|
authorize page for phone is too small, how to solve this problem, make page size suitable for mobile.
Posted 2 months ago.
(permalink)
|
Would you like to comment?
Sign up for a free account, or sign in (if you're already a member).
|
Flickr API /
Discuss
Feed – Subscribe to Flickr API discussion threads
