Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to request CAPTCHA on user creation #200

Open
RohanNagar opened this issue Jun 22, 2018 · 0 comments
Open

Add option to request CAPTCHA on user creation #200

RohanNagar opened this issue Jun 22, 2018 · 0 comments
Assignees
Labels
P3 Low priority. No set deadline to address. Size: Large The work involved in addressing this issue is substantial. Multiple days or weeks of work. Status: Available Work on this issue has not yet started and is available to be worked on. Type: Feature Addresses adding a new feature to the application.
Milestone

Comments

@RohanNagar
Copy link
Owner

Describe the problem that this feature would solve

One of the standard ways to prevent bot signups is to require the end user to answer a CAPTCHA sent from the server. Thunder does not currently have this functionality.

Describe the solution you'd like

There should be a configurable option to enable CAPTCHA on POST /users. Ideally, when enabled, the flow would look like:

  1. Client application sends a POST request with the user data
  2. The server responds with an appropriate error code asking the client to re-try with a solution to the given CAPTCHA challenge
  3. The client displays the CAPTCHA challenge to the user, they answer
  4. The client retries the request with the answer to the CAPTCHA

Additional context

I have never worked with CAPTCHA before, so I may not know all of the limitations or how the protocol should actually work.

@RohanNagar RohanNagar added Type: Feature Addresses adding a new feature to the application. P3 Low priority. No set deadline to address. Status: Available Work on this issue has not yet started and is available to be worked on. Size: Large The work involved in addressing this issue is substantial. Multiple days or weeks of work. labels Jun 22, 2018
@RohanNagar RohanNagar added this to the v2.1.0 milestone Jun 22, 2018
@NickEckert NickEckert self-assigned this Jun 26, 2018
@RohanNagar RohanNagar modified the milestones: v2.1.0, v2.2.0 Aug 20, 2018
@RohanNagar RohanNagar modified the milestones: v2.2.0, v2.3.0 Aug 31, 2018
@RohanNagar RohanNagar modified the milestones: v2.3.0, v2.4.0, v2.5.0 Feb 15, 2019
@RohanNagar RohanNagar modified the milestones: v2.5.0, v3.2.0 May 27, 2020
@RohanNagar RohanNagar modified the milestones: v3.2.0, v3.3.0 Aug 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 Low priority. No set deadline to address. Size: Large The work involved in addressing this issue is substantial. Multiple days or weeks of work. Status: Available Work on this issue has not yet started and is available to be worked on. Type: Feature Addresses adding a new feature to the application.
Projects
None yet
Development

No branches or pull requests

2 participants