On Thu, 2011-06-30 at 13:45 -0400, Matthew Barnes wrote:
On Fri, 2011-06-10 at 17:02 +0100, Philip Withnall wrote:
On Thu, 2011-06-09 at 17:24 -0400, Matthew Barnes wrote:
Google Calendars have me stumped, however, since we defer to our
standard CalDAV backend which authenticates with
On Thu, 2011-06-30 at 18:34 +, Philip Withnall wrote:
That's a neat idea. Perhaps it would be worthwhile putting this in
libsoup proper so that we have a common place for OAuth implementations.
It does seem to be the right place.
Once I can verify that it actually works I'll see if Dan's
On 30 June 2011 19:45, Matthew Barnes mbar...@redhat.com wrote:
Once I can verify that it actually works I'll see if Dan's interested,
although he did point me to librest, which is libsoup-based and provides
more complete OAuth support than my little hack.
On Fri, 2011-06-10 at 17:02 +0100, Philip Withnall wrote:
On Thu, 2011-06-09 at 17:24 -0400, Matthew Barnes wrote:
On Thu, 2011-06-09 at 21:56 +0100, Philip Withnall wrote:
I guess this involves updating the Google Contacts address book backend
to use GOA's OAuth 1.0 magic. I've recently
On Thu, 2011-06-09 at 17:24 -0400, Matthew Barnes wrote:
On Thu, 2011-06-09 at 21:56 +0100, Philip Withnall wrote:
I guess this involves updating the Google Contacts address book backend
to use GOA's OAuth 1.0 magic. I've recently updated libgdata to be able
to cope with OAuth, and I've got
On Thu, 2011-06-09 at 17:24 -0400, Matthew Barnes wrote:
Google Calendars have me stumped, however, since we defer to our
standard CalDAV backend which authenticates with stored passwords from
the keyring. I'm not sure how to slip in OAuth integration for this
one special case.
Hi,
I
