openid authentication in raindrop

[Shane Caraveo]

I've added openid authentication to the api server, it was very simple.
I'll be using repoze.who and possibly repoze.what as a part of
modifying pylons to work with a db/user. Once gozer and I work out a
few other issues, we'll nail down whether this is the defacto open id
support for raindrop.

You will need to install a new module by either running setup.py in
storm again, or:

easy_install repoze.who.plugins.openid

the root index file has links for login and logout, demo's will fail
ungracefully right now.

You can disable the openid auth by editing storm/development.ini and
changing handle_auth to false.

Shane

[Mark Hammond]

Cool!

On 7/08/2010 8:23 AM, Shane Caraveo wrote:
> the root index file has links for login and logout, demo's will fail
> ungracefully right now.
>
> You can disable the openid auth by editing storm/development.ini and
> changing handle_auth to false.

Should we disable this by default, at least until the demos and tests
all work "out of the box"? We should also consider disabling it by
default until Gozer says he wants it? I don't expect anyone running
raindrop locally will want it enabled by default, at least in the short
term...

(FWIW, I tried disabling it just in test.ini but that had no effect)

Cheers,

Mark

[Shane Caraveo]

On 10-08-06 5:34 PM, Mark Hammond wrote:
> Cool!
>
> On 7/08/2010 8:23 AM, Shane Caraveo wrote:
>> the root index file has links for login and logout, demo's will fail
>> ungracefully right now.
>>
>> You can disable the openid auth by editing storm/development.ini and
>> changing handle_auth to false.
>
> Should we disable this by default, at least until the demos and tests
> all work "out of the box"? We should also consider disabling it by
> default until Gozer says he wants it? I don't expect anyone running
> raindrop locally will want it enabled by default, at least in the short
> term...

we can for dev purposes. the demo's do work, so long as you're logged
in first. the account setup fails, I'll have to figure out how to work
with that.

> (FWIW, I tried disabling it just in test.ini but that had no effect)

comment out the line entirely, seems setting to false doesn't disable it.