#4722 closed enhancement (wontfix)
OpenID to Trac system
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | |
Severity: | normal | Keywords: | authentication consider |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
Hi, I think OpenID verification is better than local Trac accounting. Because lots of site which uses trac, has different user accounting. And for applying a bug, its bad to open a new account.
With OpenID, users can use their OpenID count to verify it's ID. Please look at new technology at.
See also: http://openid.net
Attachments (1)
Change History (19)
comment:1 by , 18 years ago
Keywords: | authentication added |
---|
comment:2 by , 18 years ago
Description: | modified (diff) |
---|---|
Keywords: | consider added |
Milestone: | → 2.0 |
comment:4 by , 15 years ago
This would be a good default setting for just about all open source projects. I support this. I hate having to sign up to every damn project I want to submit a bug report to.
comment:5 by , 15 years ago
Well, another problem with OpenID is that it is web/browser only. It will not be supported as a user id when using a Subversion client and other VCS clients for instance, so a separate user management system is needed anyway. At best it can be an additional option for 'ad-hoc visitors', but I don't really see it being a default in core.
comment:6 by , 15 years ago
I have to say I really support the idea of a Trac OpenID plugin, in the core would be better as a built in option. For me the reason would be, the single biggest reason why OSS users don't bother submitting bug reports on bug tracking systems like Trac, Bugzilla etc is the fact that they have to create a new account for every different bug tracking installation out there. Simply most just aren't bothered creating an account for a system they might only come back to a few times ever. This propagates the problem of people using the same user name and password on every account system that they are forced to login to, which is of course bad security.
At least if users could quickly and easily login with their OpenID, they might be more inclined to submit more bug reports. It would be a case of set it and forget it, not having to remember which user name and password they chose for any given site.
comment:7 by , 15 years ago
The TracAuthOpenId:
seems to be very nicely written and quite feature rich, please give it a try and report back.
comment:8 by , 15 years ago
Yes OpenID is great. No need to remember a lot of things any more. You even get on your OpenID server, a list of URLs you subscribed to.
Nice to see you've done it. But why then did I not find OpenID on http://trac.transmissionbt.com/register? I wanted to tell them something interesting but my subscription quota is over 100.
Please effectively install OpenID on Trac sites. Thanks.
follow-up: 11 comment:10 by , 14 years ago
Milestone: | triaging |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
authopenid-plugin seems to be working and maintained, so I'm closing this ticket.
comment:11 by , 14 years ago
Replying to rblank:
authopenid-plugin seems to be working and maintained, so I'm closing this ticket.
Please, note that this plugin works with Trac 0.11 version only. Later versions might work as well but I personally will not support them since I don't use Trac anymore myself.
follow-up: 13 comment:12 by , 14 years ago
Please reconsider this. The AuthOpenID plugin is shoddy and incomplete. For example, the username of users logged in with OpenID shows up as the OpenID URL. Completely unacceptable.
comment:13 by , 14 years ago
Replying to ShiningMasamune:
Please reconsider this. The AuthOpenID plugin is shoddy and incomplete. For example, the username of users logged in with OpenID shows up as the OpenID URL. Completely unacceptable.
Looking at the plugin, it seems to be all but shoddy and incomplete… Furthermore, the login name only shows the OpenID URL in addition to the full name if you have the [openid] combined_username
, otherwise it's the full name alone, with care taken of avoiding duplicates (see also discussion in https://bitbucket.org/Dalius/authopenid-plugin/issue/15/username-generation).
I don't see how by making the functionality builtin this could get any better.
Of course, if the plugin's author see some changes we could do in Trac that could help improve the plugin (I'm referring to The main problem with trac is that user name and display name are not clearly separated in the ticket above), we're all ears. I think in particular about #7339 and #3737, but granted those are perhaps not easy to fix in a satisfying way without making deeper changes (#2456, #1890).
comment:14 by , 14 years ago
Please excuse my earlier post. I was using the version in the Ubuntu repositories, which is apparently VERY outdated. Strangely, this outdated version seems to be in use on a number of websites… Anyway, I built the most recent version from the source, and it has turned out to be more than sufficient. Silly me, what I was thinking expecting Ubuntu repos to be up-to-date!
Apologies to the plugin author.
follow-up: 16 comment:15 by , 14 years ago
Hi, I'm using the authopenid-plugin and I'm very satisfied with it. Unfortunately it doesn't work with Trac 0.12 (I tested). The original author states:
This plugins allows to login to Trac using OpenID. Please, note that this plugin works with Trac 0.11 version only. Later versions might work as well but I personally will not support them since I don't use Trac anymore myself.
I'd be a pity if the plugin would be discontinued in later versions of Trac. I'd appreciate if someone could port the plugin to 0.12.
follow-up: 17 comment:16 by , 14 years ago
Replying to Petr P.:
… I'd be a pity if the plugin would be discontinued in later versions of Trac. I'd appreciate if someone could port the plugin to 0.12.
Exactly. And what about that someone being you? That's how open source works, people who need the software are the one who make it live.
Note that I doubt the adaptations needed are that hard to do, the changes that happened between 0.11 and 0.12 are well documented (TracDev/ApiChanges/0.12). If that's not enough, you're welcome to ask specific questions on Trac-dev.
comment:17 by , 14 years ago
Replying to cboos:
Replying to Petr P.:
… I'd be a pity if the plugin would be discontinued in later versions of Trac. I'd appreciate if someone could port the plugin to 0.12.
Exactly. And what about that someone being you? That's how open source works, people who need the software are the one who make it live.
Sure I was thinking about it. But I've never used Python for something larger than a few lines of code and at this time I have no spare time to start learning the language and TRAC internals :-(. I suppose might have a look at it in a couple of months, when I hope I'll have more time.
Note that I doubt the adaptations needed are that hard to do, the changes that happened between 0.11 and 0.12 are well documented (TracDev/ApiChanges/0.12). If that's not enough, you're welcome to ask specific questions on Trac-dev.
Thanks for the pointers.
comment:18 by , 14 years ago
Hi,
I've just set up a patch against release 3.3 to support trac 0.12. But I'm unable to test it at the moment. I'd appreciate if anyone could give it a review: http://pastebin.com/EmHShgSx (also attached).
Many thanks in advance!
by , 14 years ago
Attachment: | authopenid-for-trac-0.12.patch added |
---|
This could be nice on trac.edgewall.org
However, this cannot be implemented in Trac core, but as a plugin: this kind of authentication would not work on a private network, for example - as long as the private network cannot access an OpenID server.
I'm not sure whether this ticket should be closed or not, as it could be nice to have the OpenID feature on t.e.o.