[clo-devel] Using Google accounts for Trac access?

[Erik Huelsmann]

Hi Daniel,

On Tue, Aug 16, 2011 at 12:57 PM, ehuels at gmail.com <ehuels at gmail.com> wrote:

> Hi Daniel,
>
> Yesterday, I enabled OpenID on the armedbear project. trac now simply
> offers 2 login links: 1 for local account and one for openid. i haven't
> discovered how to associate the two yet.
>

Reading https://bitbucket.org/Dalius/authopenid-plugin/wiki/Home I conclude
we should be able to provide a mapping service to the OpenID module which
maps openIDs to internal user accounts. My idea would be to allow users to
create an .openid file in their home directories; these files could be
concatenated by the mapping service on every request when the cache is older
than 15 minutes - or something alike.

All we need now is someone to develop the service.


Bye,

Erik.


Bye,
>
> Erik.
>
>
> Sent from my Nokia phone
> -----Original Message-----
> From: Daniel Herring
> Sent:  16/08/2011, 03:40
> To:
> Subject: Re: [clo-devel] Using Google accounts for Trac access?
>
>
> On Mon, 15 Aug 2011, Erik Huelsmann wrote:
>
> > When I saw it's now possible to log in to SourceForge using your Google
> Account, I thought it's a nice way to open up our Trac wikis and bug
> trackers to a broader public than the current "account holders of c-l.netonly" policy.
> > From what I can tell, Google offers OAuth/OpenID user authentication. As
> far as I can tell, there's an OpenID plugin available for Trac 0.11 (our
> version). Is that good enough for us?
> >
> > As far as I'm aware, we have that policy to prevent spam bots from
> logging in and destroying wiki content.  Would a relaxation be all right?
>
> Assuming it doesn't increase the spam load, I'd prefer using OpenID to
> creating a local trac account.
>
> Curious whether OpenID accounts could be associated with local accounts as
> a bonus feature.
>
> - Daniel
> _______________________________________________
> clo-devel mailing list
> clo-devel at common-lisp.net
> http://lists.common-lisp.net/cgi-bin/mailman/listinfo/clo-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/clo-devel/attachments/20110816/4285845e/attachment.html>