Plone should…

Email address Login

Email address should be your user name not username. No one can remember their user name and this is a really big block for having logged in access to a site.

103 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    anonymousanonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    25 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Martin LundwallMartin Lundwall commented  ·   ·  Flag as inappropriate

        The betahaus.emaillogin has just been updated to support sites with large number of users. Now it is very fast even on sites with users up in the 10 or 100 thousands. There are unfortunately two patches that I would like to get rid of so if anyone know of a good way to get told when a users preferences are changed please let me know. ;)

      • deichideichi commented  ·   ·  Flag as inappropriate

        It is already possible to use email adresses for login since the introduction of PlonePAS. Your only problem will be to get the address from the email field to the "login name". We have already done this in the Plone 2.1 (now 2.5) site under http://www.gibinfo.de/
        If you leave the userid alone, you can login with both after that. (It was a pain back in 2.1, since everybody seemed to have mixed up userid and username in the code, but that is now working)

      • Ken WasetisKen Wasetis commented  ·   ·  Flag as inappropriate

        Allowing users ONLY the option of logging in with email address would be taking a step backwards, especially in cases where users prefer to remain somewhat anonymous (for example, a site for people with depression or alcoholism, where users don't want the world to know who they are), not be contacted by email by spambots, other users, etc.

        Also, isn't it already possible to allow an email address to serve as the username just by modifying the regex expression in the portal_registration tool to whatever pattern you choose?

      • IanFHoodIanFHood commented  ·   ·  Flag as inappropriate

        If vve have both then vve need the option to autogenerate (and make invisible) the userid (preferable the email address, or a hash of it) .
        It's the reuirement of user id for registration that I'd like changed because I already have integrated vvith systems that use email as UID and I keep having to search out the user by email, xref back and forth, etc.. and the users vvould prefer one to remember (not both).

      • WichertWichert commented  ·   ·  Flag as inappropriate

        I think the main thing here is to use the email address as login, but *not* use it as userid. If you do that correctly that almost all problems magically disappear.

        This is easily proven by the fact that people have been using email logins for LDAP accounts for years in Plone, without any problems.

      • Maurits van ReesMaurits van Rees commented  ·   ·  Flag as inappropriate

        Fred: you still need a user id, both with betahaus.emaillogin and with collective.emaillogin. The user id never changes. With collective the user id, login name and email address start out as the same thing; login name then tracks any email changes. With betahaus the login name never changes, even when the email changes.

        I have not tried betahaus, but the code looks good. I expect that it will have worse performance when there are a lot of users though. Some smart caching would be called for then. Some performance testing on both approaches would be good.

      • Fred van DijkFred van Dijk commented  ·   ·  Flag as inappropriate

        Robin: allthough betahaus.emaillogin allows you to login with an email address you still have to provide/make up a user id upon registration. The idea is that you do away with user id at all and use the unique email address instead.

      • Ricardo AlvesRicardo Alves commented  ·   ·  Flag as inappropriate

        I don't buy the argument "No one can remember their user name". Anyway, email logins are more and more frequent and I agree that Plone should also support this, as an optional configuration.

      • Robin Harms OredssonRobin Harms Oredsson commented  ·   ·  Flag as inappropriate

        Check out Martin Lundwall's excellent betahaus.emaillogin too, it simly looks up a username from an email address and makes sure email addresses are unique when users register. This is transparent to users, so you can enter an email address or a user name - both works.
        It doesn't monkeypatch anything.
        http://pypi.python.org/pypi/betahaus.emaillogin

      • Jussi TalaskiviJussi Talaskivi commented  ·   ·  Flag as inappropriate

        Email type login names come also to play when using federated authentication services like Shibboleth. Login names with @ should be allowed by default in my opinion.

      ← Previous 1

      Feedback and Knowledge Base