Defect #3780
Attribute exchange with OpenID providers
| Status: | New | Start date: | 2009-08-25 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 100% | |
| Category: | OpenID | |||
| Target version: | - | |||
| Affected version: | Resolution: |
Description
Redmine should "include the attribute exchange parameters to authentication requests to access user information (such as name and email)" (quote: Google OpenID documentation), and i think this not what our OpenID implementation does now. As of r2847 , the attribute exchange doesnt work with Google accounts (this id the only provider i tried), and i think this is a major usability issue with the recent state of OpenID support.
Related issues
History
#1 Updated by Stas SUSHKOV over 3 years ago
The OpenID support as it is now is useless.
Please provide a way to define the required user details or enable only the bare basic openid support (just to allow a user to log in).
I would also rise the priority for this issue, though, hope it won't take months to be solved.
Thank you in advance.
#2 Updated by Tom S over 3 years ago
+1
#3 Updated by Stas SUSHKOV over 3 years ago
- Status changed from New to Resolved
Here's a work around (dirty, lazy hack) which works for us with Launchpad's, WordPress's, Yahoo's OpenID.
Patch here: http://gist.github.com/179159
#4 Updated by Jean-Philippe Lang over 3 years ago
- Assignee set to Eric Davis
#5 Updated by Alex Munroe about 3 years ago
+1 -- the patch is about the same hack I made, but seeing something more robust built in would be nice.
#6 Updated by Stas SUSHKOV almost 3 years ago
Bump!
And soon we make an year.
#7 Updated by Eric Davis almost 3 years ago
- Status changed from Resolved to New
- Assignee deleted (
Eric Davis)
Stas:
Redmine is developed by a group of volunteers. This hasn't been a high priority feature, which might be why no one has contributed their free time to build a more robust system for this.
#8 Updated by Stas SUSHKOV almost 3 years ago
Since this is important for me, I might consider spending some time/$ for coding/testing, if you could guide me what exactly is to be expected from existing patch/features making it a possible fix.
I agree with you and I know what volunteering means, but this was more like an ignorance.
#9 Updated by Stas SUSHKOV almost 3 years ago
Thank you.
#10 Updated by M B over 2 years ago
+1
#11 Updated by Ladislav Nesnera over 2 years ago
- File redmineOpenID.png added
Is there any progress in this case or I have some wrong settings? This doesn't look very well ;?(
Redmine 1.0.3.stable.4425 (MySQL)
#12 Updated by Toshi MARUYAMA about 2 years ago
- Category set to Accounts / authentication
#13 Updated by Etienne Massip over 1 year ago
- Category changed from Accounts / authentication to OpenID
#14 Updated by Antoine Beaupré over 1 year ago
- % Done changed from 0 to 100
there is a fix for this: http://projects.andriylesyuk.com/projects/openid-fix
why isn't this factored in?!
#15 Updated by Andrew Dahl 5 months ago
Antoine Beaupré wrote:
there is a fix for this: http://projects.andriylesyuk.com/projects/openid-fix
why isn't this factored in?!
I don't see the fix you refer to, Antoine. (Although, it could have been removed in the last year.) The only changes I see are in the repository and they involve allowing manual versus on-the-fly creation of users upon login, which Redmine provides currently and doesn't solve the problem this ticket identifies.
As this is relevant, I posted a patch here => http://www.redmine.org/issues/11778 <= that handles AX (Attributes Exchange) and works to auto-register users on Google and Yahoo (and probably others, but I only tested those two). I provide it more as an example of what needs to be done, but if it were to be pulled in, it does work better than the current implementation.
As well, if you like what you see and would like me to test & verify it across several OpenID providers (not just Google & Yahoo) and modify the code to include additional AX attributes as necessary, I can definitely do that and repost!
#16 Updated by Antoine Beaupré 2 months ago
Direct ref to an issue with a patch: #11778.