<?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: GMail and Google Calendar with OpenID and OAuth</title>
	<atom:link href="http://open.bekk.no/2009/12/18/gmail-and-google-calendar-with-openid-and-oauth/feed/" rel="self" type="application/rss+xml" />
	<link>http://open.bekk.no/2009/12/18/gmail-and-google-calendar-with-openid-and-oauth/</link>
	<description>Et innblikk i hva som skjer i BEKK</description>
	<lastBuildDate>Mon, 26 Jul 2010 10:03:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Thor Marius Henrichsen</title>
		<link>http://open.bekk.no/2009/12/18/gmail-and-google-calendar-with-openid-and-oauth/comment-page-1/#comment-191</link>
		<dc:creator>Thor Marius Henrichsen</dc:creator>
		<pubDate>Tue, 27 Apr 2010 13:55:48 +0000</pubDate>
		<guid isPermaLink="false">http://open.bekk.no/?p=2242#comment-191</guid>
		<description>@Antal: The code for doing OAuth is shared on GitHub. Checkout http://github.com/thormarius/oo for the code and http://oo-demo.heroku.com/ for an example on a live app that implements OpenID+OAuth  with GMail and calendar feed.</description>
		<content:encoded><![CDATA[<p>@Antal: The code for doing OAuth is shared on GitHub. Checkout <a href="http://github.com/thormarius/oo" rel="nofollow">http://github.com/thormarius/oo</a> for the code and <a href="http://oo-demo.heroku.com/" rel="nofollow">http://oo-demo.heroku.com/</a> for an example on a live app that implements OpenID+OAuth  with GMail and calendar feed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antal Kiss</title>
		<link>http://open.bekk.no/2009/12/18/gmail-and-google-calendar-with-openid-and-oauth/comment-page-1/#comment-190</link>
		<dc:creator>Antal Kiss</dc:creator>
		<pubDate>Thu, 22 Apr 2010 19:26:57 +0000</pubDate>
		<guid isPermaLink="false">http://open.bekk.no/?p=2242#comment-190</guid>
		<description>Hi there!
We just face the same problem, we can&#039;t implement the authorization process to the gmail feeds.

@Thor
Could you upload the code, how to implement the gmail feeds with the GApps accounts?
thanks</description>
		<content:encoded><![CDATA[<p>Hi there!<br />
We just face the same problem, we can&#8217;t implement the authorization process to the gmail feeds.</p>
<p>@Thor<br />
Could you upload the code, how to implement the gmail feeds with the GApps accounts?<br />
thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thor Marius Henrichsen</title>
		<link>http://open.bekk.no/2009/12/18/gmail-and-google-calendar-with-openid-and-oauth/comment-page-1/#comment-162</link>
		<dc:creator>Thor Marius Henrichsen</dc:creator>
		<pubDate>Fri, 19 Feb 2010 09:01:24 +0000</pubDate>
		<guid isPermaLink="false">http://open.bekk.no/?p=2242#comment-162</guid>
		<description>@Shyam

We have actually implemented this with a GApps account. It&#039;s a while since we did this now, so I don&#039;t remember all the nitty gritty details. What I do remember is that we had the same problem until we figured out that we had to publish a xrds document at http://example.com/openid in order for the discovery to work.  Google will access this URL in the openid discovery process.  

There&#039;s also something about a host-meta document that should be hosted on http://example.com/.well-known/host-meta, but I don&#039;t remember if the latter is really neccessary. 


Checkout http://nith.no/openid and http://nith.no/.well-known/host-meta for an example on how we did it.</description>
		<content:encoded><![CDATA[<p>@Shyam</p>
<p>We have actually implemented this with a GApps account. It&#8217;s a while since we did this now, so I don&#8217;t remember all the nitty gritty details. What I do remember is that we had the same problem until we figured out that we had to publish a xrds document at <a href="http://example.com/openid" rel="nofollow">http://example.com/openid</a> in order for the discovery to work.  Google will access this URL in the openid discovery process.  </p>
<p>There&#8217;s also something about a host-meta document that should be hosted on <a href="http://example.com/.well-known/host-meta" rel="nofollow">http://example.com/.well-known/host-meta</a>, but I don&#8217;t remember if the latter is really neccessary. </p>
<p>Checkout <a href="http://nith.no/openid" rel="nofollow">http://nith.no/openid</a> and <a href="http://nith.no/.well-known/host-meta" rel="nofollow">http://nith.no/.well-known/host-meta</a> for an example on how we did it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shyam Krishna Khadka</title>
		<link>http://open.bekk.no/2009/12/18/gmail-and-google-calendar-with-openid-and-oauth/comment-page-1/#comment-151</link>
		<dc:creator>Shyam Krishna Khadka</dc:creator>
		<pubDate>Tue, 09 Feb 2010 03:01:44 +0000</pubDate>
		<guid isPermaLink="false">http://open.bekk.no/?p=2242#comment-151</guid>
		<description>No I couldn&#039;t find a way so that open Id authentication gets successful with google apps accout.
I changed IDENTITY URL to &quot;https://www.google.com/accounts/o8/site-xrds?hd=mydomain.com&quot; which redirects user to Google Apps login page instead of Google login page and goes for OAuth process as in step #3 of above example.But when I click allow button,It says open Id Authentication failed.
Any ideas????</description>
		<content:encoded><![CDATA[<p>No I couldn&#8217;t find a way so that open Id authentication gets successful with google apps accout.<br />
I changed IDENTITY URL to &#8220;https://www.google.com/accounts/o8/site-xrds?hd=mydomain.com&#8221; which redirects user to Google Apps login page instead of Google login page and goes for OAuth process as in step #3 of above example.But when I click allow button,It says open Id Authentication failed.<br />
Any ideas????</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aslak Hellesøy</title>
		<link>http://open.bekk.no/2009/12/18/gmail-and-google-calendar-with-openid-and-oauth/comment-page-1/#comment-150</link>
		<dc:creator>Aslak Hellesøy</dc:creator>
		<pubDate>Mon, 08 Feb 2010 13:17:17 +0000</pubDate>
		<guid isPermaLink="false">http://open.bekk.no/?p=2242#comment-150</guid>
		<description>Shyam,

I haven&#039;t tested if use you Google Apps credentials to log into a site that uses Google as OpenID provider. I would think you can. If you have a Google Apps account you can try it out with our demo app.</description>
		<content:encoded><![CDATA[<p>Shyam,</p>
<p>I haven&#8217;t tested if use you Google Apps credentials to log into a site that uses Google as OpenID provider. I would think you can. If you have a Google Apps account you can try it out with our demo app.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shyam Krishna Khadka</title>
		<link>http://open.bekk.no/2009/12/18/gmail-and-google-calendar-with-openid-and-oauth/comment-page-1/#comment-149</link>
		<dc:creator>Shyam Krishna Khadka</dc:creator>
		<pubDate>Fri, 05 Feb 2010 10:57:29 +0000</pubDate>
		<guid isPermaLink="false">http://open.bekk.no/?p=2242#comment-149</guid>
		<description>Thanks for nice article.
But I wonder if there is a way so that users can login with their Google Apps account as well using Open ID + OAuth as in your example.
Any suggestions are highly welcomed!!</description>
		<content:encoded><![CDATA[<p>Thanks for nice article.<br />
But I wonder if there is a way so that users can login with their Google Apps account as well using Open ID + OAuth as in your example.<br />
Any suggestions are highly welcomed!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aslak Hellesøy</title>
		<link>http://open.bekk.no/2009/12/18/gmail-and-google-calendar-with-openid-and-oauth/comment-page-1/#comment-124</link>
		<dc:creator>Aslak Hellesøy</dc:creator>
		<pubDate>Thu, 14 Jan 2010 16:07:48 +0000</pubDate>
		<guid isPermaLink="false">http://open.bekk.no/?p=2242#comment-124</guid>
		<description>Thanks Rune. I&#039;ll try this out the next time I use OAuth. You&#039;re right that it might be a hybrid protocol thing - I haven&#039;t really tried OAuth against any other OAuth providers.</description>
		<content:encoded><![CDATA[<p>Thanks Rune. I&#8217;ll try this out the next time I use OAuth. You&#8217;re right that it might be a hybrid protocol thing &#8211; I haven&#8217;t really tried OAuth against any other OAuth providers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rune Botten</title>
		<link>http://open.bekk.no/2009/12/18/gmail-and-google-calendar-with-openid-and-oauth/comment-page-1/#comment-121</link>
		<dc:creator>Rune Botten</dc:creator>
		<pubDate>Wed, 13 Jan 2010 10:29:50 +0000</pubDate>
		<guid isPermaLink="false">http://open.bekk.no/?p=2242#comment-121</guid>
		<description>I dont think you&#039;re absolutely right about the OAuth consumer secret being tied to the registered domain, it can be used from localhost. It is tied to the registered domain in the sense that you can only redirect to that domain after authorization at Google. In that redirect is an oauth_verifier get-param which you need for swapping an authorized request token for an access token.

Once you have that access token though, you can use it locally. I just confirmed this in IRB locally doing YouTube Data API requests with an access token, after copy-pasting the oauth_verifier from the Google redirect to my registered Heroku domain. The request token was created and swapped for an access token locally. If you plug something like Mechanize in there to authorize at Google and get the verifier from the redirect, you&#039;d have at least the OAuth thing going for you locally.

The hybrid protocol might be a whole other thing.

I wrote a blog post on Ruby, OAuth and YouTube which should supply the needed info, http://runerb.com/2010/01/12/ruby-oauth-youtube.</description>
		<content:encoded><![CDATA[<p>I dont think you&#8217;re absolutely right about the OAuth consumer secret being tied to the registered domain, it can be used from localhost. It is tied to the registered domain in the sense that you can only redirect to that domain after authorization at Google. In that redirect is an oauth_verifier get-param which you need for swapping an authorized request token for an access token.</p>
<p>Once you have that access token though, you can use it locally. I just confirmed this in IRB locally doing YouTube Data API requests with an access token, after copy-pasting the oauth_verifier from the Google redirect to my registered Heroku domain. The request token was created and swapped for an access token locally. If you plug something like Mechanize in there to authorize at Google and get the verifier from the redirect, you&#8217;d have at least the OAuth thing going for you locally.</p>
<p>The hybrid protocol might be a whole other thing.</p>
<p>I wrote a blog post on Ruby, OAuth and YouTube which should supply the needed info, <a href="http://runerb.com/2010/01/12/ruby-oauth-youtube" rel="nofollow">http://runerb.com/2010/01/12/ruby-oauth-youtube</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shyam  krishna  khadka</title>
		<link>http://open.bekk.no/2009/12/18/gmail-and-google-calendar-with-openid-and-oauth/comment-page-1/#comment-115</link>
		<dc:creator>shyam  krishna  khadka</dc:creator>
		<pubDate>Wed, 06 Jan 2010 02:58:53 +0000</pubDate>
		<guid isPermaLink="false">http://open.bekk.no/?p=2242#comment-115</guid>
		<description>Sorry i couldn&#039;t find any way to work with localhost.
I tried with several options but it didn&#039;t work for me with reference to this documentation http://code.google.com/apis/accounts/docs/OAuth_ref.html#SigningOAuth
Instead i deployed the application and made hybrid protocol work.</description>
		<content:encoded><![CDATA[<p>Sorry i couldn&#8217;t find any way to work with localhost.<br />
I tried with several options but it didn&#8217;t work for me with reference to this documentation <a href="http://code.google.com/apis/accounts/docs/OAuth_ref.html#SigningOAuth" rel="nofollow">http://code.google.com/apis/accounts/docs/OAuth_ref.html#SigningOAuth</a><br />
Instead i deployed the application and made hybrid protocol work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thor Marius Henrichsen</title>
		<link>http://open.bekk.no/2009/12/18/gmail-and-google-calendar-with-openid-and-oauth/comment-page-1/#comment-114</link>
		<dc:creator>Thor Marius Henrichsen</dc:creator>
		<pubDate>Tue, 05 Jan 2010 07:11:16 +0000</pubDate>
		<guid isPermaLink="false">http://open.bekk.no/?p=2242#comment-114</guid>
		<description>@shyam: There might be a way of making it work from localhost, but we did not figure out how to accomplish this. It seems like the oauth secret key is bound to the domain making the oauth request. Instead we deployed our app to Heroku so that we could easily develop - deploy - run the application in a short cycle.  

If you find a way to make the hybrid protocol work from localhost please let us know!</description>
		<content:encoded><![CDATA[<p>@shyam: There might be a way of making it work from localhost, but we did not figure out how to accomplish this. It seems like the oauth secret key is bound to the domain making the oauth request. Instead we deployed our app to Heroku so that we could easily develop &#8211; deploy &#8211; run the application in a short cycle.  </p>
<p>If you find a way to make the hybrid protocol work from localhost please let us know!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
