To control spam and other abuse, a phone verification system could be useful. This would be optional for any Allura instance to use, of course.
Initially I'd like to see this on project registration. The
ProjectRegistrationProvider can provide methods to allow flexibility in different deployments. A default implementation could be as follows. The first time a user registers a project, they will be shown a followup screen requesting a phone number for either SMS or voice verification. (If a user has any existing non-deleted projects, this will be skipped and registration occurs as normal). Verification occurs (see next paragraph). If verification succeeds, record that on the user record so they won't have to verify again, and add a user audit log too. Use a non-salted hash of the phone number, do not ever store the full number. Then project registration actually occurs. If verification fails, record an audit log also. Let the user try again.
For actual phone verification, we should set up a simple abstraction layer to allow different verification services to be used. See the "spam.method" config and
SpamFilter classes as an example of that type of setup. Specific implementations could include Twilio, Nexmo Verify, etc. These classes could be used for different situations later too (e.g. two-factor login)
Site-specific messages will need to be included in this too. E.g. saying the phone number will be used for verification only and will not be stored; or if they are having problems how to contact support, etc. Simple text could be handled with a config setting, more complex with a template override.
Don't need to apply this to project imports.
Log in to post a comment.