403 After submitting credentials on OAuth sign-in page

janole · 2012-09-13T19:42:44.000Z

For me it’s a bit more difficult as I cannot enable cookies

episod · 2012-09-13T20:46:59.000Z

Sorry for the difficulty with these endpoints – the problem should now be resolved.

Thanks,
@episod

janole · 2012-09-13T20:50:18.000Z

Yay, it’s working again for me.

Thanks a million for the quick fix, Taylor!!

alignminds1 · 2013-02-06T05:24:36.000Z

Hi,
i am getting a 403 status while working with update with media.consumerKey: ‘QyTkRg1Lp8QMVxwvtnAg’.
please give any suggestions

pramanathan1 · 2013-04-08T08:05:07.000Z

Hi guys,
now i am also getting the 403 Forbidden:The server understood the request, but is refusing to fulfill it.the previous week it’s working great in login credential page but today i got the above error. so i share my consumerKey:67KGBUuiTiGeIFQMSRGc6w.
please fix it this issue for me taylor…

janole · 2013-04-08T08:08:23.000Z

Same over here. We’ve had this before (I think a couple of months ago.)

If I remember correctly, it was related to the OAuth pages suddenly requiring cookies.

@episod fixed it quickly last time. Hope he can do it again

pramanathan1 · 2013-04-08T08:32:34.000Z

thanks for your reply janole. how episod fixed the above issue? any code including twitter+oauth sdk?if u know?

janole · 2013-04-08T08:43:51.000Z

I assume @episod sent an eMail to the “appropriate” people working on the OAuth website :-}

Hopefully it will be fixed soon. The browser I am using for authenticating via OAuth doesn’t support cookies :-/

pramanathan1 · 2013-04-08T10:02:59.000Z

so episod sent code to your email. i totally confused pls explain this issue why it occurs? and where? how u resolved this issue using episod code.please reply me.

pramanathan1 · 2013-04-08T12:41:49.000Z

mr.episod pls help me for the above issue how to solve that one?where was problem started and reason for that problem? it;s very urgent…

episod · 2013-04-08T14:59:18.000Z

Sorry for the issues, folks. We had an issue over the weekend that required a hotfix to oauth/authenticate. This hotfix ended up requiring cookies where they were previously non-required. We are working on a follow-on fix today that will resolve the underlying issue without requiring cookies for environments such as yours that do not support them. Thanks for your patience while we complete the fix.

sickp · 2013-04-08T22:13:34.000Z

Do you have an updated time estimate for this fix? No one has been able to sign in with our iOS apps for about 18 hours now.

SNCRConnectors · 2013-04-09T09:24:45.000Z

We also need urgent fix for this problem, can you please provide time estimate for when this will be fixed, thanks

drnkwlst · 2013-04-09T17:04:55.000Z

Funny thing: I’ve disabled cookies in default browser and now it works fine for me!

episod · 2013-04-09T23:55:13.000Z

Those who were having issues with web browsers that did not support cookies and oauth/authorize or oauth/authenticate should now be functional again. Let me know if you continue to experience such difficulties.

dictionarypr · 2013-04-15T20:51:51.000Z

verry good

JoeMayo · 2013-04-16T03:32:11.000Z

Same problem here - ConsumerKey: 7H7qflDJknPhWiLBDkLA

403 Forbidden: The server understood the request, but is refusing to fulfill it.

ctsdataminer · 2013-05-15T11:08:05.000Z

I am getting 401 unauthorized error. The same code was working for me before. Now it is generating a 401 error. I am using proper consumer key and consumer secret. Evreything is same, it just stopped working when I upgraded from API v1.0 to API v1.1. Kindly explain.

Mugu_Yaaro · 2013-05-26T08:26:38.000Z

For about 5 days now,i have been receiving an error message " Failed to validate oauth signature & token" when I try signing in to twitter via my windows phone.Pls can @episod or anyone help me out?

TruBeautyVee_xo · 2013-06-07T16:17:26.000Z

i dont understand since yesterday i tried following some of my friends and this keeps coming up “You are unable to follow more people at this time. Learn more here.” why is this?..i learnt that the following limit is 2000 when clearly i am only following 612 persons…this shouldnt happen please help!