betahaus.emaillogin 0.2

What is betahaus.emaillogin?

The use of emailaddress are speading more and more but Plone does not have a convenient way to use a users registered email address to login.

betahaus.emaillogin makes it possible to login using the email address specified in the user profile.

Plone has a very powerful and modifiable authentication system called Pluggable Authentication Service (PAS). As the name suggest the system is pluggable and thus can easily be extended by third-party products such as this.

Installation

buildout:

• add betahaus.emaillogin entries to eggs and zcml in the appropriate buildout configuration file.

• re-run buildout.

• Install via portal_quickinstaller or Site Setup in plone

buildout.eggnest:

• copy this eggnest file to your eggnest directory

• re-run buildout

• Install via portal_quickinstaller or Site Setup in plone

How it works

betahaus.emaillogin is at installation put first in the list of extraction plugins. If an email address is specified and a corresponding user is found. The email address in the request is replaced with the username and then simulates failed extraction to continue normal login procedure.

• Code repository: https://svn.plone.org/svn/collective/betahaus.emaillogin

• Nestegg url: http://svn.plone.org/svn/collective/betahaus.emaillogin/buildout/src/betahaus.emaillogin.nestegg

A quick word about buildout.eggnest

buildout.eggnest is an extension to buildout that enables you to auto load eggs. You only drop a .nestegg specification file into a predefined directory and it will get downloaded by buildout as if it was entered in the buildout configuration file. This way you don’t have to edit the buildout config all the time. The .nestegg specification file is normally made by the author of the egg. More information at http://pypi.python.org/pypi/buildout.eggnest/

0.2 (2009-05-22)

• Fix bug in personalize_form.vpy that prevented editing user profiles. [davisagli]

0.1 (2009-05-11)

• Added custom personalize_form.vpy to prevent changing an existing user’s e-mail address to one that already exists. [davisagli]

• Avoid applying the custom import steps when other profiles are applied. [davisagli]

• Duplicate email warning at install [mlundwall]

• Check at registration to not allow multiple users with same email [mlundwall]

• Moved to collective. [mlundwall]

• Created recipe with ZopeSkel [Robin Harms Oredsson].