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.
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.net only" 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@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/clo-devel
Hi Daniel,
On Tue, Aug 16, 2011 at 12:57 PM, ehuels@gmail.com ehuels@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@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/clo-devel
16.08.2011, 23:19, "Erik Huelsmann" ehuels@gmail.com:
Reading https://bitbucket.org/Dalius/authopenid-plugin/wiki/Home%C2%A0I 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.
Another option is to tweak the trac openid plugin by few python lines so that the OpenID-to-local mapping may be stored in the trac.ini.
Some new trac.ini option:
[openid] # Key-value list of OpenID to local Trac account mapping. openid_to_local = <openid1>:<username1>;<openid2>:<username2>
And in in the plugin sources - https://bitbucket.org/Dalius/authopenid-plugin/src/65c4d2c474d9/authopenid/a...:
Around the line 149:
openid_to_local = Option('openid', 'openid_to_local', None, """ Key-value list of OpenID to local Trac account mapping.""")
Arount the line 532:
if allowed and and self.openid_to_local: new_user = parse_somehow_to_map(self.openid_to_local)[remote_user] if new_user: remote_user = new_user
The format of key-value list may be chosen depending what is easier to parse (maybe even a literal to execute with python's eval, or maybe json to parse with simple json, etc.).
A question: what are the benefits of translating OpenID to a local account?
As far as I understand, the trac account are only valid for trac and have nothing to do with the common-lisp.net user account. So if we use OpenID to login to trac, the only advantage is that I will see all the information (tickets) already assigned to my old trac name as assigned to me logged-in with OpenID. No other benefits?
If so, it is only useful for existing projects, new projects can use OpenID from the beginning?
I also curious how trac accounts are created. As far as I understand, trac instance for every cl-net project is a separate application, with it's own database (in the <project dir>/trac/db/), right? Do you have a script which scans <user home>/trac-info.txt and populates trac databases of all the trac instances on common-lisp.net?
Best regards, - Anton
-
Anton Vodonosov -
ehuels＠gmail.com -
Erik Huelsmann