XMPP Authentication 0.3

This plugin has two main features: any reader on your website can comment if one has an Instant Messaging address (XMPP protocol, otherwise called Jabber. A Gmail or a LiveJournal account for instance are such standard IM identifiers as well); a subscribed user (whatever its role) can authenticate with one's IM address if they set their IM address.This plugin is still in experimental state but is usable.Detailed ProcessThe authentication part is something like openID, except that it uses your existing IM address: you ask for authentication on a website, and it pops-up a confirmation via IM (that you can accept, or refuse).Considering that the IM protocol (XMPP) is very secure, all the infrastructure to securely exchange an authentication request is there. No need to make any new account, no need a special client, nor a identity third party provider, and that's really instantaneous (as instant messaging) and more secure than HTTP or SMTP protocols.Spam ProtectionIt adds an additional layer to protect against Spam by verifying an identity using a very secure and modern protocol (XMPP), which also is instant, hence much more reliable in any way than email for instance.Secure and Easy LoginMany reasons to use such a plugin for login: not to have to remember a new password (password-login can be disabled in your profile, on a per-user choice); you are in a very insecure environment (for instance a cybercafe) and consider only your IM account to be a minimum securized. Or better, you run an IM client on your smartphone (or a similar tool), so you would receive the query on this personal item while never typing any kind of password on the insecure platform where you log. And so on. Install : The easy way is via your installed WordPress's administration pages: Click Plugins > Add New; Search for xmpp-auth; Find it in the displayed list; Click Install Now.Alternatively, here is the old "manual" version: Upload the plugin archive to wp-content/plugins/ directory on your WordPress installation; Uncompress it by keeping it in its own sub-directory called xmpp-auth/; Activate the plugin through the 'Plugins' menu in WordPress; Configure the plugin through the appearing sub-menu XMPP Authentication under the Plugins menu; When aknowledging the configuration by pressing the Update button, login will be tested (a connection will be attempted). If anything is wrong with your configuration, you will be immediately informed.Once installed, I would suggest to modify the configuration in Settings > Discussion > uncheck Comment author must fill out name and e-mail as they will be verified by XMPP (but the fields will stay if the user wants to add them in).dependencies PHP > 5.1.0 (for function stream_socket_enable_crypto). expat library to parse XML (enabled with the --with-xml option of the php compilation).Note for gentoo users: you must set the 'xml' USE flag. Auth_SASL PEAR module (pear install Auth_SASL or install with your distribution's package manager) for SASL authentication. For now, this dependency is mandatory. Maybe in some future will it become optional. OpenSSL (> 0.9.6) must be installed on the server and PHP must be built with --with-openssl. OPTIONAL: if the plugin is installed on a BSD (Mac included), in order to use the SRV records on the admin JID, which is the correct way of resolving the server and port addresses for a domain, the PEAR extension NET_DNS must be installed: pear install NET_DNS (Note that it will ask to have php compiled with mhash option). If it is installed on Windows, it is not anymore useful if you have PHP 5.3.0 or later installed (under this version of PHP, you should also install the NET_DNS extension to benefit SRV records). Linux servers do not need this extension to have SRV.Note for gentoo users: you must set the 'mhash' USE flag.Working PlatformsThis script has been tested only currently on WordPress 3.2.1 up to WordPress 3.2.1 with PHP 5.3.5 up to PHP 5.3.6, running on a GNU/Linux 64 bits (Gentoo Linux). Hopefully it should work with other software versions (not for PHP4, because of the TLS feature which is PHP5 specific. Yet if you are really interested into PHP4 compatibility and if TLS is not required for your connection, just ask me, I will try to make a compatibility layer), but I cannot guarantee. Tell me please if you tried this successfully with another configuration so that I update the known working platforms list.At the opposite, if you find a bug or encounter an issue on some configuration, don't hesitate to tell me, and I will try and fix it.

Requirements:	No special requirements
Platforms:	PHP
Keyword:	Email,  Login,  Modern,  Reasons,  Reliable,  Verifying
Users rating:	0/10