=== WP-OpenID ===
Contributors: wnorris, alanjcastonguay, factoryjoe
Tags: openid, authentication
Requires at least: 2.2
Tested up to: 2.5.0rc1
Stable tag: 2.1.7

Allow the use of OpenID for authentication of users and commenters.


== Description ==

OpenID is an [open standard][] that lets you sign in to other sites on the Web
using little more than your blog URL. This means less usernames and passwords
to remember and less time spent signing up for new sites.  This plugin allows
verified OpenIDs to be linked to existing user accounts for use as an
alternative means of authentication.  Additionally, commenters may use their
OpenID to assure their identity as the author of the comment and provide a
framework for future OpenID-based services (reputation and trust, for
example).

[open standard]: http://openid.net/


== Installation ==

This plugin follows the [standard WordPress installation method][]:

1. Upload the `openid` folder to the `/wp-content/plugins/` directory
1. Activate the plugin through the 'Plugins' menu in WordPress
1. Configure the plugin through the 'OpenID' section of the 'Options' menu

[standard WordPress installation method]: http://codex.wordpress.org/Managing_Plugins#Installing_Plugins


== Frequently Asked Questions ==

= Why do I get blank screens when I activate the plugin? =

In some cases the plugin may have problems if not enough memory has been
allocated to PHP.  Try ensuring that the PHP memory_limit is at least greater
than 8MB (limits of 64MB are not uncommon).

= Why don't `https` OpenIDs work? =

SSL certificate problems creep up when working with some OpenID providers
(namely MyOpenID).  This is typically due to an outdated CA cert bundle being
used by libcurl.  An explanation of the problem and a couple of solutions 
can be found [here][libcurl].

[libcurl]: http://lists.openidenabled.com/pipermail/dev/2007-August/000784.html

= How do I add an OpenID field to my comment form? =

The easiest way to display the fact that your blog accepts OpenIDs is to enable
the "Comment Form" option for the plugin.  This will allow the normal website
field to be used for OpenIDs as well.  If this doesn't display properly for
your particular theme or you simply prefer to have a separate OpenID field, you
can modify your comments.php template to include an "openid_url" text field as
part of your comment form.  For the default theme, this might look like:

	<p><input type="text" name="openid_url" id="openid_url" />
	<label for="openid_url"><small>OpenID URL</small></label></p>

The input element MUST have the name "openid\_url".  Additionally, using
"openid\_url" for the id causes the field to be styled with an OpenID logo.  To
remove this, you can override the stylesheet or simply change the element id.

= How do I get help if I have a problem? =

Please direct support questions to the "Plugins and Hacks" section of the
[WordPress.org Support Forum][].  Just make sure and include the tag 'openid'
so that I'll see your post.  Additionally, you can file a bug
report at <http://dev.wp-plugins.org/report>.  Existing bugs and feature
requests can also be found at [wp-plugins.org][bugs-reports].

[WordPress.org Support Forum]: http://wordpress.org/support/
[bugs-reports]: http://dev.wp-plugins.org/report/9?COMPONENT=openid


== Screenshots ==

1. Commentors can use their OpenID when leaving a comment.
2. For users with wordpress accounts, their OpenID associations are managed through the admin panel.
3. Users can login with their OpenID in place of a traditional username and password.


== Changelog ==

= version 2.1.7 =
 - remove php5 dependency bug... AGAIN!
 - also remove some other custom changes to php-openid I forgot were in there.  This may actually re-introduce some edge-case
   bugs, but I'd rather expose them so that we can get the appropriate patches pushed upstream if they really are necessary.

= version 2.1.6 =
 - update php-openid library to latest.  Now properly supports Yahoo's OpenID provider.

= version 2.1.5 =
 - add support for wordpress v2.5

= version 2.1.4 =
 - fix php5 dependency bug
 - improve jQuery code to reduce problems with other js libraries

= version 2.1.3 =
 - address security bug mentioned [here](http://www.gnucitizen.org/blog/hijacking-openid-enabled-accounts).  Props: Sam Alexander

= version 2.1.2 =
 - minor typo in profile data code

= version 2.1.1 =
 - minor bug where profile data is being overwritten

= version 2.1 =
 - added FAQ items for plugin updater and adding an OpenID field to a comment form
 - better tracking of which users have OpenIDs linked to their local WP account
 - better automatic username generation
 - fixed bug where non-OpenID websites had problems (bug [729])
 - upgrade to version 2.0 of JanRain OpenID library
 - admin option to rebuild tables

= version 2.0 =
 - simplified admin interface by using reasonable defaults.  Default behaviors include:
  - "unobtrusive mode"
  - always add openid to wp-login.php
  - always use WP option 'home' for the trust root
 - new features
  - hook for trust engine, with very simple implementation included
  - supports OpenID 2.0 (draft 12) as well as OpenID 1.1 and SReg 1.0
 - normal collection of bug fixes

= version 1.0.1 =
 - added wordpress.org style readme.txt
 
= version 1.0 (also known as r13) =

Full SVN logs are available at <http://dev.wp-plugins.org/log/openid/>.

[729]: http://dev.wp-plugins.org/ticket/729