We are currently implementing a web interface whereby users register themselves, we return a one time only password which they log in and set various security questions.
We have a potential issue where somebody could create a script to fire off thousands of user registrations from one machine and clog up our network. Is there something cute I could do with the log on? Or am I over-reacting and this isn't really an issue?
Thanks
We have a potential issue where somebody could create a script to fire off thousands of user registrations from one machine and clog up our network. Is there something cute I could do with the log on? Or am I over-reacting and this isn't really an issue?
Thanks