Well my mail set up has changed and (unfortunately) I'm no longer on 
Horde.  I'm ashamed to admit I actually don't remember what prompted 
me to request this feature, so if I was the only requester, it's 
probably safe to drop this for now.

That said, I'm not sure I agree with most of the points in the most 
recently linked article.  This bug report may not be the best place 
for a rebuttal, but here goes:

1. The argument that OpenID solves a non-existent problem is poorly 
made, especially in the context of email.  Half of the proposed 
workarounds are essentially: don't use the site if you don't feel like 
registering.  The other half are: spend 5 minutes registering and use 
some 3rd mechanism to remember your login.

2. The irony-of-OpenID argument is tired. Yes, you need one additional 
registration to save potentially dozens of future registrations. Yes. 
you can make it sound ridiculous if you entirely neglect the second 
half of that statement, as many people have done since day 1.

3. Really the only valid criticism is that using a URL as an ID is 
confusing to end users.  This is an education/familiarity issue.  Any 
*developer* unable to grasp the OpenID credential exchange should not 
be handling my data.  :)  And I doubt Horde ever wants to implement a 
Facebook-dependent solution or cave to the argument that "no one 
really cares about security anyways."

So to summarize, I don't need a third-party login feature any more, 
but if Horde were to implement such a thing, I still think OpenID is 
the way to go. :)

I think we may have outlasted this one. See 
http://www.25hoursaday.com/weblog/2011/01/30/LearningFromOurMistakesTheFailureOfOpenIDAtomPubAndXMLOnTheWeb.aspx, and the writeups linked from 
there.

http://googlecode.blogspot.com/2010/11/googles-sample-openid-relying-party.html

Thanks for the recommendation - we'll take a look before we dig into this.

I noticed that the proposal for this was to use Zend_Crypt.  Having 
used that, myself, I, personally, would recommend that phpseclib be 
used, instead:

http://phpseclib.sourceforge.net/

phpseclib has been discussed here before:

http://bugs.horde.org/ticket/8341#c2

http://www.readwriteweb.com/archives/google_plaxo_openid_oauth_usability.php

Google's implementation:

http://www.readwriteweb.com/archives/google_is_now_an_openid_provider.php

Usability research from Yahoo! and notes about it:

http://developer.yahoo.com/openid/bestpractices.html

http://developer.yahoo.net/blog/archives/2008/10/open_id_research.html

http://www.25hoursaday.com/weblog/2008/10/15/YahooSharesOpenIDUsabilityStudy.aspx

ideas for login usability:

http://www.readwriteweb.com/archives/openid_usability_problems.php

http://www.25hoursaday.com/weblog/2008/09/19/ThingsToKeepInMindWhenImplementingOpenIDOnYourWebsite.aspx

Hello

Do they are some commit in cvs for this implementation ?

a little start of code or do you have a delay for implemante openID in horde.

thank you for your reply.

The start of implementation notes/resources are here:

http://wiki.horde.org/Project/OpenID

It'd be nice to have Horde/IMP support OpenID login.  You've been 
listed on the wishlist at http://wiki.openid.net/WishList for quite 
some time.  :)