Description of problem
We currently have an easy-to-use feature that empowers administrators to turn on CAPTCHA very easily and it mostly just works. However, this feature is almost as old as DNN and hasn't been improved over the years to implement newer standards. It also is not accessible and visitors who know how can easily get around it.
This issue was once in DNN's other issues trackers in the past, but I'd like to bring it back up for potentially being implemented in the future.
Description of solution
Replace the current CAPTCHA feature with a provider model. The providers available out-of-the-box should be this one (default) since it's super-simple to turn on and use, with ReCAPTCHA available as an alternative (requires sign-up and copying/pasting unique keys from another website).
This probably would be best implemented as a connector at this point.
Description of alternatives considered
We could just replace the current CAPTCHA with ReCAPTCHA, but with our ecosystem, people would be much happier if they had a choice on which provider to use, and having a provider model allows for new commercial and open-source extensions to be created for the ecosystem.
Additional context
This has been spoken about off and on for more than ten years now (since I worked at DNN Corp, for sure...). Here's the most recent forum post about this feature:
https://dnncommunity.org/forums/aft/1990
Past Issues:
https://dnntracker.atlassian.net/browse/DNN-6288
https://dnntracker.atlassian.net/browse/DNN-6385
https://dnntracker.atlassian.net/browse/DNN-6384
https://dnntracker.atlassian.net/browse/DNN-10177
https://dnntracker.atlassian.net/browse/DNN-9693
Affected browser(s)
Description of problem
We currently have an easy-to-use feature that empowers administrators to turn on CAPTCHA very easily and it mostly just works. However, this feature is almost as old as DNN and hasn't been improved over the years to implement newer standards. It also is not accessible and visitors who know how can easily get around it.
This issue was once in DNN's other issues trackers in the past, but I'd like to bring it back up for potentially being implemented in the future.
Description of solution
Replace the current CAPTCHA feature with a provider model. The providers available out-of-the-box should be this one (default) since it's super-simple to turn on and use, with ReCAPTCHA available as an alternative (requires sign-up and copying/pasting unique keys from another website).
This probably would be best implemented as a connector at this point.
Description of alternatives considered
We could just replace the current CAPTCHA with ReCAPTCHA, but with our ecosystem, people would be much happier if they had a choice on which provider to use, and having a provider model allows for new commercial and open-source extensions to be created for the ecosystem.
Additional context
This has been spoken about off and on for more than ten years now (since I worked at DNN Corp, for sure...). Here's the most recent forum post about this feature:
https://dnncommunity.org/forums/aft/1990
Past Issues:
https://dnntracker.atlassian.net/browse/DNN-6288
https://dnntracker.atlassian.net/browse/DNN-6385
https://dnntracker.atlassian.net/browse/DNN-6384
https://dnntracker.atlassian.net/browse/DNN-10177
https://dnntracker.atlassian.net/browse/DNN-9693
Affected browser(s)