-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to obtain a request token from the Twitter api #161
Comments
Hi @ThomasArdal - I have honestly no idea :( If it was -every- time, then I would have guessed it was because of POODLE and SSLv3 was disabled. Could you try adding this to ... say your global.asax startup stuff ServicePointManager.Expect100Continue = true; or in the The error feels like it's trying to do the SSL cert dance .. and fails. This means it could be because of some invalid cert getting dl'd (from a rogue target server) or a timeout while trying to grab the cert details.. for example. |
Settings those statics is global, right? I mean every communication from my server would then use those settings? |
Yep, correct - I believe so. |
@ThomasArdal Heya - any update for us, on this? Did it work, not work, you flipped a desk? |
I'm not sure that I would want to switch to SSL3, But I'll try the expect 100 setting. I have other out-going requests from my server and I want to make absolutely sure that I don't mess up any of those using the new global settings. By the way, I cannot re-create the error localhost. The error only happens on Azure, but I'm not using any other environments for staging and production, why I'm not sure if this is Azure related or not. |
@ThomasArdal URGH - oops. nononon. bad, me. not SSL3 .. that is the vulnerable protocol highlighted via POODLE. try this: my reasoning is that, when you do a call to Twitter, the code might be using the vulnerable protocols and therefore twitter is rejecting the request. (NOTE: I have no idea how the web request determines which ssl protocol to use. I'm guessing there's an initial handshake with this info in it). |
Setting SecurityProtocol to Tls12 didn't solve the problem. |
Thoughts @phillip-haydon ? |
I think there's something wrong in general with the way I use SimpleAuthentication. I constantly get errors like these: SimpleAuthentication.Core.Exceptions.AuthenticationException: Failed to obtain a request token from the Twitter api OR the the response was not an HTTP Status 200 OK. Response Status: 0. Response Description: . Error Message: The request was aborted: Could not create SSL/TLS secure channel.. SimpleAuthentication.Core.Exceptions.AuthenticationException: Failed to retrieve an authorization code from Google. The error provided is: access_denied SimpleAuthentication.Core.Exceptions.AuthenticationException: No code parameter provided in the response query string from WindowsLive. System.ArgumentException: ProviderKey value missing. You need to supply a valid provider key so we know where to redirect the user Eg. providerkey=google. SimpleAuthentication.Core.Exceptions.AuthenticationException: Reason: user_denied. Error: access_denied. Description: Permissions error. |
Any updates on this issue, something you've experienced elsewhere or similar? I'm planning to switch to ASP.NET Identity, but I could really save the development hours, if there's a solution with SimpleAuthentication that works. |
Same exception message? |
Yeah, same message. |
I just encountered this running in azure. SimpleAuthentication.Core.Exceptions.AuthenticationException: |
@Dashue more info, please.
|
Unfortunately wasn't me, I just saw it in the AppInsights logs. … Might the operating system be the commonality in with this problem? |
|
Shouldn't this be a completely other thread? |
probably @ThomasArdal - i was testing the waters to see if it is/was. |
Sorry for the confusion, I assumed it would be understood as in context of the thread. I should have been explicit that my messages was the info I received when getting this: |
Same error then :) I think it may be caused by someone not hitting "Allow Access" when visiting the Twitter login screen, but I'm not sure. |
I keep getting the following exception from time to time:
"Failed to obtain a request token from the Twitter api OR the the response was not an HTTP Status 200 OK. Response Status: 0. Response Description: . Error Message: The request was aborted: Could not create SSL/TLS secure channel.."
The error can occur and if I try again 3 seconds later, everything works. Here's the entire stacktrace:
The text was updated successfully, but these errors were encountered: