Skip to content
This repository has been archived by the owner. It is now read-only.

Discuss introducing a challenge before login attempt limit is exceeded #3646

Closed
ryanfeeley opened this issue Apr 11, 2016 · 10 comments
Closed

Discuss introducing a challenge before login attempt limit is exceeded #3646

ryanfeeley opened this issue Apr 11, 2016 · 10 comments
Assignees

Comments

@ryanfeeley
Copy link
Contributor

@ryanfeeley ryanfeeley commented Apr 11, 2016

Currently, when the number of login attempts exceeds our threshold, we simply put a "Attempt limit exceeded" error message above the login form.

Before blocking login attempts, we should introduce a challenge to verify that the user is indeed a human.

What are the best ways to accomplish this that deliver a great UX on mobile and desktop, and align with our engineering goals?

@vladikoff
Copy link
Contributor

@vladikoff vladikoff commented Apr 11, 2016

We can try using http://visualcaptcha.net/, it can be self-hosted and let us customize the options if needed

@vladikoff
Copy link
Contributor

@vladikoff vladikoff commented Apr 12, 2016

image

@ryanfeeley
Copy link
Contributor Author

@ryanfeeley ryanfeeley commented Apr 12, 2016

Final draft. Select object should have 1px dotted outline, #0095dd, no fill.
challenge-blue

@ryanfeeley
Copy link
Contributor Author

@ryanfeeley ryanfeeley commented Apr 13, 2016

Outstanding questions, perhaps of interest to @ckarlof:

  1. Is the number of attempts a user gets before seeing the challenge fixed in any way? (i.e. can we show a count down?)
  2. How many times is the user allowed to fail the challenge?
  3. What happens when the user exceeds the number of times they can fail the challenge?
@ryanfeeley
Copy link
Contributor Author

@ryanfeeley ryanfeeley commented Apr 13, 2016

@vladikoff Is there a way we can separate the captcha from the login? Like show it in a modal or on its own step?

@vladikoff
Copy link
Contributor

@vladikoff vladikoff commented Apr 13, 2016

From mtg: messaging might need to be adjusted if ip is blocked and it's user's first time

@rfk
Copy link
Member

@rfk rfk commented Apr 13, 2016

messaging might need to be adjusted if ip is blocked and it's user's first time

Right, so there's two reasons a user might encounter this error:

  • They individually are trying the same password over and over again on their account
  • They're on a shared IP that we've rate-limited due to other activity, but it's actually their first try at submitting the password

We should have the server return a different errno in these two different cases, so that we can give more accurate messaging to the user. I've noticed a few folks on twitter lately complaining that "FxA tells me attempt limit exceeded on my first try, wtf??".

@shane-tomlinson
Copy link
Member

@shane-tomlinson shane-tomlinson commented Apr 18, 2016

@ryanfeeley - can you open a feature card for this so we can prioritize appropriately?

@vladikoff
Copy link
Contributor

@vladikoff vladikoff commented May 2, 2016

Need to add result of discussion... and move to feature doc or something..

vladikoff added a commit that referenced this issue May 25, 2016
@vladikoff vladikoff added this to the FxA-84: recaptcha milestone May 25, 2016
@vladikoff
Copy link
Contributor

@vladikoff vladikoff commented May 31, 2016

moved to mozilla/fxa#153

@vladikoff vladikoff closed this May 31, 2016
vladikoff added a commit that referenced this issue Jun 6, 2016
vladikoff added a commit that referenced this issue Jun 7, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants