Re: [Snowy] OAuth in Snowy



Stuart,

Thanks for all your help with this.  I just pushed these patches with
some additional fixes, including support for the Root resource.  For
Tomboy, I pushed changes that require all this new OAuth stuff.  It
works for me.

Interoperability issues:
* Tomboy expects the OAuth authentication realm to be "Snowy" (see
recent email to list)
* Tomboy sets the consumer key to abcdefg and the secret to 1234567
(both should be empty or some other sentinel value, as discussed
previous in this thread)
* I have not tested with HTTPS (Tomboy may need additional updates for that)
* Tomboy hard-codes the oauth_callback URL to http://www.google.com
(very useful, I know)

Snowy issues:
* You must now set DOMAIN_NAME in local_settings.py
* Very sensitive about URLs...very unhappy if I used 127.0.0.1 instead
of localhost in my Authenticate URL
* Threw an error when bringing up the Authenticate URL without being
logged in (presumably a common situation)
* Requires an oauth_callback URL (we should make a good default one instead)
* Snowy hard-codes URLs returned from the API to be HTTP (maybe the
easy fix would be to just add that to what the user sets in
DOMAIN_NAME?)

Tomboy issues:
* Prefs UI is kind of hacky (it's a rip from Tasque's RTM prefs GUI).
Enter your base URL (whatever shows up *before* /oauth*, /api*, etc),
click the giant button, submit the form in your browser, click the
giant button again, click Save, start syncing).
* If you have hundreds of notes, sync may fail with an error in the
log about a collection changing during enumeration. I'm working on
this...it's not at all related to this work, except that if you're
testing initial sync a lot you may run into it.

Now that we have a baseline for this stuff upstream, patch review/push
turn-around time should speed up considerably.

Thanks for your patience,
Sandy

On Fri, Jun 5, 2009 at 3:26 AM, Stuart
Langridge<stuart langridge canonical com> wrote:
> OK, I've added OAuth support to Snowy. OAuth endpoints are at
> /oauth/{request_token,authenticate,access_token} and everything under
> api/ now requires OAuth (and does not work with basic auth). Two patches
> attached.
>
> I had to patch piston; the piston patches are required for OAuth support
> to actually work, and are taken from
> http://bitbucket.org/ephelon/django-piston/changeset/a7f81eae936c/ in
> consultation with jespern (who hasn't yet merged these patches upstream).
>
> Your comments invited. :-)
>
> sil
>
> _______________________________________________
> Snowy-list mailing list
> Snowy-list gnome org
> http://mail.gnome.org/mailman/listinfo/snowy-list
>
>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]