http://code.google.com/p/oauth-dot-net/

Paul


On May 28, 11:36 am, "Paul (Google)" <[email protected]> wrote:
> Great find, Karthik.  Thanks for posting it in the forum!  That's the
> great thing about an open standard; lots of choices for libraries!
>
> I also ran across an oauth-dot-net project (link below) that has a
> Google Contacts example.  I haven't been able to verify that it uses 3-
> legged OAuth, but it might also be a good API to investigate.
>
> Paul
>
> On May 27, 7:26 pm, karthik mellachervu <[email protected]> wrote:
>
>
>
> > Hi Paul,
>
> > last week i am looking for that in the google then i found this information
> > which i thought useful so i am sharing here.
>
> > A third party application which used the oAuth to connect to the Google
> > AddressBook which is also given the implementation of the oAuth in Google.
> > Download the Source code fromhttp://www.dotnetopenauth.net/. It has some
> > sample applications at *
> > DotNetOpenAuth-3.4.3.10103\DotNetOpenAuth-3.4.3.10103\Samples\OAuthConsumer 
> > \GoogleAddressBook.aspx,
> > which
> > used the OAuth to connect Google Address book.*
> > * *
> > Thanks,
> > Karthik M
>
> > On Thu, May 27, 2010 at 10:07 PM, Paul (Google) <[email protected]> wrote:
> > > Hi Karthik,
>
> > > You will want to use 3-Legged OAuth for connecting to Health.  I sent
> > > the 2-legged example since it had some .NET code that you could
> > > potentially start with.  Although, it would certainly need to be
> > > tweaked for 3-legged OAuth, which is possible according to the
> > > following thread:
>
> > >http://www.google.com/support/forum/p/apps-apis/thread?tid=41a622a18e...
>
> > > Unfortunately, I've yet to track down a 3-legged example at Google.  I
> > > will keep looking, however.
>
> > > If you find a good example in the meantime, please be sure to post it
> > > here!
>
> > > Paul
>
> > > On May 27, 2:40 pm, karthik mellachervu <[email protected]> wrote:
> > > > Hi Paul,
>
> > > > Thanks for th Response.
>
> > > > I have gone through all the Links which you have provided.I Have seen
> > > that
> > > > you provided thatwe can connect to gHealth using the 2-legged OAuth but 
> > > > i
> > > > want to know how we can acheive this using the 3-Legged.I didnt see any
> > > > samples for this?
>
> > > > I am not able to find the classes,methods etc to implement the 3-legged
> > > > OAuth in the Documentation provided by Google Data API.
>
> > > > Could you please guide me or provide me the References or samples to
> > > > implement the 3-legged OAuth.
>
> > > > The PlayGround is a very nice tool which is very useful for the
> > > Developers.
>
> > > > MK
> > > > MK
>
> > > > On Mon, May 24, 2010 at 8:30 PM, Paul (Google) <[email protected]> wrote:
> > > > > Hello Karthik,
>
> > > > > OAuth authentication to Health is certainly possible.  The following
> > > > > link is for the OAuth+Health documentation:
>
> > > > >http://code.google.com/apis/health/docs/2.0/developers_guide_protocol.
> > > ..
>
> > > > > Since the Health feeds are built using the GData, the following is
> > > > > another good reference, which includes .NET examples:
>
> > > > >http://code.google.com/apis/gdata/docs/auth/oauth.html#2LeggedOAuth
>
> > > > > You may also want to try the OAuth Playground, which has a working
> > > > > example of OAuth and Health (not .NET however).
>
> > > > >http://googlecodesamples.com/oauth_playground/
>
> > > > > Cheers!
>
> > > > > Paul (Google)
>
> > > > > On May 19, 6:37 pm, karthik mellachervu <[email protected]> wrote:
> > > > > > Hi,
>
> > > > > > I want to know wheather i can connect to gHealth using oAuth
> > > > > > authentication either using 3-legged or 2-legged.Please provide the
> > > > > > useful information(any links) for this?
>
> > > > > > I am creating a application in .NET.
>
> > > > > > Thanks,
> > > > > > Karthik M
>
> > > > > > --
> > > > > > You received this message because you are subscribed to the Google
> > > Groups
> > > > > "Google Health Developers" group.
> > > > > > To post to this group, send email to
> > > > > [email protected].
> > > > > > To unsubscribe from this group, send email to
> > > > > [email protected]<googlehealthdevelopers%
> > > > >  [email protected]><googlehealthdevelopers%
> > > [email protected]>
> > > > > .
> > > > > > For more options, visit this group athttp://
> > > > > groups.google.com/group/googlehealthdevelopers?hl=en.
>
> > > > > --
> > > > > You received this message because you are subscribed to the Google
> > > Groups
> > > > > "Google Health Developers" group.
> > > > > To post to this group, send email to
> > > > > [email protected].
> > > > > To unsubscribe from this group, send email to
> > > > > [email protected]<googlehealthdevelopers%
> > > > >  [email protected]><googlehealthdevelopers%
> > > [email protected]>
> > > > > .
> > > > > For more options, visit this group at
> > > > >http://groups.google.com/group/googlehealthdevelopers?hl=en.
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "Google Health Developers" group.
> > > To post to this group, send email to
> > > [email protected].
> > > To unsubscribe from this group, send email to
> > > [email protected]<googlehealthdevelopers%
> > >  [email protected]>
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/googlehealthdevelopers?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Health Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/googlehealthdevelopers?hl=en.

Reply via email to