[twitter-dev] Request token failed
Hello, From out of nowhere I got Failed to validate oauth signature and token when I do a request token (GET with https on this url : https://api.twitter.com/oauth/request_token). It was working since several days. Is it normal ? Matthieu -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: New oAuth Authorization screen is unusable on phone webbrowser control
On Apr 30, 12:09 pm, Tom van der Woerdt i...@tvdw.eu wrote: I've heard this before. It sounds like all UIWebView, WebBrowser and probably Android's WebView are blocked. This is definitely a *good* thing for security reasons. They are not blocked, it's *only* a problem of layout. The workaround I recommend: launch the actual browser, using a yourapp:// link (something like myapplication://tokenDone) as the return URL. This is a LOT safer for the users. I have the same problem, and I don't see why using a webcontrol is a security problem. Since xauth is the exception, why twitter is making the use of oauth so hard ? Matthieu -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: New oAuth Authorization screen is unusable on phone webbrowser control
On Apr 30, 7:13 pm, Tom van der Woerdt i...@tvdw.eu wrote:
On 5/1/11 12:47 AM, Matthieu GD wrote: On Apr 30, 12:09 pm, Tom van der
Woerdti...@tvdw.eu wrote:
I've heard this before.
It sounds like all UIWebView, WebBrowser and probably Android's WebView
are blocked. This is definitely a *good* thing for security reasons.
They are not blocked, it's *only* a problem of layout.
Are you sure? A block of CSS saying html { display: none; } doesn't
look like a problem, more like a feature. The workaround I recommend:
launch the actual browser, using a
yourapp:// link (something like myapplication://tokenDone) as the
return URL. This is a LOT safer for the users.
I have the same problem, and I don't see why using a webcontrol is a
security problem. Since xauth is the exception, why twitter is making
the use of oauth so hard ?
You should read the article athttp://goo.gl/xI0PZ
Not sure if my previous message get trough.
ok now we know it's insecure. But why removing the page without notice
since it's not easy to deploy a new version of a native application?
We have lived with xAuth (and it's still used by some applications
like full-fledged clients) during several months until oauth was
ready.
Matthieu
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: New oAuth Authorization screen is unusable on phone webbrowser control
On May 1, 7:52 am, Bob12345 yuz...@gmail.com wrote: I figured out an easy workaround for WP7 WebBrowser: 1) Navigate to a local dummy page in your isolated storage before going to the oAuth page -- somehow this fixes the scrolling 2) Set the width of the 'auth' div to the width of your screen by invoking javascript on the browser-- this uncrowds the page. Wasted 2 days on this nonsense :( Thanks Bob for the workaround, not easy to implement but still a temporary solution. A better one would be that Twiter restores the page so we could migrate our application. Matthieu -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: New oAuth Authorization screen is unusable on phone webbrowser control
and the doc page for OOB authentication is not available : http://dev.twitter.com/pages/auth#oob Amateur hour here we come I'm going to ask for a xauth exception On May 1, 7:52 am, Bob12345 yuz...@gmail.com wrote: I figured out an easy workaround for WP7 WebBrowser: 1) Navigate to a local dummy page in your isolated storage before going to the oAuth page -- somehow this fixes the scrolling 2) Set the width of the 'auth' div to the width of your screen by invoking javascript on the browser-- this uncrowds the page. Wasted 2 days on this nonsense :( On Apr 30, 3:47 pm, Matthieu GD matthie...@gmail.com wrote: On Apr 30, 12:09 pm, Tom van der Woerdt i...@tvdw.eu wrote: I've heard this before. It sounds like all UIWebView, WebBrowser and probably Android's WebView are blocked. This is definitely a *good* thing for security reasons. They are not blocked, it's *only* a problem of layout. The workaround I recommend: launch the actual browser, using a yourapp:// link (something like myapplication://tokenDone) as the return URL. This is a LOT safer for the users. I have the same problem, and I don't see why using a webcontrol is a security problem. Since xauth is the exception, why twitter is making the use of oauth so hard ? Matthieu -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: New oAuth Authorization screen is unusable on phone webbrowser control
this message don't indicate any security concerns:
http://groups.google.com/group/twitter-api-announce/browse_thread/thread/3aac43cb45873232
On Apr 30, 7:13 pm, Tom van der Woerdt i...@tvdw.eu wrote:
On 5/1/11 12:47 AM, Matthieu GD wrote: On Apr 30, 12:09 pm, Tom van der
Woerdti...@tvdw.eu wrote:
I've heard this before.
It sounds like all UIWebView, WebBrowser and probably Android's WebView
are blocked. This is definitely a *good* thing for security reasons.
They are not blocked, it's *only* a problem of layout.
Are you sure? A block of CSS saying html { display: none; } doesn't
look like a problem, more like a feature. The workaround I recommend:
launch the actual browser, using a
yourapp:// link (something like myapplication://tokenDone) as the
return URL. This is a LOT safer for the users.
I have the same problem, and I don't see why using a webcontrol is a
security problem. Since xauth is the exception, why twitter is making
the use of oauth so hard ?
You should read the article athttp://goo.gl/xI0PZ
Tom
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: New oAuth Authorization screen is unusable on phone webbrowser control
On Apr 30, 7:18 pm, Ben Ward benw...@twitter.com wrote: Hi Bob, Tom, and others, On Apr 29, 2011, at 11:50 PM, Bob12345 wrote: I've been using a WebBrowser control in my Window Phone application to login into Twitter. Today I noticed that the login/authorization page format had changed and it is now unusable in a web browser control that my application displays. The text on the page is squeezed together, and the page unscrollable. I've seen a couple of reports of this concerning rendering in the current browser on Windows Phone 7. This is obviously unintended and I'm working on a fix. Thanks Ben for your message. Matthieu -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: New oAuth Authorization screen is unusable on phone webbrowser control
On May 3, 8:00 pm, LoungeFlyZ chrisfjohn...@gmail.com wrote: Hi Ben, Thanks for your reply about this issue. I am also seeing this in my Windows Phone 7 application. Something has changed in the last few days and now the page is rendering a little better but scrolling/panning/zooming isnt working i cant enter text in the username or password fields. Is there anything i can do to help diagnose this issue? Thanks, Chris. I have the same issue, I emailed to Ben a screenshot of the problem on my applicaion, Matthieu -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
