Support/Comments for LoginFields 1.0.0-beta1

This is an auto-generated topic for LoginFields 1.0.0-beta1 by jrotering.

Brief Description:

Works with standard profile fields or extended fields. Requires that a matching value be unique amongst all users - i.e. if matching the "fullname" field, and there are two users named "John Doe", the plugin will fail.

james,
would you give us an example how to use this and what kind of the output it should return?

Quote from: goldsky at Dec 06, 2010, 02:03 PM

james,
would you give us an example how to use this and what kind of the output it should return?

Once you install the package, you will find the LoginFields plugin in your list of plugins. If you click the plugin to edit it, then look at the properties, there is one property listed, called ’fields’. Here is where you can specify the names of user profile fields that you would like users to be able to have the option of using instead of the username. By default there are two fields listed: ’fullname’ and ’email’. This means that users can log in using either their full name or their email address instead of their username. This applies to Manager logins as well as logins to your web context if you have a login-based site.

There aren’t really any other basic fields in the user profile that would make sense to use (the list is here: http://rtfm.modx.com/display/revolution20/Users#Users-UserFields), but you can also use extended profile fields - this might make sense if you have an extended field like an employee ID number or something.

There is no output involved - if the user enters in the username field a value that matches one of the fields you are allowing - and they are the only user to have that value, then the login will succeed (assuming they have the right password for the account). If they input something that doesn’t match on any of the allowed fields (or multiple matches are found) the login will fail.

So, just to be clear: by default the plugin lets users use their fullname or email address instead of their login name when logging in. So if I have the plugin installed, I can login using ’jrotering’, ’James Rotering’, or ’[email protected]’ as the username value. Any of them will work, *provided that* there are not multiple accounts found. If I use my full name, there has to be only one user account with my full name or the login will fail. Same for the email address, or any other fields you are allowing with the plugin.

Ow, well...
For a big site with huge subscribers list, full name duplicates seems a common situation.
If this is the Login’s defaut, then it’s wrong.

Don’t you think so?
I’d rather restricting the username (1st) and/or email (2nd).

Full name duplicates is definitely a likely scenario on a large site. Hopefully a future version of the plugin will accommodate that - but it would have to test the password against each matching name. I’m not entirely sure of the wisdom of that from a security perspective, or of how to write the code from a technology perspective. For now I’ve just kept it simple, with the caveat that it only works when one matching record is found.

Quote from: jrotering at Dec 06, 2010, 10:45 PM

Once you install the package, you will find the LoginFields plugin in your list of plugins. If you click the plugin to edit it, then look at the properties, there is one property listed, called 'fields'. Here is where you can specify the names of user profile fields that you would like users to be able to have the option of using instead of the username. By default there are two fields listed: 'fullname' and 'email'.

How should it look like? I don't have such a property in the plugin. Could you please show the whole line or just name it's number?

Maybe something changed in a new version?

By the way, I had problems with the automatic instalation of the plugin. It didn't install and after all manager began to output a js error. I had to delete the plugin from DB manually and then create a new plugin from manager. Is there a difference?