<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: OAuth and Web2Py Part 1</title>
	<atom:link href="http://dougwarren.org/2010/06/oauth-and-web2py-part-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://dougwarren.org/2010/06/oauth-and-web2py-part-1/</link>
	<description>Ramblings Revisited</description>
	<lastBuildDate>Fri, 02 Dec 2011 07:43:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Tom</title>
		<link>http://dougwarren.org/2010/06/oauth-and-web2py-part-1/comment-page-1/#comment-7978</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 02 Dec 2011 07:43:58 +0000</pubDate>
		<guid isPermaLink="false">http://dougwarren.org/?p=28#comment-7978</guid>
		<description>Thanks for a fantastic walkthrough! 

Just implemented this on 12/2/2011 and it works. The only issue is that the request token url has changed. 
Was:
https://twitter.com/oauth/request_token
https://twitter.com/oauth/access_token
https://twitter.com/oauth/authorize
Change to:
https://api.twitter.com/oauth/request_token
https://api.twitter.com/oauth/access_token
https://api.twitter.com/oauth/authorize

appending api to the url fixes that. Otherwise, you&#039;ll get an error.</description>
		<content:encoded><![CDATA[<p>Thanks for a fantastic walkthrough! </p>
<p>Just implemented this on 12/2/2011 and it works. The only issue is that the request token url has changed.<br />
Was:<br />
<a href="https://twitter.com/oauth/request_token" rel="nofollow">https://twitter.com/oauth/request_token</a><br />
<a href="https://twitter.com/oauth/access_token" rel="nofollow">https://twitter.com/oauth/access_token</a><br />
<a href="https://twitter.com/oauth/authorize" rel="nofollow">https://twitter.com/oauth/authorize</a><br />
Change to:<br />
<a href="https://api.twitter.com/oauth/request_token" rel="nofollow">https://api.twitter.com/oauth/request_token</a><br />
<a href="https://api.twitter.com/oauth/access_token" rel="nofollow">https://api.twitter.com/oauth/access_token</a><br />
<a href="https://api.twitter.com/oauth/authorize" rel="nofollow">https://api.twitter.com/oauth/authorize</a></p>
<p>appending api to the url fixes that. Otherwise, you&#8217;ll get an error.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: albert</title>
		<link>http://dougwarren.org/2010/06/oauth-and-web2py-part-1/comment-page-1/#comment-6</link>
		<dc:creator>albert</dc:creator>
		<pubDate>Wed, 23 Jun 2010 17:36:35 +0000</pubDate>
		<guid isPermaLink="false">http://dougwarren.org/?p=28#comment-6</guid>
		<description>It worked. 

Just target the callback url to:
‘http://127.0.0.1:8000/twitter/default/callback’

Also, I imported Token, it wasn&#039;t imported.
-- from oauth2 import Client, Consumer
++ from oauth2 import Client, Consumer, Token

Thanks Doug</description>
		<content:encoded><![CDATA[<p>It worked. </p>
<p>Just target the callback url to:<br />
‘http://127.0.0.1:8000/twitter/default/callback’</p>
<p>Also, I imported Token, it wasn&#8217;t imported.<br />
&#8211; from oauth2 import Client, Consumer<br />
++ from oauth2 import Client, Consumer, Token</p>
<p>Thanks Doug</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Warren</title>
		<link>http://dougwarren.org/2010/06/oauth-and-web2py-part-1/comment-page-1/#comment-5</link>
		<dc:creator>Doug Warren</dc:creator>
		<pubDate>Wed, 23 Jun 2010 16:20:26 +0000</pubDate>
		<guid isPermaLink="false">http://dougwarren.org/?p=28#comment-5</guid>
		<description>The tutorial has you specifying a separate page for the callback &#039;http://127.0.0.1:8000/twitter/default/callback&#039; Now you don&#039;t actually need to do so, but if you do not, then you will need to move the logic that is in the callback() function into the index()  In fact, when I originally wrote this up, I had it as such.  I moved it to it&#039;s own callback to be more clear what was going on. Place everything in callback() other than the redirect at the start of index() and everything should work.</description>
		<content:encoded><![CDATA[<p>The tutorial has you specifying a separate page for the callback &#8216;<a href="http://127.0.0.1:8000/twitter/default/callback" rel="nofollow">http://127.0.0.1:8000/twitter/default/callback</a>&#8216; Now you don&#8217;t actually need to do so, but if you do not, then you will need to move the logic that is in the callback() function into the index()  In fact, when I originally wrote this up, I had it as such.  I moved it to it&#8217;s own callback to be more clear what was going on. Place everything in callback() other than the redirect at the start of index() and everything should work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: albert</title>
		<link>http://dougwarren.org/2010/06/oauth-and-web2py-part-1/comment-page-1/#comment-4</link>
		<dc:creator>albert</dc:creator>
		<pubDate>Wed, 23 Jun 2010 16:09:15 +0000</pubDate>
		<guid isPermaLink="false">http://dougwarren.org/?p=28#comment-4</guid>
		<description>Hi, I&#039;m trying it in local.
There&#039;s something that I&#039;m doing wrong, but I don&#039;t know what.

At twitter app, I configured all as urls: http://127.0.0.1:8000

At the moment, when I enter the app, it redirects me to twitter auth, when I accept, it&#039;s always on a loop answering me if I accept or cancel the auth.

I test it in a shell, and session.* doesn&#039;t have request_token and access_token.

I&#039;m lost! I need some light! 

Sorry my english. 
Thanks for the article.</description>
		<content:encoded><![CDATA[<p>Hi, I&#8217;m trying it in local.<br />
There&#8217;s something that I&#8217;m doing wrong, but I don&#8217;t know what.</p>
<p>At twitter app, I configured all as urls: <a href="http://127.0.0.1:8000" rel="nofollow">http://127.0.0.1:8000</a></p>
<p>At the moment, when I enter the app, it redirects me to twitter auth, when I accept, it&#8217;s always on a loop answering me if I accept or cancel the auth.</p>
<p>I test it in a shell, and session.* doesn&#8217;t have request_token and access_token.</p>
<p>I&#8217;m lost! I need some light! </p>
<p>Sorry my english.<br />
Thanks for the article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention OAuth and Web2Py Part 1 &#124; Doug's Ramblings -- Topsy.com</title>
		<link>http://dougwarren.org/2010/06/oauth-and-web2py-part-1/comment-page-1/#comment-2</link>
		<dc:creator>Tweets that mention OAuth and Web2Py Part 1 &#124; Doug's Ramblings -- Topsy.com</dc:creator>
		<pubDate>Mon, 21 Jun 2010 17:43:58 +0000</pubDate>
		<guid isPermaLink="false">http://dougwarren.org/?p=28#comment-2</guid>
		<description>[...] This post was mentioned on Twitter by Bruno Cezar Rocha, Doug Warren. Doug Warren said: #OAuth and #web2py tutorial using #twitter as an example http://dougwarren.org/2010/06/oauth-and-web2py-part-1/ [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Bruno Cezar Rocha, Doug Warren. Doug Warren said: #OAuth and #web2py tutorial using #twitter as an example <a href="http://dougwarren.org/2010/06/oauth-and-web2py-part-1/" rel="nofollow">http://dougwarren.org/2010/06/oauth-and-web2py-part-1/</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

